Skip to content

Commit 6446fa3

Browse files
committed
Update release instructions for new system
1 parent e9bdf30 commit 6446fa3

1 file changed

Lines changed: 9 additions & 3 deletions

File tree

README.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -353,11 +353,17 @@ package and push the .jar every time a commit changes a source file).
353353

354354
## Releasing
355355

356+
Releasing must be done by users authorized to push to the `org.jruby` group ID on https://central.sonatype.org and to push the `jruby-rack` gem to https://rubygems.org.
357+
356358
* Make sure auth is configured for "central" repository ID in your `.m2/settings.xml`
357-
* Update the version in `src/main/ruby/jruby/rack/version.rb` to the release version
358-
* `./mvnw release:prepare`
359-
* `./mvnw release:perform` (possibly with `-DuseReleaseProfile=false` due to Javadoc doclint failures for now)
359+
* Update the versions in `pom.xml` and `src/main/ruby/jruby/rack/version.rb` to the release version
360+
* Commit the version update locally
361+
* Run `./mvnw deploy -Prelease` to build, sign, and push all artifacts to Maven Central staging
362+
* Once verified by Maven Central, authorize the deployment of the release on https://central.sonatype.org
360363
* `rake clean gem SKIP_SPECS=true` and push the gem
364+
* Tag the release version in git
365+
* Update the versions again to the next dev version (`-SNAPSHOT` for the Maven artifact in `pom.xml` and `.SNAPSHOT` for the gem in `version.rb`)
366+
* Push all commits and tags to GitHub
361367

362368
## Adding testing for new Rails versions
363369

0 commit comments

Comments
 (0)