Misc #9217: Ruby 1.9.3 End of Life Maintenance Policy

• Status: Closed
• Assignee: usa (Usaku NAKAMURA)

[hone (Terence Lee)]

We need a defined plan for how long 1.9.3 will be maintained for bug fixes and security fixes? 6 months? 9 months? 12 months? timeline?

[vo.x (Vit Ondruch)]

In Red Hat, we are shipping Ruby 1.9.3 as a part of Red Hat Software Collections product. It means that we are going to support Ruby 1.9.3 at least until September 30, 2016 [1]. If the time comes and Ruby 1.9.3 should be EOLed, I am willing to keep Ruby 1.9.3 branch updated as long as we support it in our products (or as long as I'll stay Ruby maintainer in Red Hat).

[1] https://access.redhat.com/site/support/policy/updates/rhscl/

[samkottler (Sam Kottler)]

I think it makes sense to do a 12 month maintenance cycle so people can start upgrading. Although 2.0.0 is nearly a drop-in replacement, it's not that easy for larger apps. 12 months feels like a reasonable amount of time for people to upgrade. Once the first cycle is over then Vit or someone else can take over security backporting based on the conversation we had yesterday.

[zzak (zzak _)]

• Status changed from Open to Closed

1.9.3 will be EOL'd in March 2014

We will announce it officially with the announcement of 2.1.0 release.

Additional 1.9.3 maintenance is depending upon Ruby Association contract extension with usa.

If a third-party commercial organization would like to continue maintenance after this, we can discuss it before EOL.