Issue #9215 has been updated by Yui NARUSE.


* Who is "we"?
* It doesn't define what is "support"
* "at least 6 months and at best 3 years" is the conclusion. it is at leastX years or after two newer release, in my understanding
* "TEENY versions will be released approx. every 2-3 months" should be 2-4 months. it also needs how ruby-core treat older teeny (if this is announce)
* How to finish a release maintenance is essential information. an announcemust have it.

Anyway decisions on Ruby development is based on consensus building.
A decision must be implicitly/explicitly approved by persons concerned in the decision.
Persons concerned in the maintenance policy is naruse, usa, nagachika.
At least you get explicit approval by them. (idealy a comment on redmine orreply to ML)
A meeting is not enough. It means only sharing information)

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

* Author: Terence Lee
* Status: Feedback
* Priority: Normal
* Assignee: Zachary Scott
* Category: doc
* Target version: 2.1.0
----------------------------------------
In order to support long lived applications better, people need informationto 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/