Backport #22574
closed
- Copied from Bug #22517: Cache never becoming consistent after failed updates added
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to Nathan Cutler
- Description updated (diff)
- Assignee changed from Nathan Cutler to Adam Emerson
- Status changed from In Progress to Fix Under Review
@Adam DC949 It's not a big deal, but in the past we have dispensed with the "Need Review" status for backports. The workflow for backport PRs is different than for master PRs. In a nutshell:
1. backport PR opened (backport tracker status changes from "New" to "In Progress")
2. backport PR passes integration testing (noted in PR; lead pinged in PR)
3. lead reviews/approves PR
4. PR merged (backport tracker status changes from "In Progress" to "Resolved" and target version gets set)
5. if all backports are resolved, the master tracker issue status changes from "Pending Backport" to "Resolved"
HTH
Nathan
- Status changed from Fix Under Review to Resolved
- Target version set to v12.2.3
Also available in: Atom
PDF