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

Upgrade Ruby #1943

Closed
danielbreves opened this issue Nov 4, 2017 · 3 comments
Closed

Upgrade Ruby #1943

danielbreves opened this issue Nov 4, 2017 · 3 comments

Comments

@danielbreves
Copy link

danielbreves commented Nov 4, 2017

Ruby version 2.1.5 is past its end of life and is now unsupported. It no longer receives bug fixes or critical security updates.

See Support of Ruby 2.1 has ended.

@daniellemoorhead
Copy link
Contributor

daniellemoorhead commented Nov 10, 2017

Hi @danielbreves, we all definitely want to upgrade our Ruby version but from what we understand (research about year ago) we're blocked from doing this by the Spree upgrade that is currently (slowly) underway, which would then let us upgrade Rails which would then let us upgrade Ruby.

But looking at the latest information it seems that we can now upgrade to at least version 2.2. But then again, 2.2 is only supported till next March...so do we spend the time upgrading to 2.2 now, or do we focus our efforts on upgrading Spree so we can get Rails and Ruby up to the latest version directly afterwards?

Ping @sauloperez and @lin-d-hop and @oeoeaio and @sigmundpetersen if you have any thoughts to add to this.

@sauloperez
Copy link
Contributor

Just to clarify:

so we can get Rails and Ruby up to the latest version directly afterwards?

we won't be able to get to Rails 5.1 in one go. There are way too many API changes between 3.2 and that version. Not doable IMO. The last upgrade that I did on a Rails app from 3.2 to 4 was already quite painful.

I agree though that it's better to wait for other epics to be solved before tackling the upgrade of the ruby version. Ruby 2.2. doesn't give us much room anyway...

@myriamboure
Copy link
Contributor

Closing as captured in the icebox: https://community.openfoodnetwork.org/t/ensure-that-softwares-and-components-we-depend-on-are-maintained/1247 and dependent on Spree upgrade so will reopen after Spree upgrade to 2.0 is complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants