Changes between Version 1 and Version 2 of org/teams/NetworkTeam/TicketTriage


Ignore:
Timestamp:
Apr 9, 2018, 5:49:18 PM (14 months ago)
Author:
dgoulet
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • org/teams/NetworkTeam/TicketTriage

    v1 v2  
    22This page documents our ticket triaging process for a milestone.
    33
    4 We often end up with a lot of tickets in a milestone and unfortunately not enough capacity to address them all. Furthermore, we have a roadmap to respect so in order for a ticket to get into a milestone, it must match those criteria:
     4We often end up with a lot of tickets in a milestone and unfortunately not enough capacity to address them all. Furthermore, we have a roadmap to respect so in order for a ticket **to get into a milestone**, it must match those criteria:
    55
    66 * Must-fix bugs, to include:
    7    * Security issues
    8    * Regressions
    9    * Crash bugs
    10  * Issues which are very very fast to fix.
    11  * Roadmap item.
     7   * Security issues (keyword: `security`)
     8   * Regressions (keyword: `regression`)
     9   * Crash bugs (keyword: `crash`)
     10 * Issues which are very very fast to fix, usually under an hour (keyword: `fast-fix`)
     11 * Roadmap item (see below for the process).
     12
     13If you are unsure if a ticket should go in the `Unspecified` milestone, mark it **<VERSION>-proposed** so we can decide during the network team weekly meeting if it should.
    1214
    1315== Triage Algorithm ==