Misc #9219

Policy Announcement for All Versions

Added by Terence Lee over 1 year ago. Updated 9 months ago.

[ruby-core:58870]
Status:Closed
Priority:Normal
Assignee:Zachary Scott

Description

Once the policy has been decided for any released branch, there should be an announcement made on www.ruby-lang.org NEWS in the actual release announcement. We should aim to announce along with the 2.1.0 release announcement.

History

#1 Updated by Zachary Scott about 1 year ago

  • Status changed from Open to Assigned
  • Assignee set to Zachary Scott

This proposal was accepted, during the release of 2.1.0 we will announce our maintenance policy plans.

#2 Updated by Zachary Scott about 1 year ago

  • Category changed from Project to doc

#3 Updated by Zachary Scott about 1 year ago

This is actually pretty much a duplicate of #9215, the only difference is we still don't have an anticipated maintenance window for 2.0.0

Perhaps nagachika-san could comment on this, and we could formally introduce a tentative maintenance plan for that branch.

#4 Updated by Yui NARUSE about 1 year ago

About 2.1 and 2.0.0 is discussing now.

#5 Updated by Yui NARUSE about 1 year ago

Issue #9219 has been updated by Yui NARUSE.

About 2.1 and 2.0.0 is discussing now.


misc #9219: Policy Announcement for All Versions
https://bugs.ruby-lang.org/issues/9219#change-44274

  • Author: Terence Lee
  • Status: Assigned
  • Priority: Normal
  • Assignee: Zachary Scott
  • Category: doc
  • Target version: 2.1.0 ---------------------------------------- Once the policy has been decided for any released branch, there should be an announcement made on www.ruby-lang.org NEWS in the actual release announcement. We should aim to announce along with the 2.1.0 release announcement.

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

#6 Updated by Hiroshi SHIBATA about 1 year ago

  • Target version changed from 2.1.0 to current: 2.2.0

#7 Updated by Zachary Scott 9 months ago

  • Status changed from Assigned to Closed

We've already made maintenance announcements for 1.9.3 and only recently changed maintainers for 2.0.0.

In this case, I don't think we need an open-ended ticket. We should consider making an announcement regarding 2.0.0's lifecycle closer to the EOL of 1.9.3.

Also available in: Atom PDF