[RELENG-9] Version bump script fails when there is 4 digit versioning Created: 12/Mar/15 Updated: 19/Oct/17 Resolved: 26/Aug/15 |
|
| Status: | Resolved |
| Project: | releng |
| Component/s: | Autorelease |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Thanh Ha (zxiiro) | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 2831 |
| Description |
|
VTN project has 4 digit versioning and the existing versionbump script seems to fail to properly version bump these scheme. |
| Comments |
| Comment by Stephen Kitt [ 13/Aug/15 ] |
|
This is likely to cause problems with Maven version comparisons: in the default scheme the first three fields are compared numerically, but anything after that is compared alphabetically... Wouldn't it be better to switch VTN to three-component versions? |
| Comment by Thanh Ha (zxiiro) [ 13/Aug/15 ] |
|
(In reply to Stephen Kitt from comment #1) Ideally yes but I don't believe the TSC mandates a project versions their project in any particular way so ultimately it is up to them. We could try to convince them. |
| Comment by Hideyuki Tai [ 26/Aug/15 ] |
|
The VTN project have changed four-number version numbers to three-number version numbers. https://git.opendaylight.org/gerrit/#/c/25649/ (master) Now, all version numbers in the VTN project is three-number. |
| Comment by Thanh Ha (zxiiro) [ 26/Aug/15 ] |
|
(In reply to Hideyuki Tai from comment #3) Thanks Hideyuki. I'll close this bug as WONTFIX since VTN was the only project that had 4 digits. |