launchpad development|
Size: 2877
Comment:
|
← Revision 62 as of 2010-06-07 16:49:22 ⇥
Size: 2027
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| = Themes and User Stories = | = Stories In Active Development = |
| Line 11: | Line 11: |
| For general Launchpad info, see [[VersionFourDotO/Themes|Themes]] and [[VersionFourDotO/Stories|Stories]]. The bugs team itself is currently working on 3 user stories under one general theme. == Getting Bugs "off" Ubuntu == * [[Bugs/PatchTracking|Patch Tracking]] [DONE] * [[Bugs/BugHeat|Bug Heat]] * [[Bugs/ReliableBugSyncing|Reliable Bug Syncing]] Stories in the approval process: * [[LEP/BetterBugSubscriptionsAndNotifications|Better Bug Supscription and Notifications]] |
* [[LEP/BetterBugSubscriptionsAndNotifications|Better Bug Subscription and Notifications]] |
| Line 26: | Line 14: |
| Stories that have been discussed but are not being scheduled anytime soon: | = 10.06 = |
| Line 28: | Line 16: |
| * [[Bugs/BugQ&A|Bug Q&A]] | Goals for 10.06 include: |
| Line 30: | Line 18: |
| = 10.04 = Goals for 10.04 include: * Complete reliable bug syncing work * gnome-bugs updates * Status for a bug watch in UI * "reschedule" button in UI * deliever QA system (there is an open RT currently) * Finish 2-3 remaining minor issues for bug heat * Get jml approval for finished heat story * See bug list in gobby.ubuntu.com doc named lp-malone-bug-priorities * Finish remaining UDS-L actions/bugs * Do final polish/bug killing around UI, accessibility for getting bugs off Ubuntu work * Complete work on [[LEP/CloseBugsLeaveDiscussionsOpen|Closing Bugs while Leaving Discussions Open]] * Finish LEP * Get LEP approval * Implement feature * Better bug subscriptions and notifications * Get approval for [[LEP/BetterBugSubscriptionsAndNotifications|LEP for the feature]] * Finish designs with DUX team * Compile bug list and story tag * i.e. be "ready to code" by end of 10.04 |
* Start coding on [[LEP/BetterBugSubscriptionsAndNotifications|Better Bug Subscription and Notifications]] * Still waiting on UI research/mockups, so work on bugs that help drive down noise in bug mail * Work on cleaning up the code around mail notifications * Finish mini-feature around OPINION status (see "Close Bugs while..." LEP linked above) * More tech-debt clean up and bug fixes, especially around: * Comment handling in bugs * Test refactoring * Dupe handling |
| Line 56: | Line 29: |
| Work in progress is tracked on the Launchpad's Lean Kit Kanban board. Standup calls are held daily at 14:30 UTC to discuss the state of the board. |
Work in progress is tracked on the Launchpad's Lean Kit Kanban board. Standup calls are held daily at 16:00 UTC to discuss the state of the board. |
| Line 65: | Line 37: |
| * [[Bugs/10.04|10.04 cycle (April 2010)]] * [[Bugs/10.05|10.05 cycle (May 2010)]] |
This page is about the code that runs Launchpad's bug tracker. For information about handling and triaging Launchpad-related bugs, please see BugHandling instead. Ask for help right away if you have any questions. |
Launchpad Bugs is often called malone in code or by Launchpad developers. This is the application responsible for code that handles bugs, filing bugs, bug search, bug watches, external bug tracker integration, bug email, and more.
Stories In Active Development
10.06
Goals for 10.06 include:
Start coding on Better Bug Subscription and Notifications
- Still waiting on UI research/mockups, so work on bugs that help drive down noise in bug mail
- Work on cleaning up the code around mail notifications
- Finish mini-feature around OPINION status (see "Close Bugs while..." LEP linked above)
- More tech-debt clean up and bug fixes, especially around:
- Comment handling in bugs
- Test refactoring
- Dupe handling
In Progress
Work in progress is tracked on the Launchpad's Lean Kit Kanban board. Standup calls are held daily at 16:00 UTC to discuss the state of the board.
