Re: [groovy-dev] Towards 1.8-beta-4 on Friday
Russel Winder <russel@...
2011-02-01 13:40:35 GMT
On Tue, 2011-02-01 at 14:15 +0100, Guillaume Laforge wrote:
[ . . . ]
> We're going to release 1.8-beta-4 on Friday (a joint release with
> If you have some things in the works, please raise your hand, and we
> can see if we can integrate that in time for the release.
Grails needs a Gant to be released with the Groovy 1.8.0 release, so I
am raising my hand for a co-release cycle.
> Beta-4 should be the last beta release for 1.8, with the idea of
> switching to Release Candidate mode (and hence feature freeze, with
> only key fixes to be committed).
Russel being (tediously) repetitive, to pre-empt the usual argument:
Once release candidate mode is entered, there should be nothing
committed to the release branch at all unless it is critical to the
release to fix a blocking or majorly critical bug. The final release
artefacts should be identical to the final release candidate -- just a
name change. Once the release is made the branch can be opened for bug
fixes. Once 1.8.0 is released, only bug fixes should be applied leading
to 1.8.1, 1.8.2, etc., no development should happen on the maintenance
branch, all development should be on the 1.9.0-snapshot branch.
> We'll create a 1.8 branch after the beta, and trunk will become Groovy
I wonder if there should be some access control applied to the
maintenance branches so as to ensure only bug fixes are applied?
> Keep on groovying
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder <at> ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel@...
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder