Triage
|
Size: 366
Comment:
|
← Revision 82 as of 2015-12-08 19:12:52 ⇥
Size: 2116
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from One Hundred Papercuts/Work-flow/Triage | |
| Line 3: | Line 4: |
| ## Borrowed from <wiki.ubuntu.com/Bugs/Triage> | ## Pictographs available at <unicode.org/charts/PDF/U1F300.pdf> |
| Line 8: | Line 9: |
| To triage a bug is to make it ready to be fixed by a developer. | To triage '''is''' to make a [[/Lists of bugs|listed bug]] ready to be fixed by a developer: |
| Line 10: | Line 11: |
| /!\ Only triage bugs to projects you're involved with (bugs in Ubuntu are managed by the [[UbuntuBugControl||Ubuntu Bug Control]] team). /!\ Never triage work-flow bugs. |
=== Validate === * 🔧 It isn't a [[/Support request|support request]]. * 💿 There's no evidence that the software has been installed from a '''third party''' or personal archive. === Shine === * 💻 It contains [[/Enough information|enough information]] as far as possible. * 🎯 The '''title''' is specific and meaningful. * 🔳 The '''panel''' hasn't any obvious error for you. * 🐾 There isn't any obvious [[/Duplicates|duplicate]]. === Classify === * 🕑 As a [[/Classify as a stable release update|stable release update]] if appropriate. * 📜 As a [[/Classify as a papercut|papercut]] if needed. * 🔑 As a [[/Classify as a security bug|security bug]] if needed. * 💟 As a [[/Classify as a kernel bug|kernel bug]] if needed * 💬 As a '''translation''' bug if needed. === Publish === * 🔓 Make it '''public''' if needed (carefully). * 📨 Ask to report [[/Upstream|upstream]] if needed. * 📤 Set its status to '''triaged''' if appropriate. == == If at any point there's '''missing information''': * Set the bug status to '''incomplete'''. * Ask the bug reporter to provide the '''information''', and to set the bug status back to '''confirmed''' when done. == == ;) If you need to clarify '''specific doubts''', you can have a look at the [[Bugs/Triage|detailed triaging guide]]. ;) If you want to triage '''for this project''', you can do by joining the [[https://launchpad.net/~papercuts-ninja|Papercuts Ninjas]]. ;) If you want to triage '''for Ubuntu''', you can do by joining the [[https://launchpad.net/~ubuntu-bugcontrol|Ubuntu Bug Control]] team. == == [[https://wikipedia.org/wiki/File:Puzzle_Krypt-2.jpg|{{attachment:Puzzle.jpg|(CC-BY-SA 3.0) 2006 Muns & 2009 Schlurcher|height=300}}]] |
To triage is to make a listed bug ready to be fixed by a developer:
Validate
🔧 It isn't a support request.
💿 There's no evidence that the software has been installed from a third party or personal archive.
Shine
💻 It contains enough information as far as possible.
🎯 The title is specific and meaningful.
🔳 The panel hasn't any obvious error for you.
🐾 There isn't any obvious duplicate.
Classify
🕑 As a stable release update if appropriate.
📜 As a papercut if needed.
🔑 As a security bug if needed.
💟 As a kernel bug if needed
💬 As a translation bug if needed.
Publish
🔓 Make it public if needed (carefully).
📨 Ask to report upstream if needed.
📤 Set its status to triaged if appropriate.
If at any point there's missing information:
Set the bug status to incomplete.
Ask the bug reporter to provide the information, and to set the bug status back to confirmed when done.
If you need to clarify specific doubts, you can have a look at the detailed triaging guide.
If you want to triage for this project, you can do by joining the Papercuts Ninjas.
If you want to triage for Ubuntu, you can do by joining the Ubuntu Bug Control team.
One Hundred Papercuts/Triage (last edited 2015-12-08 19:12:52 by es20490446e)