-
Notifications
You must be signed in to change notification settings - Fork 779
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-dev definition #2311
Add ruby-dev definition #2311
Conversation
* Currently the same as 3.3.0-dev but that name changes every year, so this makes it easy to install ruby dev/master.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like that there is a definition that always means "Ruby master", but it also might be slightly confusing that we now have to identical definitions: ruby-dev
and 3.3.0-dev
(or whichever the latest MAJOR.MINOR version Ruby is at).
Could we set up ruby-dev
as an alias that resolves to the latest MAJOR.MINOR.0-dev
definition? I've also been meaning to set up ruby
as an alias for the latest Ruby stable version, so it can be used as an easy way to install latest Ruby.
I think it's best to keep them separate, because e.g. once Ruby 3.3.0 is released the 3.3.0-dev file should be updated to use the Specifically, ruby-dev should never need to change and always use master, while n.n.n-dev changes at least once. There is also the question of whether it makes sense to even have e.g 3.4.0-dev before 3.4 is released, but that can be considered separately. |
Aside: the naming 3.2.0-dev is pretty strange given there is 3.2.2 now, but 3.2.0-dev is newer than 3.2.2. |
Agreed. Maybe that's a naming scheme we could go for |
+1 How about this transition?
|
Sounds good, I'll merge this then. |
That all sounds great, thank you.
Should the legacy names |
I think it's very rare to use X.Y-dev after X.Y.0 is out, so I think it'd be fine to break that, and if it proves to affect too many users then we could do some kind of aliasing. |
I always wondered why this is missing, well, let's add it.
cc @nirvdrum who mentioned there is some non-trivial workaround at Shopify due to the lack of this.