Skip to content
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.

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

Improve EOL schedule for Ruby versions #2965

Closed
hsbt opened this issue Jan 20, 2023 · 4 comments
Closed

Improve EOL schedule for Ruby versions #2965

hsbt opened this issue Jan 20, 2023 · 4 comments

Comments

@hsbt
Copy link
Member

hsbt commented Jan 20, 2023

I'd like to improve EOL schedule each Ruby versions like:

We have a machine-readable data for this at https://github.com/ruby/www.ruby-lang.org/blob/master/_data/branches.yml.

@unak
Copy link
Member

unak commented Jan 20, 2023

The information I think users need is:

  • Clarification of Ruby's maintenance schedule principles
    • Stable version with new teeny will be released every December
    • Each teeny is scheduled to move to the security maintenance phase from April two years after the initial release of it
    • The security maintenance phase will last for 1 year, after which it will be EoL
  • A cool chart showing the above for each specific version

@gotoken
Copy link
Member

gotoken commented Jan 25, 2023

#2970 should fulfill all unak's advice. I prepared a simple benchmark. I'm not sure if the dates in _data/branches.yml for the commits are accurate, so I would appreciate it if you could check. Thanks.

@JuanitoFatas
Copy link
Member

By the way, there is an existing service called Ruby | endoflife.date that has EOL schedule for Ruby.

CleanShot 2023-01-30 at 10 11 28@2x

@hsbt
Copy link
Member Author

hsbt commented Mar 1, 2023

We can improve this at https://www.ruby-lang.org/en/downloads/branches/. I'll close this.

@hsbt hsbt closed this as completed Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants