Release cycle triage proposal

[nikomatsakis]

@brson

My best guess is that P-high means 'critical to fix right now'. As a corollary, that also means 'somebody is assigned'. If we're not willing to assign somebody thin it must not be critical.

As we discussed on IRC, I have sometimes considered four categories:

• Fix it now.
• Retriage regularly (say, every release).
• Retriage periodically (as a background task).
• Do not retriage unless requested to do so. Will get fixed when it gets fixed.

Currently, we don't have the "retriage regularly category", I don't think. I would sort of like to use a milestone-per-release as the "fix it now" category; P-high for retriage regularly; P-medium for retriage periodically; and P-low for "do not retriage unless requested".

The idea would be that after every release we focus on p-high bugs, than focus on p-medium bugs until the next release.

@brson

Similar to the last, we're not doing anything in particular to uncover regressions and promote them to P-high. Just hoping that individuals are watching the incoming issues and tagging them right.

At some point we also discussed the idea of reviewing issues opened since the last triage meeting and so forth. But I think that would require more regular meetings.

@brson

Anybody interested in bumping the frequency from every 3 weeks to every 2 weeks?

+1