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 to 2.3 #2794

Closed
wants to merge 1 commit into from
Closed

Upgrade ruby to 2.3 #2794

wants to merge 1 commit into from

Conversation

jtapia
Copy link
Contributor

@jtapia jtapia commented Jul 6, 2018

Issue: #2743

Ruby 2.2 has passed its end of life. This changed the required ruby versions to Ruby 2.3

@jtapia jtapia changed the title Update ruby to 2.3 Upgrade ruby to 2.3 Jul 6, 2018
Copy link
Member

@kennyadsl kennyadsl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 just left a comment for the readme

brew install ruby sqlite3 imagemagick
gem install rails
```

See more detailed installation information below.

### Upgrade Ruby on macOS
### Upgrade Ruby on macOS

If you run macOS Sierra or an older OS, you system's version of Ruby will need
to be upgraded from 2.0.x to 2.2.2 or newer. You can check what version of Ruby
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we should also change this line?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done, thanks

Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As long as Rails 5.1 allows >= 2.2.2 we should as well. There is no reason to not support 2.2 even if it’s EOL. It’s the stores decision to make, not ours. It’s the same with outdated gems. We still allow them. The same is true for Ruby versions. Stores can and should be able to decide which Ruby version to run.

@BenMorganIO
Copy link
Contributor

I'm 👎 on this as well. Because if a store isn't able to reach 2.3, we could leave them out as Solidus goes forward.

@ericsaupe
Copy link
Contributor

I agree with @tvdeyen we should support whatever the Rails versions are supporting.

@BenMorganIO
Copy link
Contributor

BenMorganIO commented Sep 13, 2018

@ericsaupe Also, 2.3 minimum would go against Solidus principles, which is to make upgrades easier for users. If we remove a version of ruby, we need a practical reason for it. Mainly, I think, it's when that version of ruby stops working with the minimal version of Rails we're permitting. So, if Rails 5.2 supports 2.2, which I think it does, we should keep it.

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

Successfully merging this pull request may close these issues.

5 participants