Re: [HACKERS] CVS trees and post-6.4 release issues

On Fri, 30 Oct 1998, Bruce Momjian wrote:

> We will not be splitting the CVS tree after the 6.4 release.

Actually, the 'splitting' and 'tagging' are one and the same, and
it will be tagged the moment I roll the release tar ball...that is
automatic *shrug* Its been done for every past release...if you don't use
the branch, not a problem, but it is created...

> We will continue with one source tree, applying patches needed for any
> 6.4.* minor releases.
>
> When we have finished with 6.4.* releases, we will mark the cvs tree,
> and start on 6.5. We mark it so we can supply patches to fix serious
> problems that appear after 6.4.* has been closed.
>
> Any risky feature patches that are posted during this period will be
> held, and applied once 6.4.* is finished. We expect the 6.4.* feature
> freeze period to last about one month.
>
> Certain _safe_ feature patches will be applied during this period.

I don't think so...I heard that one after the BETA freeze, and
look at the mess *that* created. If there is a feature freeze for
post-release bugs to be fixed, features are *frozen*, period, end of
story, do not pass go, do not collect $200, end of story...

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org