> On Wed, Nov 16, 2011 at 1:11 PM, Matt Foley wrote: > I support giving all three active code branches a clean start, on an equal > footing: > > - The next release of 0.20-security (formerly expected as > "0.20.205.1") to be 1.0.0, establishing branch-1.0 > - The next release of 0.22 to be 2.0.0, establishing branch-2.0 > - The recent release of 0.23.0 to be 3.0.0, establishing branch-3.0, > from which the formerly expected "0.23.1" may be released as 3.0.1 > - All three code branches to obey the established major.minor.patch > versioning rules going forward. > - So the next release from trunk to be 3.1.0 or 4.0.0, at the choice of the > then release manager, and the pleasure of the community.
+1 non binding Clean and easily understood. After an initial round of "what just happened?", it will be much easier explaining Hadoop evolution to users. - Andy
