Release Engineering 2.2

see also version independent topics.

• Meta Ticket #10553

Ruby 2.2

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

Schedule

• Declared next version is 2.2
• bump version.h
  • done at r44436, 2013-12-26
• ruby:DevelopersMeeting20140214Japan
• ruby:DevelopersMeeting20140418Japan
• ruby:DevelopersMeeting20140517Japan
• Call for Feature Proposals
  • announce: 2013-06-26
• ruby:DevelopersMeeting20140618Japan
• ruby:DevelopersMeeting20140726Japan
• ruby:DevelopersMeeting20140904Japan
• RubyKaigi
  • 2014-09-18 - 2014-09-20
• preview 1
  • scheduled: 2014-09-18
• Dead line of adding big feature
  • scheduled: 2014-09-30
  • can't introduce big feature after this
• reviewing features: 1 month
• ruby:DevelopersMeeting20141029Japan
• RubyWorld Conference 2014-11-13,14
• RubyWorld Conference 2014-11-17,18,19
• ruby:DevelopersMeeting20141126Japan
• preview 2
  • 2014-11-28
  • feature freeze
• bug fix only
• Release Candidate
  • scheduled: 2014-12-XX
  • create ruby_2_2_0 branch
  • don't fix after this unless a critical bug is found
• fix only critical bugs: 2 week
• Release
  • scheduled: 2014-12-XX

ToDo

• #9113
• #8257

Notable changes

• new RubyGems

Checklist for Releasing

• without baseruby
• ruby-build
• cross compile

FAQ

Can I commit to ruby_2_2?

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