-
Notifications
You must be signed in to change notification settings - Fork 137
Releasing
Karol Bucek edited this page Sep 17, 2017
·
3 revisions
For contributors, the jruby-rack release process goes something like the following:
- Ensure History.md is updated with latest release information.
update the target version using rake update_version
commit the change and run rake release
which does about:
- Ensure that release version is correct in pom.xml and
mvn install
runs clean. - Ensure generated changes to src/main/ruby/jruby/rack/version.rb are checked in.
- Tag current release in git:
git tag <version>
. - Push commits and tag:
git push origin master --tags
- Build gem:
rake clean gem
- Push gem:
gem push target/jruby-rack-*.gem
- Release jar to maven repository:
mvn -DupdateReleaseInfo=true deploy
optionally (recommended) - update the version after the release to the next development "SNAPSHOT" using rake update_version
again and commit the changes