[SERVER-81252] Increase priority on future git tag variant failures closer to release Created: 20/Sep/23 Updated: 24/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | bkp | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Correctness
|
||||||||
| Backport Requested: |
v7.3
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently, BFs from future git tag variants are triaged and treated as normal BFs. Since these BFs will block upgrading FCV, we should prioritize these BFs leading up to a release. I believe this was discussed when we had first introduced the future git tag variant, but the conclusion was that they could not be labeled as hot BFs due to process reasons. We should consider making them hot BFs a month or so before the release or creating a separate label for these BFs so that they are appropriately prioritized. |