Project

General

Profile

Actions

Feature #6881

open

Version numbering sort

Added by SwedishMatch TimerWolf over 13 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Roadmap
Target version:
-
Start date:
2010-11-13
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

This is my first bug report im not sure if it is a bug but

0.1
0.2

1.0
1.1

Works good but if you do

0.1
0.2
0.11

It be a bit wrong

/ Slaktarn


Files

Redmine.png (80.4 KB) Redmine.png SwedishMatch TimerWolf, 2010-11-13 06:00

Related issues

Related to Redmine - Feature #6974: Define manually the versions order in Roadmap (when date isn't defined)New2010-11-25

Actions
Has duplicate Redmine - Feature #7269: Sort versions by version numbers x.y.z{z} instead of alphabeticallyClosed2011-01-10

Actions
Has duplicate Redmine - Defect #28035: Order of versions is not correctly orderedClosed

Actions
Actions #1

Updated by John Yani over 13 years ago

I think, you should use

0.01
0.02
0.11
0.20

If you want to change the version number from 0.1 to 0.01, I think, you can do that.

Actions #2

Updated by Jean-Philippe Lang over 13 years ago

  • Tracker changed from Defect to Feature
  • Subject changed from Roadmap, Version Error to Version numbering sort
  • Priority changed from High to Normal

Versions are sorted by date then by name (alphabetically), so what you describe is not a defect (1.1 < 1.10 < 1.2 is alphabetically correct).
What you expect is some kind of version numbering sort when names looks like x.y where x and y are integers.

Actions #3

Updated by SwedishMatch TimerWolf over 13 years ago

Are it not any way to first sort them after numbering?

/ Slaktarn

Actions #4

Updated by SwedishMatch TimerWolf over 13 years ago

SwedishMatch TimerWolf wrote:

Are it not any way to first sort them after numbering?

/ Slaktarn

Or atlest if that not possibel first store after date and not name to get it right anyways it culd be a workaround

Actions #5

Updated by Ebrahim Mohammadi almost 13 years ago

I don't know of any versioning scheme in which "1.10" is smaller than "1.2". I think this issue deserves a higher priority, or even it could be set as a "defect".

Actions #6

Updated by Go MAEDA about 5 years ago

  • Has duplicate Defect #28035: Order of versions is not correctly ordered added
Actions #7

Updated by Frank Schwarz over 2 years ago

I guess the reason for this ticket not being solved within 10 years is the fact that there is no one-size-fits-all solution.

However, if you would refactor the code for the internal version sort to be extensible, I could help myself with a plugin.

Actions

Also available in: Atom PDF