A lightweight method is to create a TAG in SVN for each RC and also for ALPHA
and BETA, and then cut a branch when releasing 4.0.0
Regarding CHANGES, it should have full-blown sections for 4.0.0-ALPHA and
4.0.0-BETA, but for e.g. 4.0.0-BETA-RC2 it should be enough with a marker line
in
I put a new changes entry after the alpha under the 4-Alpha release in
CHANGES.txt for Solr.
I missed the discussion if there was one, but if we plan to have a CHANGES
section for alphas and betas, let me know, and I'll move that entry when we
start a new section.
We should add the next
I think thats fine: basically the reason the RC has a revision # is
for purposes like this.
If the alpha vote succeeds, I would (myself, personally, my
responsibility) simply move this stuff under BETA in the branch.
The alternative is to actually make a proper branch for the beta, but
I
