Issue #9215 has been updated by zzak (Zachary Scott).

Category changed from Project to doc
Status changed from Open to Assigned
Assignee set to zzak (Zachary Scott)

We have decided the following:

* MINOR level versions of Ruby have a "best effort" goal of at least 6 months and at best 3 years.
* TEENY versions will be released approx. every 2-3 months
* Branch maintainers are not obligated to commit 3 years maintenance
* ruby-core as a team is responsible for a proper EOL for each MINOR version

Our main goal is to avoid a sudden death

Assigning this ticket to myself in order to document the approved maintenance plan.


----------------------------------------
misc #9215: Maintenance Policy for Future Releases (2.1.0 & beyond)
https://bugs.ruby-lang.org/issues/9215#change-43556

Author: hone (Terence Lee)
Status: Assigned
Priority: Normal
Assignee: zzak (Zachary Scott)
Category: doc
Target version: current: 2.1.0


In order to support long lived applications better, people need information to make decisions. When someone chooses to use a particular programming language it???s important to know how long something is going to be supported.

For future releases it???d be great if we could provide a formal end of life window upon release. This would allow companies to be able to make decisions on how long something will be supported. For instance, when Ruby 2.1.0 comes out this Christmas, giving an expectation that support will be stopped by 12/25/2015 gives an accurate picture of how much time must be allocated to upgrading, how urgent it will be, or if Ruby is even the right language for the project.


-- 
http://bugs.ruby-lang.org/