launchpad development|
Size: 2762
Comment: Add Abel's idea about branches as patches.
|
Size: 2957
Comment: Update based on recent tag cleanup.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 36: | Line 36: |
| = Work Done = The best way to see work done is probably to see bugs tagged with the [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=story-patch-report|story-patch-report tag]]. |
|
| Line 38: | Line 42: |
| 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. The external component will be re-considered sometime after April, 2010. | 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 40: | Line 44: |
| For now, any bugs related to the external patch tracking story are collected here: | Bugs related to external patch tracking are collected here: |
| Line 42: | Line 46: |
| * [[https://bugs.edge.launchpad.net/launchpad-project/+bugs?field.tag=story-patch-report-external|story-patch-report-external tag]] | * [[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.
Current focus: story-patch-report bugs
Drivers: Abel Deuring and Karl Fogel
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
Important Links
See the spec
See Bryce's patch page
Work Done
The best way to see work done is probably to see bugs tagged with the story-patch-report tag.
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:
