Actions
Bug #22767
closednot assigning dev numbers correctly since 3.1.0
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Deployment
Target version:
Story points:
-
Updated by Peter Amstutz 9 days ago
- Position changed from -950326 to -950314
- Status changed from New to In Progress
Updated by Peter Amstutz 9 days ago
22767-dev-version-assignment @ 49f2256a64a499b571e163a33464a4c14d639082
The background on this is that the development-3.0.0
tag was the least-bad solution I could come up with the get the version-at-commit.sh
script to start generating version numbers for 3.0.0, because given X.Y.Z version numbers the logic only knew how to generate X.(Y+1).0~dev
or X.Y.(Z+1)~dev
and would have continued to make 2.8.0~dev versions forever. Unfortunately, the 3.1.0 release revealed that the development-3.0.0 tag came with its own bug, but the above branch should do the right thing now.
Updated by Peter Amstutz 2 days ago
- Target version changed from Development 2025-04-16 to Development 2025-04-30
Updated by Peter Amstutz 2 days ago
- Target version changed from Development 2025-04-30 to Development 2025-04-16
Actions