On Thursday 24 February 2005 14:28, Brad Templeton wrote: > I would hope that the two most common suggestions here would not make > the project any less fun. > > a) There's a period of about 1-2 weeks every few months between > release candidate and release where new features are not checked > in, > only fixes > > and/or > > b) Somebody trusted steps up to the plate to be a release handler > who > volunteers to move any significant bug fixes from post release > into > the release branch, and works with the binary packagers to get > these fixes into those packages. Also works with them to make > release candidate binary packages.
Why not combine (a) & (b) and create the release branch 1-2 weeks prior to the actual release, and only allow bug fixes on the release branch? Then you could release 0.17-pre1, -pre2, -rc1, -rc2, etc right from the release branch. That way bleeding-edge development can continue on the trunk without interruption. Everybody wins. As long as someone is willing to manage the release branch, it's not any extra work for anyone but the release manager. -JAC _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
