Spin off from ticket
CLDT TC meeting notes Dec 12, 2018
Two kinds of tickets fixed by TC votes — or XML change.
Fix errors in resolution, or sometimes from tickets, but shouldn’t be “hard fix”; vetters should be able to refine in later releases.
This ticket is to design a tools solution to handle TC votes that were done based necessary to change quickly and are not backed by any policy decision.
The design should include:
1.How to identify this second type of TC votes that's different than policy (ticket #11676).
2.Vetter votes should not be imported.
3. We may also want to remove the last release data and set this to Missing so that the vetters can see these as Missing and vote.
4.An ability to flag to vetters that this had an issue in the last release. Possibly a link to ticket or description so that this flags to vetters as needing more attention (i.e. ways to prevent them from adding in the same value that they used in the past.)