Currently on issues.roundup-tracker.org we list the
versions as:

devel
1.0
1.1
1.2
1.3
1.4
1.5

I suggest reversing that so that it is reverse chronological order.
This places the current releases at the top so the most likely to be
used don't require scrolling to use. When we add 1.6 it will
most likely require scrolling to access.

Also do we want to include minor releases 1.5.1 etc?

Does the version Class have an 'order' property? If so, sorting is
easily achieved by setting this appropriately for each item. If not I
suggest we add one instead of coding a custom sort in the templating.

No strong feelings on the minor releases, this is a balance between
usefulness for reproducing something and reporters willing to set the
field...

Hi Ralf:

In message
<1468843314.35.0.493068687318.issue2550918@psf.upfronthosting.co.za> ,
Ralf Schlatterbeck writes:
>Does the version Class have an 'order' property? If so, sorting is
>easily achieved by setting this appropriately for each item.

Yup setting the order column was my plan. That's how devel is sorting
to the top.

>No strong feelings on the minor releases, this is a balance between
>usefulness for reproducing something and reporters willing to set the
>field...

Ok.

Thanks for the feedback.

Order reversed.  Set the order of 1.5 to 100, 1.4 101 etc. with devel
set to 1. That allows 98 or so releases before we have to worry about
renumbering things again.