History

HowToRelease

see also HowToReleaseRuby193 for patch release

How To Release new version

  1. Ensures make test and make test-all are ok.
    • inside/outside of $(srcdir)
    • On some platforms
    • check Ruby CI.
  2. bump version.h (see r44417)
  3. Notify the distributors that a new release will be out so that they can prepare their package.
    • currently, only akira, the maintainer for ruby on debian project.
  4. Tags a new tag for the revision which will be released.
    • svn cp -m "tags trunk@r43806 as v2_1_0_preview2" svn+ssh://svn@ci.ruby-lang.org/ruby/trunk svn+ssh://svn@ci.ruby-lang.org/ruby/tags/v2_1_0_preview2
  5. make dist RELNAME=relname
    • This generates tarballs and outputs checksums for them.
    • relname is 1.9.3-p286 or 2.0.0-preview1.
    • see also tool/make-snapshot
  6. Unpacks the archives, builds a ruby from them, and ensures make test and make test-all are ok.
    • without already installed ruby
  7. Send the archives to platform maintainers.
    • Ensures they can successfully build a ruby and make test and make test-all are ok.
  8. Uploads it into ftp.ruby-lang.org
    • at /home/ftp/pub/ruby/1.9/
    • symlinks at /home/ftp/pub/ruby/
    • see tool/release.sh
  9. Writes the release announce.
  10. Rotate NEWS and ChangeLog on trunk (see r44427)

How To Release 2.1.1

  1. Ensures make test and make test-all are ok.
    • inside/outside of $(srcdir)
    • On some platforms
    • check Ruby CI.
  2. bump version.h (see r44442)
  3. Tags a new tag for the revision which will be released.
    • backport tag
  4. login to ftp.ruby-lang.org
  5. make dist RELNAME=relname
    • This generates tarballs and outputs checksums for them.
    • relname is 2.1.1
    • see also tool/make-snapshot
  6. Unpacks the archives, builds a ruby from them, and ensures make test and make test-all are ok.
    • without already installed ruby
  7. run tool/release.sh
  8. Writes the release announce.
  9. Rotate NEWS and ChangeLog on trunk (see r44427)
  10. bump version to 2.1.2 (r45163)

How To Release security fix

How To Be A Release Manager

  1. get an account on carbon
    • the account is a member of group 'ftp' and 'staff'
    • get the password of the account to use sudo