As promised, I created the 1.7.x branch in r1145993. I hope to have a
beta from the branch posted in a couple of hours. A couple of notes:
This probably goes without saying, but the branch is a release
stabilization branch, so changed which are merged to the branch need
to be reviewed an voted on in the STATUS file (or at least recorded
there after IRC or dev@ votes) before they'll be merged to the branch.
I don't have to be the person who does the merging, but my OCD
usually doesn't mind. :) All code changes require 3 +1s (and no
vetoes) before merging, and I promise that *I* won't merge if an item
has been in STATUS less than 24-hours, to ensure interested folks get
a chance to review it.
Remember the following exceptions to the 3 +1s rule:
* Documentation and other non-code fixes can go straight to the
branch, without going through STATUS (please cite the "obvious fix"
rule)
* Things in tools/ and the bindings only need a single +1 and at
least another +0.
* Translations (as is currently the case)
If your fix has several commits, please arrange them in one group in
STATUS, so they can be reviewed together.
As soon as we release the first RC, the stabilization period will
start. Any critical bugfix will need to restart that stabilization
period as a new release candiate is prepared. There may also be
subsequent release candidates during the soak period to pick up any
non-critical fixes. A final RC will be rolled shortly before the
final release. If you believe a bug (and the corresponding fix) is a
critical issue, please note that in the STATUS file.
You can read all about release stabilization here:
http://subversion.apache.org/docs/community-guide/releasing.html#release-stabilization
Thanks for the hard work, and there will be a release process quiz next week.
-Hyrum
Received on 2011-07-13 15:22:06 CEST