I considered that as well, but this project decided to follow this workflow [1]. That article suggests that bug fixes are made on the release branch and then (immediately) merged back into develop.
That also makes sense, as the release branch will be as stable as possible, while develop may or may not be, depending on what is committed. I don't want to impose any restrictions on the develop branch, as the 'less-RC' may take considerable time. Reading the 'stabilizing' article right now, interesting stuff. EdB 1: http://nvie.com/posts/a-successful-git-branching-model/ On Tue, Dec 2, 2014 at 2:27 PM, Frédéric THOMAS <webdoubl...@hotmail.com> wrote: > Hi Erick, > Nice introduction, I just wanted to ask, it is written "Any issues found > should be fixed - preferably by the reporter - and committed to the 'release' > branch", why not fix on the dev branch and cherry picked onto the release one > avoiding a merge back to the dev branch ? > A nice article too [1] btw ! > > Frédéric THOMAS > [1] http://producingoss.com/fr/stabilizing-a-release.html > >> From: e...@ixsoftware.nl >> Date: Tue, 2 Dec 2014 09:19:34 +0100 >> Subject: Re: The 'less-RC' process explained >> To: dev@flex.apache.org >> >> Excellent idea. I've added it to the Wiki text. >> >> EdB >> >> >> >> On Mon, Dec 1, 2014 at 9:04 PM, Alex Harui <aha...@adobe.com> wrote: >> > I’m ok with it too. I would like to see a specific subject tag for the >> > way the RM "makes his intention” known. How about [LAST CALL]? That >> > would make it stand out from the usual email traffic. >> > >> > -Alex >> > >> > >> > On 12/1/14, 10:26 AM, "Kessler CTR Mark J" <mark.kessler....@usmc.mil> >> > wrote: >> > >> >>+1 >> >> >> >>Looks like it's doable and shows similarities to other development >> >>projects I have seen. But with a lot less steps. >> >> >> >>-Mark >> >> >> >> >> >>-----Original Message----- >> >>From: Erik de Bruin [mailto:e...@ixsoftware.nl] >> >>Sent: Monday, December 01, 2014 5:07 AM >> >>To: dev@flex.apache.org >> >>Subject: The 'less-RC' process explained >> >> >> >>Hi, >> >> >> >>I've put an initial draft for an explanation of the 'less-RC' process >> >>into the Wiki: >> >> >> >>https://cwiki.apache.org/confluence/x/2oH0Ag >> >> >> >>Please take a look and see if that properly summarizes the previous >> >>discussions we've had. >> >> >> >>Thanks, >> >> >> >>EdB >> >> >> >> >> >> >> >>-- >> >>Ix Multimedia Software >> >> >> >>Jan Luykenstraat 27 >> >>3521 VB Utrecht >> >> >> >>T. 06-51952295 >> >>I. www.ixsoftware.nl >> > >> >> >> >> -- >> Ix Multimedia Software >> >> Jan Luykenstraat 27 >> 3521 VB Utrecht >> >> T. 06-51952295 >> I. www.ixsoftware.nl > -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
