Blueprint changed by James Page: Whiteboard changed: UDS Discussion Points: Review of current process - http://reports.qa.ubuntu.com/reports/ubuntu-server/triage-report.html How is the New/Undecided -> New process working? are we losing focus during this step? We have a backlog - we need to have a blitz on pushing stuff through. Additional tagging to help with triage. - unreproducable? Session Notes: http://pad.ubuntu.com/uds-q-servercloud-q-bug-triage- review + + User Stories: + + Alphonse has just started contributing to Ubuntu as a member of the + Ubuntu Server team. He's able to quickly and effectively start triaging + bugs using the bug triage workflow and guide. + + Graham is a regular bug triager on the Ubuntu Server Bug Triage rota. + His life is made alot easier as installation and upgrade failures are + automatically marked as duplicates by the bug bot which allows him to + get to the most valuable and high impact bugs rather than trawling + through install/upgrade failure logs during this triage time. + + Tony is doing some analysis on installation and upgrade failures in the + Ubuntu Server packageset. As these bugs are now automatically marked as + duplicates he can easily see which packages are causing the most pain + during upgrades. + + Assumptions: + + - Reporting will continue to be delivered outside of launchpad. + - All bugs will continue to be reported inside launchpad. + - Automation activity will be carried out by bug bots. + + Test Plan: TBC + Release Note: N/A
-- Review of Server Bug Triage Process https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-bug-triage-review -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
