Comment 13 for bug 500072
Revision history for this message
| Ian Clatworthy (ian-clatworthy) wrote | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
To explain my comment re "reports", my vision is for the bottom half of the repository view and the bottom half (third?) of the status view to show useful "reports". Right now:
* the repo view has 3 of these: Recent History, Local Changes and Missing Revisions
* the status view has one: Submit Delta.
The Submit Delta report only appears for feature branches too.
Looking forward, the idea is that the user will be able to say, for each report, whether they want to see it on each view or not. So if you want to see Recent History on the status view, that will be easy to configure. Furthermore, developers will be able to add their own reports defined in XML. The decision as to where to render those custom reports, if anywhere, will be left to the user to configure. Make sense?
I'm curious about the frequent use of branches with 1000s of changes. What sort of data were you managing?