Skip to content

We announce approved maintenance policy window for Ruby #602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 11 commits into from
Closed

We announce approved maintenance policy window for Ruby #602

Changes from all commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
344c649
We announce approved maintenance policy window for Ruby
Jan 13, 2014
a5933f3
Clarify who "we" is
Jan 20, 2014
3c9f57d
Define how Ruby versions are supported
Jan 20, 2014
4bb3b6e
Should be every 2-4 months for TEENY release, clarify about backports to
Jan 20, 2014
fed16d1
Describe maintenance ability for 2 simultaneous stable versions
Jan 20, 2014
c6e68c9
List maintenance policy team members and approval process for policy
Jan 20, 2014
c80634d
Make decision clear, what we will discuss.
Jan 31, 2014
8ebd207
Rephrase supported version scheme and simply detailed policy section …
Jan 31, 2014
58254fb
Users don't care about what branch we backport to.
Jan 31, 2014
31f8b1e
Separate maintenance types into groups to clearly explain policy.
Jan 31, 2014
dd25efa
Add heading to final section and note regarding this policy as our be…
Jan 31, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions en/news/_posts/2014-01-13-approved-maintenance-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
layout: news_post
title: "Approved Maintenance Policy"
author: "zzak"
translator:
date: 2014-01-13 03:28:19 UTC
lang: en
---

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

For context, you should read our recent policy changes for [semantic versioning](/en/news/2013/12/21/semantic-versioning-after-2-1-0).

Given the current supported version scheme, the ruby-core policy is as follows:

* `MINOR`: With "best effort" goal with at least 6 months and at best 3 years or after two newer `MINOR` releases.
* `TEENY`: Will be released approximately every 2-4 months.

During this time, the ruby-core team will support maintained versions of Ruby in the following groups:

## Bug fix

For general bug fixes, we will support the latest release until a decision is made to end support.

## Security fix

After bug fix period has ended, security maintenance will continue until the version is End-of-Life.

## End-of-Life and Unsupported Versions

Once a version is End-of-Life, it's your responsibility to deal with bugs and security fixes. An approved commercial party may be able to accept responsibility of maintaining an End-of-Life version.

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.

## Your encouragement is appreciated

Please understand that we want to focus on improving Ruby for future releases and encourage the use of the latest stable release. The longer a version lives the harder it becomes to maintain it. With the limited resources of ruby-core, it makes it hard for us to maintain more than 2 stable versions at a time.

We're going to give our best effort to support this policy in order to provide a sustainable upgrade path to modern versions of Ruby.

Thank you for your support as we continue to provide a stable and healthy Ruby.