Re: Release planning (was: Re: Status report) - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Release planning (was: Re: Status report)
Date
Msg-id 1089770787.49769.4.camel@jester
Whole thread Raw
In response to Re: Release planning (was: Re: Status report)  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
On Tue, 2004-07-13 at 20:49, Marc G. Fournier wrote:
> On Tue, 13 Jul 2004, Tom Lane wrote:
> 
> > We could certainly do something along that line if we had a few people 
> > willing to be "gatekeepers".  We'd have to work harder at making the 
> > release generation process open and documented though.  Right now there 
> > are plenty of steps that only you, Bruce, or Lamar (respectively) know 
> > how to do...
> 
> I think we could do it if we restricted it to *just* one release back ... 
> but I do agree with Peter about ppls motivations for upgrading (bug fixes 
> vs new features) ... we'd have to have a 'two branch stable', one would be 
> only bug fixes, the other would be bug fixes+feature backpatch ... would 
> could get interesting trying to figure out release naming conventions :)

FreeBSD does do this. They tag the bug-fix only branches as being
SECURITY releases, since typically they only contain fixes for security
or reliability related issues.

The 5.2.1 release which followed 5.2.0 was an example of one of the few
releases the Security team has done. They usually just allow users to
use CVSUP to follow the branch.




pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: Release planning (was: Re: Status report)
Next
From: Rod Taylor
Date:
Subject: Re: Release planning (was: Re: Status report)