launchpad development|
Size: 2246
Comment:
|
Size: 3478
Comment: missing paren
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''Bug Patch Tracking''' is '''''not''''' one of the main stories under development by the Launchpad [[Bugs|Bugs team]] for what is being called [[/VersionFourDotO|Launchpad v4.0]]. However, after discussions at UDS, based on the amount of work required and the importance of this work for the story of bridging the gap, this story has been taken on in addition to other work. | '''Bug Patch Tracking''' is '''''not''''' one of the main stories under development by the Launchpad [[Bugs|Bugs team]] for what is being called [[/VersionFourDotO|Launchpad v4.0]]. However, after discussions at UDS, based on the amount of work required and the importance of this work for the story of bridging the gap, this story has been taken on in addition to the work being done for [[Bugs/BugHeat|BugHeat]] and [[Bugs/BugQ&A|Bug Q&A]]. |
| Line 3: | Line 3: |
| <<TableOfContents(1)>> | See the [[https://wiki.ubuntu.com/Specs/LaunchpadUpstreamImprovements|spec]] and see Bryce Harrington's [[http://www2.bryceharrington.org:8080/X/Reports/patches.html|example patch report page]] for more about this set of features. |
| Line 5: | Line 5: |
| * Current focus: [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=story-patch-report|story-patch-report bugs]] * Drivers: [[http://launchpad.net/~adeuring|Abel Deuring]] and [[http://launchpad.net/~kfogel|Karl Fogel]] |
|
| Line 6: | Line 8: |
| = Links = | = Status = |
| Line 8: | Line 10: |
| * See the [[https://wiki.ubuntu.com/Specs/LaunchpadUpstreamImprovements|spec]] * See Bryce's [[http://www2.bryceharrington.org:8080/X/Reports/patches.html|patch page]] * Related bugs are tagged with [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=patch-tracking|patch-tracking tag]] |
The best way to see where things stand is probably to look at bugs with these tags: |
| Line 12: | Line 12: |
| = Thoughts = | * the [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=story-patch-report|story-patch-report]] tag * the [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=patch-tracking|patch-tracking]] tag * the [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=patch-tracking-external|patch-tracking-external]] tag |
| Line 14: | Line 16: |
| '' What follows are notes compiled by Deryck from UDS and various conversations around patch tracking.'' | There are also screenshots (such as [[http://launchpadlibrarian.net/38192596/screenshot-2010-01-21_rich_popup.png|this one]]) attached to [[https://bugs.edge.launchpad.net/malone/+bug/506018|bug #506018]]. |
| Line 16: | Line 18: |
| * Tag bugs to be handled in this work with ''story-patch-report'' * To distinguish between any other patch-tracking bug * Will begin work with bug 172507, "show patch icon or notification on the comments page" * need icon from bueno * need new "Patches" portlet for bug page * Are their other ways to incorporate display of patches into search listings better? * Maybe a "bugs with patches" in the "filters" portlet on a project's bugs home page? * maybe add a "show patch age" flag (or whatever it's called), which would show this new column in any listing? * Or show the page age if people select show with patches? |
= Schedule and Plans = |
| Line 26: | Line 20: |
| = Plans = | == 3.1.12 (December, 2009) == |
| Line 28: | Line 22: |
| == 3.1.12 == | * bug 172507, "show patch icon or notification on the comments page" [DONE] * added new icon from beuno to patches on the bug page * bug 344054, "patches and attachments should be listed separately in bug reports" [DONE] * added new "Patches" portlet for bug page * Get agreement about design of +patches page [DONE] * according to spec, bug listing columns for page should be: "bug number, summary, importance, status, package, and patch age" * Deryck and Jorge agreed this would be added to pillars, people, and packages like +bugs to cover various views of this data * Determine how much of the external tracker part of the story can be done [DONE] |
| Line 30: | Line 31: |
| * bug 172507, "show patch icon or notification on the comments page" * Get agreement about design of +patches page * bug listing columns * traversal to get to +patches * Determine how much of the external tracker part of the story can be done == 3.2.1 == |
== 10.01 (January, 2010) == |
| Line 39: | Line 34: |
| * Expose any search additions * Expose in bug listings |
* Expose patches in bug listings and other pages * (maybe) Patches don't only appear as attachments -- they can appear in branches too. E.g., if a bug has a branch attached, autodetect when that branch gets commits and the bug goes to "fix released" or something, then that should count as a patch. |
| Line 42: | Line 37: |
| == 3.2.2 == | == 10.02 (February, 2010) == |
| Line 48: | Line 43: |
| = Outstanding Issues = | |
| Line 49: | Line 45: |
| = Open Questions = | For this story to be feature complete, we need to pull information about patches in external trackers into Launchpad and make this info available as part of our patch report. This is more than what can be done in the next couple months while delivering the other stories for the 4.0 cycle. Some of this work has been done, but the rest will be re-considered sometime after April, 2010. |
| Line 51: | Line 47: |
| * Triage bugs tagged with patch-tracking to see what makes this development effort * Add story-patch-project, per agreement with Karl Fogel about the use of this tag |
Bugs related to external patch tracking are collected here: * [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=patch-tracking-external|patch-tracking-external tag]] |
Bug Patch Tracking is not one of the main stories under development by the Launchpad Bugs team for what is being called Launchpad v4.0. However, after discussions at UDS, based on the amount of work required and the importance of this work for the story of bridging the gap, this story has been taken on in addition to the work being done for BugHeat and Bug Q&A.
See the spec and see Bryce Harrington's example patch report page for more about this set of features.
Current focus: story-patch-report bugs
Drivers: Abel Deuring and Karl Fogel
Status
The best way to see where things stand is probably to look at bugs with these tags:
the story-patch-report tag
the patch-tracking tag
the patch-tracking-external tag
There are also screenshots (such as this one) attached to bug #506018.
Schedule and Plans
3.1.12 (December, 2009)
- bug 172507, "show patch icon or notification on the comments page" [DONE]
- added new icon from beuno to patches on the bug page
- bug 344054, "patches and attachments should be listed separately in bug reports" [DONE]
- added new "Patches" portlet for bug page
- Get agreement about design of +patches page [DONE]
- according to spec, bug listing columns for page should be: "bug number, summary, importance, status, package, and patch age"
- Deryck and Jorge agreed this would be added to pillars, people, and packages like +bugs to cover various views of this data
- Determine how much of the external tracker part of the story can be done [DONE]
10.01 (January, 2010)
- Implement +patches view
- Expose patches in bug listings and other pages
- (maybe) Patches don't only appear as attachments -- they can appear in branches too. E.g., if a bug has a branch attached, autodetect when that branch gets commits and the bug goes to "fix released" or something, then that should count as a patch.
10.02 (February, 2010)
- Consider patch tracking done
- Any remaining bits must land week 1 here
- Polish based on stake-holder feedback rest of cycle
Outstanding Issues
For this story to be feature complete, we need to pull information about patches in external trackers into Launchpad and make this info available as part of our patch report. This is more than what can be done in the next couple months while delivering the other stories for the 4.0 cycle. Some of this work has been done, but the rest will be re-considered sometime after April, 2010.
Bugs related to external patch tracking are collected here:
