Issue #9215 has been updated by Yui NARUSE.


Zachary Scott wrote:
> I've updated the pull request given Martin and narsue's feedback. Please check it.
> 
> https://github.com/zzak/www.ruby-lang.org/blob/future_release_policy/en/news/_posts/2014-01-13-approved-maintenance-policy.md
> 
> My plan is to write a separate document in the redmine wiki for internal policy.


> We've decided our plans for ruby-core supported maintenance periods of Ruby.

Who are "We"?

> For context, you should read our recent policy changes for semantic versioning.

Ruby's versioning policy is not correct "semantic versioning" because Ruby breaks compatibility in minor.
Don't use this word without detailed notes.

> An approved commercial party may be able to accept responsibility of maintaining an End-of-Life version.

This sentence should be removed.

> It's important to recognize the maintainer for each version may decide they can no longer support a version, in which case ruby-core would work to responsibly discontinue the version.

useless sentence

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

* Author: Terence Lee
* Status: Assigned
* Priority: Normal
* Assignee: Zachary Scott
* Category: doc
* Target version: current: 2.2.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/