For example I have an internal build that is current to 0.20 branch but
excludes the following commits:
commit 118c6e5ba091ed96b23b74a6523eb14b4bbddc13
Author: Michael Stack <st...@apache.org>
Date: Sat Mar 6 22:38:30 2010 +0000
HBASE-2298 Backport of "HLog Group Commit" to 0.20 branch
commit cb11e28f7d15e1c8175aed0faf74834bbc387717
Author: Michael Stack <st...@apache.org>
Date: Wed Mar 10 15:20:36 2010 +0000
HBASE-2234 Roll Hlog if any datanode in the write pipeline dies
commit 61b0ac467cc48aed5455ad97044139f3aa33d2d1
Author: Michael Stack <st...@apache.org>
Date: Thu Mar 18 23:51:49 2010 +0000
HBASE-2283 row level atomicity
commit 2163795ff6eb868425e1c16d5cefbcf3859cb4c9
Author: Michael Stack <st...@apache.org>
Date: Fri Mar 26 17:38:40 2010 +0000
HBASE-2340 Add end-to-end test of sync/flush
commit 63276ee240a9c39e690990213657984d764cb15b
Author: Michael Stack <st...@apache.org>
Date: Sun Mar 28 05:26:41 2010 +0000
HBASE-2359 WALEdit doesn't implement HeapSize
commit dfe47eaa91e441a1a4a337f787ee1897aed5b0b2
Author: Michael Stack <st...@apache.org>
Date: Sun Mar 28 05:05:22 2010 +0000
HBASE-2338 log recovery: deleted items may be resurrected
commit 2a5618cfe034a2c666869bb284e8e15384b5e10a
Author: Michael Stack <st...@apache.org>
Date: Thu Apr 1 06:42:31 2010 +0000
HBASE-2338 log recovery: deleted items may be resurrected;
2nd attempt...
> We all agreed to work on and commit some changes which
> produce more than an incremental release, something in
> between a fork and an incremental release if I can be a
> little cute about it. We are walking back a little from that
> now that a release vetted on (an also vetted) HDFS-200 is a
> month or two away, so we can get something out the door now
> that fixes the warts in 0.20.3.
>
> I would personally prefer a 0.20.4 release that does not
> depend on having the patched version of Hadoop jars
> included, since Hadoop 0.20.2 does not have 200 or 826, and
> our next release will target it.
