-
Notifications
You must be signed in to change notification settings - Fork 141
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
Release 3.0.0.pre.1 #263
Release 3.0.0.pre.1 #263
Conversation
Ruby 2.7 is tagged End of Life (not even security maintanence) since this month. We (Highline) traditionally try to maintain compatibility with old rubies. But rubies bellow 2.7.1 lack "io/console" or they have incompatibilities. (as discussed in PR #259) So, this EOL of 2.7 signal to us that is time for us to move on. People relying on old versions of Highline will probably face no problem with it. But we will be free to start removing old code that is necessary only for retrocompatibility in newer versions.
560b1d7
to
16a8ced
Compare
thanks @abinoam |
@abinoam do you have a timeline or outstanding issues before releasing the 3.0.0 final cut? |
Hi @kbrock thanks for pinging me. I was drowned by some personal things (nothing serious). But those things were taking a lot of my "free" time. The good news are that I'll probably be more free from this month on. And your message made me put this on priority. |
Basically I want to recheck all the code for parts that are there only for retro compatibility with old rubies. |
There sure is not enough time out there, for sure. |
Note to self: jruby/jruby#3181 |
does this mean that going towards |
Ruby 2.7 is tagged End of Life (not even security maintenance) since this month.
We (Highline) traditionally try to maintain compatibility with old rubies.
But rubies bellow 2.7.1 lack "io/console" or they have incompatibilities.
(as discussed in PR #259)
So, this EOL of 2.7 signal to us that is time for us to move on.
People relying on old versions of Highline will probably face no problem with it.
But we will be free to start removing old code that is necessary only for
retro compatibility in newer versions.
First we're gonna release a 'pre' gem. So we have more time to testing and packing in more changes before the final release.
Question#validate
#258 / I Possible to accept multiple selections with.in
and.default
? #246 - Add validation class support (@abinoam, issue by @Joshfindit)#valid?
.in
to work with array #249 - Fix Array validation in Question#in (@abinoam, issue by @esotericpig)