Release Procedure

1. Make sure source is up to date

• % git pull

2. Make sure there are no pending changes

• % git status

3. Do a clean test

• % ant clean test

4. Take one of two paths, depending on whether this is a new minor version or not

• If this is a new minor version, then create a branch for it
• % git checkout -b version-2.5
• If this is a bug fix release, then switch to the minor version branch and merge in all changes from master
• % git checkout version-2.5
• % git merge master

5. Edit version numbers to be 2.5.0 (i.e., without SNAPSHOT)

• % bbedit pom.xml
• % bbedit build.properties

6. Build the release

• % ant clean install

7. Commit your changes to your local git repository and the remote git repository

• % git commit -am "Releasing version 2.5.0"
• % git push -u origin version-2.5

8. Push the jar to conjars

• % scp -i ~/.ssh/id_rsa_bixolabs pom.xml build/cascading.solr-2.5.0.jar [email protected]:

9. Test the uploaded jar [optional]

• % rm -rf ~/.m2/repository/com/scaleunlimited/cascading.solr/2.5.0
• modify a project that uses cascading.solr to use version 2.5.0
• build and verify the project

10. Tag the release

• % git tag -am "Tagging version 2.5.0" 2.5.0
• % git push --tags

11. Fix up version numbers (assumes releasing from a branch)

• Revert the version (e.g. back to 2.5-SNAPSHOT)
• % bbedit pom.xml
• % bbedit build.properties
• Push the new minor version number
• % git commit -am "Reverting to SNAPSHOT version number after releasing from branch"
• % git push
• If you created a new branch, update the master's version to the next one (e.g., 2.6-SNAPSHOT)
• % git checkout master
• % bbedit pom.xml
• % bbedit build.properties
• Push the new minor version number
• % git commit -am "Bumping master version after creating branch for previous one"
• % git push

12. Send out email to Cascading list, internal users