We currently use a FIXME-based suppression mechanism combined with git blame timestamp filtering to triage and analyze warnings in a fine-grained, iterative way. The process involves gradually moving the timestamp filter back to analyze the next batch of issues, until we can eventually remove timestamp filtering altogether.
DoD:
- Do the first round of this process
- Move the timestamp back to get resonable amount of issues to triage (let's say 10 issues)
- Triage this issues
- If the announcement wasn't made yet, don't assign the issues to different teams. Just leave a comment what team should be responsible for it and put it to the corresponding section of the doc.
- Triage WT-15347
- is related to
-
WT-15347 Investigate and fix disagg transaction/timestamp related warnings
-
- Open
-