On Wed, Jan 26, 2011 at 10:27 AM, Benjamin Reed <br...@yahoo-inc.com> wrote: > i would really like to get 3.3.3 out because of the fixes that just went in. > > there are quite a few bugs that are marked for 3.3.3, but i think they can > all be pushed to 3.4.0. >
Any non-blocker jiras are always pushed to the next release if they are not resolved for the current release. What you are describing is how we always do things. Blockers always hold up the release unless specifically addressed otherwise (changing the severity or agreeing to push it to a subsequent release). > i would really like to push everything to 3.4.0 and then work on getting the > 3.4.0 release out. we haven't done a release from trunk in a while, but that > is the only code that gets tested by hadoopqa. i think it is a bad idea to > be releasing from branches that are not regularly tested. > That sounds fine. However we always maintain a fix branch in parallel in case something critical (blocker) comes up before the trunk is ready. > going forward doesn't it seem like a better idea to only do a release from > just a branch if it is something that pops up quickly right after a release. > otherwise, we should be releasing from trunk and possibly doing a > simultaneous release from a branch. In theory that's how it should work. However the trunk release has gotten stalled. One way to un-stall things is for someone to step up and agree to be release manager for 3.3.3 and 3.4.0 releases (doesn't have to be the same person). That person is responsible for determining when the release is ready, what's in the release, etc... Patrick
