hbase-dev mailing list archives

Hi,
As mentioned in the previous thread [1], for 1.0.0RC0, I've created
branch-1.0 by forking branch-1. Now we have:
master
branch-1
branch-1.0
0.98
0.94
The reasoning and some guidelines are in [2].
In short, branch-1 has a pom version 1.1.0-SNAPSHOT and is the target
branch for 1.1.0 release now. branch-1 now can be used to commit patches
against 1.1.0 release. Please only commit patches that do not break
compatibility requirements as outlined in [3].
branch-1.0 has a pom version 1.0.0-SNAPSHOT now, and 1.0.0RC0 will be from
this branch (delayed to tomorrow to see whether we can get HBASE-12511 in).
Please do not commit anything in this branch until the RC.
I've also changed the jenkins build https://builds.apache.org/job/HBase-1.0/
to run the build from branch-1.0. I've created another jenkins build for
1.1, it is at https://builds.apache.org/job/HBase-1.1/ , and it builds from
tip of branch-1.
Also there are now, 1.0.0, 1.0.1 and 1.1.0 jira labels for the upcoming
releases. Please mark the jira with fixVersion at the commit time
accordingly.
[1]
https://mail-archives.apache.org/mod_mbox/hbase-dev/201412.mbox/%3CCADcMMgH6y=8Umz-UvjK0fdYko1cGtZ_GLXapP9vmCUu2Jg45wA@mail.gmail.com%3E
[2]
https://docs.google.com/document/d/1cVLxtc9icbtina2hrJCSaHLaZVeg_XfYKXMBaYvI3aA/edit#heading=h.pwj5kzppqac2
[3] https://hbase.apache.org/book/upgrading.html#hbase.versioning
Cheers,
Enis