From: e@...
Date: 2014-02-15T11:59:58+00:00
Subject: [ruby-core:60759] [ruby-trunk - misc #9215] Maintenance Policy for Future Releases (2.1.0 & beyond)

Issue #9215 has been updated by Zachary Scott.


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

> Who are "We"?

Who should "we" be? As an official post on ruby-lang.org, it must refer to ruby-core? Should it read:

The ruby-core team has decided plans for supported maintenance periods of Ruby.

How is that?

> Ruby's versioning policy is not correct "semantic versioning".

So just rephrasing this to:

For context, you should read about our recent changes to the Ruby versioning policy."

Furthermore:

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

> This sentence should be removed.

And:

>> 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

Are both stated to enforce how ruby-core will handle end-of-life responsibly, which is what you suggested before:

> What do you want to say in these paragraph?
> If this is announce, the audience is users.
> They read this, "We want to avoid sudden death".
> "ah, ok... and what ruby-core will do?"

However, I think this paragraph:

> 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.

Could be rephrased to simply:

> When support is discontinued unexpectedly ruby-core will work to support for a reasonable time until it can be End-of-Life, or an approved commercial party is able to accept maintenance of said version.

I want to reinforce what actions we plan to take to handle discontinuation of a version.

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

* 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 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/