# Process states
The [overview](https://documentation.ubuntu.com/project/MIR/main-inclusion-review.md#main-inclusion-review) aims to clarify and provide an easy
simplified entry to the topic. This page instead outlines the detailed
meaning of all MIR related bug states. This allows one to understand the
implications of such states and indicates the next course of action based on
an MIR bug’s current state.
| Index | State | Assignee / Subscriber | State-Explanation |
|---------|-------------------------------------|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|
| *1.* | New / Confirmed[1](#id5) | (unassigned, ubuntu-mir subscribed) | Bug is queued for assignment to an MIR team member |
| *2.* | New / Confirmed[1](#id5) | (assigned to MIR team member) | On the TODO list of the assigned MIR team member |
| *3.* | New / Confirmed[1](#id5) | (assigned to Security team member) | On the TODO list of the Security team member |
| *4.* | In Progress | (unassigned) | MIR team ACK (and if needed, Security team ACK) done, but now needs the Dependency / Seed change to happen to pull package(s) into `main`/`restricted` |
| *5.* | Fix Committed | (unassigned, ubuntu-archive subscribed) | All of the above done; waiting for an Archive Admin to promote the package(s) to `main`/`restricted` |
| *6.* | Fix Released | (unassigned) | Case resolved by an Archive Admin |
| *7.* | Won’t Fix | (unassigned) | Final NACK from MIR team or bug reporter gave up |
| *8.* | Incomplete | (assigned to the reporter) | Questions / Requests were raised for the bug reporter to resolve / clarify |
| *9.* | Invalid[1](#id5) | (unassigned) | No response within 60 days when in `Incomplete` state |
| Index | Transition-Explanation | Responsible to set state and assignee |
|---------|--------------------------------------------------------------------|-----------------------------------------|
| *a.* | Create MIR bug following the template | Reporter/Driver |
| *b.* | Subscribe Launchpad team ~ubuntu-mir | Reporter/Driver |
| *c.* | Triaged at MIR team meeting | MIR team |
| *d.* | MIR team ACK (report added as comment) | MIR team |
| *e.* | MIR team ACK (report added as comment), but security review needed | MIR team |
| *f.* | MIR team NACK | MIR team |
| *g.* | Needs questions answered or required actions done | MIR team |
| *h.* | Security ACK (report added as comment) | Security team |
| *i.* | Security NACK (report added as comment) | Security team |
| *j.* | Needs questions answered or required actions done | Security team |
| *k.* | Questions or requests resolved | Reporter/Driver |
| *l.* | Situation changes, new input given | Reporter/Driver |
| *m.* | Dependency/seed change that pulls package(s) into main | Reporter/Driver |
| *n.* | Archive Admin promotes package | Archive Admin |
| *o.* | No response by the bug reporter/driver within >=60 days | MIR team |
#### NOTE
All other states are undefined and should be resolved to one of the defined
states -– otherwise they might be completely missed on the weekly checks.
---
* **[1]** Since many people set Launchpad bugs to `Confirmed` once they verified the validity of a problem, MIR bugs often get set to `Confirmed`. Since `Confirmed` does not have any meaning for our process, we will handle `New` and `Confirmed` as if they are the same.