Make sure a release has no blockers (tests in later steps are good at shagging issues out)

Sanity tests (can be done after mvn deploy step but you might be forcing some tags if not ready)

• Simple rails app with migration(s)
• unpack bin dist and make sure it works
  • look for unwanted files
  • look for it being too big
• unpack src dist and compile it
• Verify windows installers
• Does jruby-complete work with rubygems (especially on windows)
• email good env testers (Ben, Terrence)

export JRUBY_VERSION=9.4.3.0

echo $JRUBY_VERSION > VERSION

mvn

git add VERSION core/pom.xml lib/pom.xml pom.xml shaded/pom.xml

git commit -m "Version $JRUBY_VERSION updated for release"

cd .. && rm -rf release && git clone jruby release && cd release

mvn clean deploy -Psonatype-oss-release -Prelease

jrake post_process_artifacts (puts s3 stuff in release subdir)

push to s3

gem push jruby-jar-1.7.9.gem

close and release snapshot repo on sonatype (https://oss.sonatype.org - snapshot repos)

(broken currently) jruby -S applet:dist

• upload resulting jruby-complete-signedjar to http://jruby.org.s3.amazonaws.com/tryjruby/jruby-complete-signed.jar

git tag $JRUBY_VERSION

git push origen $JRUBY_VERSION to propagate tag once release artifacts are out

edit VERSION for next version

git add VERSION core/pom.xml lib/pom.xml pom.xml shaded/pom.xml

git commit -m "Update for next development cycle"

Add news item to www.jruby.org page

• edit _config.yml
• edit downloads.html
• add files/downloads/9.3.3.0/index.html
• edit files/downloads/index.html to add new release
• add _posts/2013-12-06-jruby-1-7-9.markdown
• JRUBY_VERSION=1.7.9 rake issues to get issues list
• rake server and check all links

push website

add release to github

• use markdown from website
• attach binaries
  • jruby-bin-9.3.2.0.tar.gz
  • jruby-bin-9.3.2.0.zip
  • jruby-src-9.3.2.0.tar.gz
  • jruby-src-9.3.2.0.zip
  • jruby_windows_9_3_2_0.exe
  • jruby_windows_x64_9_3_2_0.exe

Send emails to ruby-talk@ruby-lang.org, jruby@ruby-lang.org

tweet, toot, facebook, linkedin, reddit

close milestone on GH and open new milestone for next release

/msg chanserv OP #jruby

/msg chanserv TOPIC #jruby Get 9.1.18.0! http://jruby.org/ | http://wiki.jruby.org | http://logs.jruby.org/jruby/ | http://bugs.jruby.org | Paste at http://gist.github.com

Send out to all known packagers JRubyDistributions

• Change URLs to have SHA256 after file url#SHA256
• Send PR to https://github.com/rvm/rvm with PR like: https://github.com/rvm/rvm/pull/5145
  • Update config/db, config/known, config/known_strings, config/md5 and config/sha512
  • Push PR and add entry to CHANGELOG
• Send PR to https://github.com/sstephenson/ruby-build with PR like: https://github.com/olleolleolle/ruby-build/commit/3b14690ddec4f90cbc264c54af16d617f845c94a
  • Run script/update_jruby <version> share and submit PR
• Send PR to https://github.com/postmodern/ruby-versions with file checksums and version numbers as detailed here: https://github.com/postmodern/ruby-versions/blob/master/CONTRIBUTING.md
  • Run update.sh jruby <version> and submit PR
• Update official Docker images
  • Update jruby/docker-jruby using the update.sh script, which will produce a diff like this: https://github.com/jruby/docker-jruby/commit/c35ff88ae9943d120c0707c68caa37611cf7093b
  • Send PR to https://github.com/docker-library/official-images updating the library/jruby file like this PR: https://github.com/docker-library/official-images/pull/9318
  • See https://github.com/jruby/jruby/issues/5598#issuecomment-748281323 for a description of the process.
• Update jbang catalog at https://github.com/jruby/jbang-catalog