Opened 13 months ago
Last modified 7 months ago
#199 new defect
Order subprojects BY ID DESC
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Future Release |
| Component: | interface | Version: | |
| Keywords: | dev-feedback | Cc: |
Description
I think that it's better to change the order of the subprojects -> ORDER BY id DESC
This is how it looks like by default: https://skitch.com/juanramondiaz/829xx/osclass-glotpress I think that it will be better this: https://skitch.com/juanramondiaz/829tw/osclass-glotpress
Attachments (1)
Change History (5)
juanramondiaz — 13 months ago
comment:2
juanramondiaz — 13 months ago
You're right, that's because development (trunk) project it's always the same one. I was thinking to rename from development to x.x.x version every time I released one and then create a new project.
comment:3
usermrpapa — 13 months ago
personally, tend to agree with current ordering, but glotpress in general is lacking in hooks/filters compared to WordPress?. Would love to see filters added to things so users can customize for themselves. Have committed a ticket or two myself for such filters, but no dice yet.

In the case of translate.wordpress.org, "Development" is the lowest ID but stays at the top of http://translate.wordpress.org/projects/wp. When we "branch", we create a new project and leave that one. That makes the order as follows:
It's not ideal, but it would be better than this:
Not that GlotPress is necessarily being built around exactly how translate.wordpress.org uses it currently, but it offers a pretty good example of where changing the ORDER BY here can be less optimal.