-
Notifications
You must be signed in to change notification settings - Fork 267
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
Getting valid versions comparison in case of qualifiers (alpha, beta, milestone, rc) #632
Comments
…t in order to prevent more than 7 parameters in methods. Preliminary work before fixing mojohaus#632.
example of actual problem : v3.0, searching next minor, creating upper and lower bounds however versions v4.0 with qualifiers alpha, beta, rc lies before 4.0, this is an expected normal feature ! the problem is 4.0rc lies between 3.1 and 4.0 excluded and that 4.0rc is wrongly declared next minor of 3.1 when its a next major instead ! the bounds created should be 3.1snapshot and 4.0snapshot so that 4.0rc lies after 4.0snapshot and is next major instead of next minor |
… rcs in the same majors when they are. Preliminary work before fixing mojohaus#632.
… rcs in the same majors when they are. Preliminary work before fixing mojohaus#632.
…e than 7 parameters in methods in the next PRs.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
…in the right majors.
Regression after infinity calculus PR ? |
non release versions are now ignored in summary but there in details |
Created #760 |
In this exemple, we can se how RC versions are treated differently from non RC versions, however Activation APIs are from same 2.0 Major and should be treated as such
The text was updated successfully, but these errors were encountered: