-
Notifications
You must be signed in to change notification settings - Fork 13
Release Procedure
Ken Krugler edited this page Jun 6, 2013
·
5 revisions
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. Edit version numbers to be 2.2.0 (i.e., without SNAPSHOT)
% bbedit pom.xml
% bbedit build.properties
5. Build the release
% ant install
6. Commit your changes to your local git repository and the remote git repository
% git commit -am "Releasing version 2.2.0"
% git push
7. Push the jar to conjars
% scp -i ~/.ssh/id_rsa_bixolabs pom.xml build/cascading.solr-2.2.0.jar [email protected]:
8. Test the uploaded jar [optional]
% rm -rf ~/.m2/repository/com/scaleunlimited/cascading.solr/2.2.0
- modify a project that uses cascading.solr to use version 2.2.0
- build and verify the project
9. Tag the release
% git tag -am "Tagging version 2.2.0" 2.2.0
% git push --tags
10. Update the version numbers to be 2.3-SNAPSHOT
% bbedit pom.xml
% bbedit build.properties
11. Push the new version numbers
% git commit -am "Bumping (restoring) version number after release"
% git push
12. Send out email to cascading list, internal users