Bug 69369 - BUGZILLA: better version drop-down menu chronological order
Summary: BUGZILLA: better version drop-down menu chronological order
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: WWW (show other bugs)
(earliest affected)
Hardware: Other All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2013-09-15 05:52 UTC by tommy27
Modified: 2013-09-15 15:58 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description tommy27 2013-09-15 05:52:33 UTC
actually the versions:
"inherited from OOo"
"Master old -3.6"
are listed at the bottom of the list.

I think that they should follow the chronological order and be placed respectively:

"inherited from OOo" --> top of the list before 3.3.0
"Master old -3.6" --> in the middle between 3.5 Daily and 3.6.0 alpha1

by the way I think that "3.5 Daily" can be safely removed from the list as well since it's the only "Daily" version of any branch left and 3.5.x is EOL.

one could argue if "Master old -3.6" can already be deleted as well for the same reasons.

regarding the "unspecified" version I think it's right place is at the end of the list like it's now.
Comment 1 tommy27 2013-09-15 05:55:49 UTC
adding Joel Madero to CC list.

who is the "expert" for BUGZILLA issues? nobody is specifically credited for this in the wiki page https://wiki.documentfoundation.org/FindTheExpert

Rob Snelders is in charge for the BSA not for the FDO, so I wonder who's the FDO "janitor"...
Comment 2 Joel Madero 2013-09-15 15:57:02 UTC
This isn't our bug - it's an issue with FDO which we don't own, it's not on our infra so we can't do anything about it. For now closing as WONTFIX but in the future we may have some control over these types of things.

Thanks for the report
Comment 3 Joel Madero 2013-09-15 15:58:20 UTC
BTW - I'm one of the people with the most rights from TDF on FDO and I don't have the ability to change the order. It'd take the FDO devs to change the code - they are incredibly overworked and unlikely to tackle this. Like I said, in the future this might change as we may have more control over our bug tracker