THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Notify developers on the mailing list that you are about to branch a release.
- Update CHANGES.txt to include the release version and date (use Unreleased for the date if it is unknown) and remove Trunk (unreleased changes).
Commit these changes to trunk.
Code Block svn commit -m "Preparing for release X.Y.Z"
Create a branch for the release series:
Code Block svn copygit clone -b master https://svngit-wip-us.apache.org/repos/asf/zookeeper/trunk https://svn.apache.org/repos/asf/zookeeper/branches/.git git checkout -b branch-X.Y -m "Branching for master git push <remote> branch-X.Y releases"
- Update CHANGES.txt to add back in Trunk (unreleased changes).
- Update the default version in build.xml on trunk to X.Y+1.0-SNAPSHOT.
- Update the version number in src/c/configure.ac and src/c/include/zookeeper_version.h to be X.Y+1.0.
Commit these changes to trunk.
Code Block svn commit -m "Preparing for X.Y+1.0 development"
...