Release Engineering 2.1

see also version independent topics.

https://bugs.ruby-lang.org/issues/8288

Ruby 2.1.0

• Status: developing
• release manager: naruse
• ABI Version: 2.1.0

NOTE: this schedule is DRAFT

• Declared next version is 2.1.0
  • done at 2013-02-23
• bump version.h
  • done at r39482, 2013-02-25
• RubyKaigi
  • 2013-05-30 - 2013-06-01
• Call for Feature Proposals
  • announce: 2013-06-28
  • ruby:DevelopersMeeting20130727Japan
  • ruby:DevelopersMeeting20130831Japan
• preview 1
  • scheduled: [ruby-core:57313] 2013-09-23
• Dead line of adding big feature
  • scheduled: 2013-09-30
  • can't introduce big feature after this
• reviewing features: 1 month
• preview 2
  • released: 2013-11-23
  • feature freeze
• bug fix only: 1 month
• Release Candidate
  • released: 2013-12-21
  • create ruby_2_1_0 branch
  • don't fix after this unless a critical bug is found
• fix only critical bugs: 2 week
• Release
  • scheduled: 2013-12-25

Notable changes

• VM (method cache)
• RGENGC
• refinements
• syntax
  • Decimal Literal
  • Frozen String Literal
  • def's return value
• Bignum
  • GMP
• String#scrub
• Socket.getifaddrs
• new Rubygem

Checklist for Releasing

• without baseruby
• ruby-build
• cross compile

FAQ

Why RC is only once

• naruse thought RC should be Literally Release Candidate.

Can I commit to ruby_2_1_0?

No. Without release manager's explicit permission, you can't backport.

ref: https://wiki.freebsd.org/Releng/9.0TODO