I've only one concern, if we go for a 4.0.1 bugfix release, since there are a lot of changes in build system and packaging on master, simply cherry picking may not work. I would like to suggest that we drive all our engineering efforts on master (release wise, build system, esp. pkging are blockers on master), switching between 4.0 and master may confuse people, I've seen some of my colleagues now becoming comfortable with maven, yes the build system, so let's not go back to ant. Maybe we can cut out a 4.0.1 release based on master since there has not been any major feature or backward compatibility breaking change on master. Flames, thoughts?
Regards. ________________________________________ From: Chip Childers [chip.child...@sungard.com] Sent: Tuesday, November 13, 2012 3:10 AM To: cloudstack-dev@incubator.apache.org Subject: Re: [DISCUSS][ASFCS40] 4.0 Branch Lifecycle On Wed, Oct 31, 2012 at 8:30 PM, Chip Childers <chip.child...@sungard.com> wrote: > Hi all, > > Since I just started up the conversation about timing of feature > releases, I wanted to start the discussion on how we want to decide > what goes into the 4.0 branch and when we would pull the trigger on a > 4.0.X bug-fix release process. Personally, I don't have a > particularly strong opinion about when we cut bug fix releases, but I > do strongly feel that we should have one or two committers that are > the "masters" of the 4.0 branch. We should be very careful about what > goes in there from now on, with a focus on (1) security issues, (2) > high priority bugs, and (3) bugs that might be minor, but really annoy > the heck out of our users. > > So... thoughts? Anyone willing to "own" the 4.0 branch during it's > support lifetime? > > -chip It looks like Joe's the only one with comments on this subject. I'd like to see us start thinking about a 4.0.1 bug-fix release shortly (perhaps we plan to cut one for mid December?). David mentioned that he thought it was about time to start thinking about this, and I agree. Thoughts?
