> > I agree with Ryan that branching the release branch can get pretty > confusing. I've only seen a version number like 0.20.3.1 once before, and > that was for a completely botched release, where the .1 was a very very > minor fix on top of the first release. In this case, even though there > aren't any giant changes slated, there are changes that are large enough > that it seems dishonest to call it a "doubly minor" release on top of > 0.20.3.
We already agreed to call it 0.20.4 instead of 0.20.3.1 > > Regarding the bigger changes we have slated for 0.20 branch (eg durability > fixes, 2248), why not just call it 0.21 at that point? We've already decided > that future versions of HBase will be compatible with multiple versions of > Hadoop, so we can add these major changes for 0.21 and then make 0.22 the > next major release with replication, mvn, etc? This is for another discussion, I'd like to end this one first. > > -Todd >
