Page History

...

RCs should be made available in succession until the community is satisfied that the RC in question is of release quality. The RC that finally makes the cut as the release should be used as it was originally built so the RCs will be named as if they were the final release. This means that we have a few technical issues to resolve:

• TODO We need a staging artifact repository where the RCs can be placed so that failed RC attempts don't pollute a release artifact repository
• TODO We need a reliable way of moving the successful RC from the staging repository to the release repository. This is an intended feature for the Repository Manager but we may need a stop-gap solution until the Repository Manager is ready for production use.

...

The use of the svnmerge script to help pick off the revisions to merge.

Useful links

[http://www.asterisk.org/developers/svn-branching-merging

]
[http://www.reactos.org/wiki/index.php/Best_practices_for_working_with_branches

]
[http://svn.apache.org/repos/asf/httpd/httpd/trunk/VERSIONING

]
[http://svn.collab.net/viewcvs/svn/trunk/contrib/client-side/

]
\[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/index.htm