We have an existing process (tracking-firefoxXX) to track bugs that need to be merged up trains. If there is an existing process to track fixes that need to be deployed (I assume you're thinking of services, AMO, Marketplace) I suggest we go with simple option A.
Lawrence
----- Original Message -----
> I noticed that the current version of my triage tracking tool never
> removes tracked bugs once they are fixed. What is the marker to
> indicate
> that a tracked bug is fixed and doesn't need to be actively tracked
> any
> more? I see two possibilities:
>
> A. Use the bug status, i.e. once a bug is RESOLVED, it no longer
> shows
> up on the triage page
> B. Add a tracking-kilimanjaro: fixed status
>
> Option A is simple, but it risks losing bugs if they land on -central
> (or some equivalent for non-product code) but need special treatment
> to
> be merged up trains or deployed
>
> Option B requires more work (probably from triage leads) but is less
> likely to accidentally leave bugs behind or unfinished.
>
> Any opinions about the better course of action here?
>
> --BDS
>
> _______________________________________________
> dev-planning mailing list
>
dev-pl...@lists.mozilla.org
>
https://lists.mozilla.org/listinfo/dev-planning
>