Comment 6 for bug 249021
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 249021] Re: Branch +merges page shows reviews newest-first, should be oldest-first | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
On Fri, 2010-03-05 at 16:53 +0000, Aaron Bentley wrote:
> I don't agree. For the +merges page, showing oldest-first means showing
> ancient merged proposals before showing anything recent active reviews,
> and that is not useful.
That suggests that you want active reviews split out and made visually
distinctive.
Some possibilities:
- sort by status(active, merged, rejected, superseded), age: that should
give the oldest unmerged reviews first on the page.
- have separate regions for each status
- do something else again
-Rob