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

Ruby 2.5 is EOL in March 2021 #853

Open
esoterik opened this issue Nov 21, 2020 · 5 comments
Open

Ruby 2.5 is EOL in March 2021 #853

esoterik opened this issue Nov 21, 2020 · 5 comments
Assignees
Labels
internal issues that are difficult for external contributors to work on tooling-upgrades upgrades to any tooling that we use, including gems

Comments

@esoterik
Copy link
Member

see here, we should update to 2.6 or 2.7 at some point.

@ghost
Copy link

ghost commented Dec 26, 2020

Hi @esoterik, I'm wondering if anyone has taken this on and if not I might want to take a stab at it.

Also, I was excited about our Christmas present and wondering if it would make sense to try and jump straight to 3.0.0? Might future-proof for a bit longer.

@esoterik
Copy link
Member Author

Hi @rgrmrts !

I was planning on working on this in the next few weeks -- I'm anticipating that most of the issues will be with the docker image, which unfortunately uses a private base image, so unfortunately this probably isn't a great issue for external contributors.

I'm a little hesitant to jump to 3.0 so soon, especially because this is a rather old app with quite a few dependencies, but it is exciting!!

@ghost
Copy link

ghost commented Jan 12, 2021

Sure - makes sense! I'm eager to start contributing to EFF projects, so if you have ideas for other areas to jump in please let me know 😉

@esoterik esoterik added internal issues that are difficult for external contributors to work on tooling-upgrades upgrades to any tooling that we use, including gems labels Jan 26, 2021
@esoterik esoterik self-assigned this Feb 3, 2021
@bunnymatic
Copy link

I assume nothing has been done here. Are there deployment restrictions for ruby versions?

@bunnymatic
Copy link

I see now that #920 is up and built on some other probably large upgrade branch so I assume this issue is kind of moot now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal issues that are difficult for external contributors to work on tooling-upgrades upgrades to any tooling that we use, including gems
Projects
None yet
Development

No branches or pull requests

2 participants