X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] [pcb] Plans for Next Release of pcb
To:	geda-user AT delorie DOT com
References:	<CAJZxidDy5HcLZivqc5w+cnv716EFNLXKJdKXo+jDPMDVrJb2=Q AT mail DOT gmail DOT com>
	<585ADD79 DOT 3020403 AT xs4all DOT nl>
From:	"Dan McMahill (dan AT mcmahill DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<bd246b73-ffa9-72df-5c42-ab04aa6b9b65@mcmahill.net>
Date:	Fri, 23 Dec 2016 17:01:44 -0500
User-Agent:	Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101
	Thunderbird/45.5.1
MIME-Version:	1.0
In-Reply-To:	<585ADD79.3020403@xs4all.nl>
X-CMAE-Envelope:	MS4wfE5Mj2W3UvzwElJAPMyHcEGalyiMg6K56SsuS9k0Ja/Wmq7HLyFj/NwsOL+KhA0UfdQlnaYMnHDdTMR6cmsW3qguwtTBodSTS0Js90SquMisuL0r1YVO
	OzSoIsgI2/oBjMV8jmnVn9NGn8nQrbip8g9YyDqoLgPfa5JJBlCpzUI4
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 12/21/2016 2:52 PM, Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via 
geda-user AT delorie DOT com] wrote:
> Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:


>> 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)?

> Yeah, I'm in the same situation ... never done a pcb release.
>

yes, for pcb there is a documented procedure.  There is a readme in the 
top level of the source tree.  I tried to strictly follow it and when 
needed, update the document to match what was actually done on all the 
snapshots I did in the past.  Note that the procedure was done in CVS 
days and may need some additional tweaking in the git world although I 
think it has been updated for git.  It is important that we follow the 
procedure because it does catch (and has caught) some relatively minor 
issues which can cause real grief if not done.

Historically we have not done release candidates for pcb.  I have 
created release branches but these have largely just been a stake in the 
ground with patch releases reserved for major screw ups like a missing 
source file in the distribution (which would be caught by the release 
procedure) or catastrophic failure.  I think between pcb and gerbv 
(which uses the same procedure) we've only had maybe 1 patch release in 
the last decade.  The reality is in the past we didn't anticipate having 
the manpower to maintain a release branch as well as the main 
development.  That is why pcb releases have been called snapshots.

-Dan

- Raw text -