Actions
Bug #17157
closed
TechniqueVersion ordering algorithm is incorrect
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
We have a (complicated) method that test for version of technique ordering.
It is incorrectly ordering "1.0.1" and "1.0", nor "1.release3" and "1.release10", or "1.3b" and "1.10a". It also doesn't know about a lot of other version things, like "alpha/beta/etc".
I'm not sure about the exact impact, but that ordering is used in a lot of place (in set, for ex). It seems bad to keep it like that.
Also: I wasn't able to understand current algorithm. It seems that it doesn't have a notion of separator after the first one.
Updated by François ARMAND over 4 years ago
- Status changed from New to In progress
Updated by François ARMAND over 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2906
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 5.0.17 to 5.0.18
Updated by François ARMAND over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|9147772c54d47583fa9996fdb87e7def26b13d6b.
Updated by François ARMAND over 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.18 and 6.1.2 which were released today.
Actions