65317 - Versions should have sortkeys like milestones.

Status: NEW

(Bugzilla :: Administration, task, P3)

Description

[Matthew Tuck [:CodeMachine]]

Versions should have sortkeys like milestones.

Comment 1

[Dave Miller [:justdave]]

Moving to real milestones...

Comment 2

[Hixie (not reading bugmail)]

Taking all Bugzilla 3.0 bugs -- congratulations to MattyT for the triage, it
really was spot on. Note: I may end up pushing some of these bugs back to 3.2,
we'll see. However, I believe all these bugs should just fall out of the 
redesign. Let's hope I'm right!

(Note: I'm also resetting the priority field to "---" so that I can retriage any
that I consider important or likely to be dropped.)

Comment 3

[Matthew Tuck [:CodeMachine]]

When this is implemented, make sure you don't reproduce bug #76157.

Comment 4

[Dave Miller [:justdave]]

The Bugzilla 3 component is going away.  We're going to depend on the Milestones 
for this.  At the time this component was created, we didn't have milestones for 
Bugzilla.

Comment 5

[Matthew Tuck [:CodeMachine]]

Mine for 2.16.

Comment 6

[Dave Miller [:justdave]]

We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.

Comment 7

[Dave Miller [:justdave]]

*** Bug 133039 has been marked as a duplicate of this bug. ***

Comment 8

[Dave Miller [:justdave]]

Taking Jake's bugs...  his Army Reserve unit has been deployed.

Comment 9

[Dave Miller [:justdave]]

Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. 
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)

Comment 10

[Dave Miller [:justdave]]

Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.

Comment 11

[Susan]

(In reply to comment #10)
> Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
> enhancement that hasn't already landed is being pushed out.  If this bug is
> otherwise ready to land, we'll handle it on a case-by-case basis, please set the
> blocking2.20 flag to '?' if you think it qualifies.

Having the option to sort our Product versions will make our job easier becuase I won't receive wasted emails requesting me to add the new version to the product., because the that version is hard to find , because I cannot sort the version numbers numerically.  Are you guys going to add the sortkey feature to EditVersions ?? -- Susan

Comment 12

[Denis Roy]

Susan, be sure to go ahead and vote for this feature using the vote options at the top of the page.

Comment 13

[Olav Vitters]

Note that Bugzilla 3.0 will sort the numbers intelligently. E.g.
2.1 - 2.2 - 2.10 (used to be 2.1 - 2.10 - 2.2). For me this removed all need to have sortkeys.

Comment 14

[Andre Klapper]

Some software projects just don't use a linear versioning scheme, e.g. Maemo has 1.2007.42-18 (week 42 in 2007) which was released after 4.2007.38-2 (week 38 in 2007).
(Yes, I already voted for this bug.)

Comment 15

[Kent Rogers [:mrbball]]

(In reply to Olav Vitters from comment #13)
> Note that Bugzilla 3.0 will sort the numbers intelligently. E.g.
> 2.1 - 2.2 - 2.10 (used to be 2.1 - 2.10 - 2.2). For me this removed all need
> to have sortkeys.
>
This is not true for the Advanced Search form.  If you select a particular
Product, the Versions are sorted by id, not by value (i.e. NOT intelligently).
This can easily be seen by selecting Product=Bugzilla on the BMO Advanced
Search page.

Can anyone explain why the LIST_ORDER in Version.pm is set to 'id', not
'value'?  I don't understand the comment in the source.

I guess sortkeys for versions would be the ultimate solution, but until that
happens, sorting by value seems to make a lot more sense than sorting by id.