X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=VuLaja2gSZI/r8KuDdbllgVEIXkXRlMh7c8KH/eHWHg=; b=gXh3B2yfui9hPTbChtp/GLH2uQ+qpYGoeWgzLaT/E5UX1lGnNoOW8CwDDmCLGxogUN YvG+okvh0dzZSVPsaMKsLF75WRi+IycJFwXbLSlEQ2m0i6jg+vigaP4MXXv0tUIuYzVc EhwibSzAKV6+I2dmpKSusmQDSDOXuJOnDrwJ0CWAwlgeKPvilzF0gln9akL8Z+5y9RbS VyNKrDcFX2oV4YEWQsOXT0Y+eG39w/TAESiXJh3oK4bluatBgQfheeU7FT6SpEV7N0TB bDZdnfplHGH5jFVc94xllR9UyvcI8g4PXjE2w0u8r9mBAI+jnwGH5j4pgY5LlHx/m6GM b01w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=VuLaja2gSZI/r8KuDdbllgVEIXkXRlMh7c8KH/eHWHg=; b=Cy+LtGpTT2sG/KGPTvKh5eMAgHdj9RxjtgI5STO+s2aiSdEq6YN7EG0wIm6EBkVhOP oV2Sr+is+qXuAtJmo9ml0Bdm/wW0JFDsjexMKOKKOZzR+OOjY0FscKhM+lHSmXBCfNph vBrHuGVKPIkM80omSytwtX5kctZp2CeljRKL5ihSdfGlzgdNXDdKg1GAysPKYGT/fHDw I1iFkHWcBlw7I2Ie4uPM9C5nPc89oNM32owztaeCyavc35QeLK4bwYfUKYMTAhEnA303 CTAVeyLtjWIgHLm49R6dK/2EBi0t/I4fzGTuT3qoRMNdDUKE/i7C0OdhD20nN510vhQ8 a/Gg== X-Gm-Message-State: AIkVDXJ/voMHFfRezRLLSkh65LdggdJRXiMpzSTZDcvGKV4cIWTRPFdSLM1jPkwkjSVjbTfW7QidYE1rpcgiMw== X-Received: by 10.28.224.5 with SMTP id x5mr6726737wmg.70.1482327821482; Wed, 21 Dec 2016 05:43:41 -0800 (PST) MIME-Version: 1.0 From: "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" Date: Wed, 21 Dec 2016 08:43:40 -0500 Message-ID: Subject: [geda-user] [pcb] Plans for Next Release of pcb To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=001a114b117e3d928605442b578c Reply-To: geda-user AT delorie DOT com --001a114b117e3d928605442b578c Content-Type: text/plain; charset=UTF-8 Hi pcb Devs- It really is time to do a release of pcb. There have been a lot of bug fixes incorporated since the last release, and the distribution packages don't keep up with the latest git version. I wanted to start this thread to collect ideas and generally figure out how to execute this process, and hopefully push it forward. Being a relatively new developer to the project, I'm not entirely sure what's involved. So, let's start with some questions: Is there already a process in place for executing a release of pcb (or other gEDA tools)? I found this on the wiki: http://wiki.geda-project.org/geda:release_engineering . Is it still relevant? Should we consider first putting out a release candidate? Regarding packaging, do we create packages for distributions, or do the distributions to that themselves? I'm willing to spend some time to make this happen, but I need some guidance. Thanks, --Chad --001a114b117e3d928605442b578c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi pcb Devs-

It really is time to d= o a release of pcb. There have been a lot of bug fixes incorporated since t= he last release, and the distribution packages don't keep up with the l= atest git version.

I wanted to start this thread to colle= ct ideas and generally figure out how to execute this process, and hopefull= y push it forward. Being a relatively new developer to the project, I'm= not entirely sure what's involved. So, let's start with some quest= ions:

Is there already a process in place for executing a release of= pcb (or other gEDA tools)?

I found this on the wiki: http://wiki.geda-proje= ct.org/geda:release_engineering . Is it still relevant?

<= div>Should we consider first putting out a release candidate?

=
Regarding packaging, do we create packages for distributions, or do th= e distributions to that themselves?

I'm willing to sp= end some time to make this happen, but I need some guidance.

<= div>Thanks,
--Chad
--001a114b117e3d928605442b578c--