Skip to content
Karol Bucek edited this page Sep 17, 2017 · 3 revisions

For contributors, the jruby-rack release process goes something like the following:

  1. 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:

  1. Ensure that release version is correct in pom.xml and mvn install runs clean.
  2. Ensure generated changes to src/main/ruby/jruby/rack/version.rb are checked in.
  3. Tag current release in git: git tag <version>.
  4. Push commits and tag: git push origin master --tags
  5. Build gem: rake clean gem
  6. Push gem: gem push target/jruby-rack-*.gem
  7. 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