Can versions be allowed to go backwards?
Closed this issue · 1 comments
Our example docker images are being generated starting with 7 because the versions of our tags are incrementing from 7.0.x. But this is confusing as our pom says 1.0.0:
AlfrescoArchive/example-runtime-bundle@ae6ec8f#diff-600376dffeb79835ede4a0b285078036
The reason seems to be that in the past our pom.xml did say 7.0.0 and we then moved our version number down. However we can't go back to 1.0.x as jx-release-version won't let us go backwards.
What can we do on this? Would a non-semantic version be possible? The trouble is we can't really move our versions forwards as they've already gone further forwards than we should've let them go.
We want to support different release trains from the same GitHub repo.
- Create spring boot QuickStart
- develop branch -> Pom -> 1.1.0-SNAPSHOT
- 1.0.x branch -> Pom -> 1.0.0-SNAPSHOT
When building the two pipelines
we should get the right release number for both.