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

Add Ruby 2.2.9 to Circle and clarify support. #1077

Merged
merged 2 commits into from
Jan 30, 2018
Merged

Conversation

nickcharlton
Copy link
Member

@nickcharlton nickcharlton commented Jan 26, 2018

@nickcharlton nickcharlton force-pushed the nc-ruby-support branch 2 times, most recently from e8b6864 to 4e51e2b Compare January 26, 2018 13:17
Copy link
Collaborator

@pablobm pablobm left a comment

Choose a reason for hiding this comment

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

Looks sensible. Do we expect to remove 2.2 when it reaches end of life?

@nickcharlton
Copy link
Member Author

That's my thinking.

The problem I foresee is that the combination of Ruby EOL, Rails versions and people's actual deployments never really line up perfectly …but also neither will we in keeping track here.

Copy link

@geoffharcourt geoffharcourt 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 we support Rails 4.2.0, Ruby 2.2 seems like it's a necessary version.

LGTM

@nickcharlton nickcharlton merged commit 6bfc705 into master Jan 30, 2018
@nickcharlton nickcharlton deleted the nc-ruby-support branch January 30, 2018 09:41
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.

3 participants