Combine Milestone Reschedule with Missed Label application
With #356 (closed), the application of missed-deliverable and ~missed:x.y
changed based on the rules at #356 (closed). In https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/354370119 the milestones were rescheduled on 2019-11-19 from %12.5 to %12.6 but the labels won't run until 2019-11-21.
We are looking to simplify the process for issue updates related to Milestone transition.
Proposal
Apply missed-deliverable, ~missed:x.y
, run move milestone forward
policy and close current milestone in the same pipeline. This application would occur based on the following rules:
- If the 22nd is a Sunday, milestone transition automation will run on Friday the 20th
- If the 22nd is a Monday, milestone transition automation will run on Friday the 19th
- Milestone transition automation will run on the 21st for all other days
Note: Milestone expiration would still occur on M+18 but the closure of the milestone would change to the date above Close the milestone 3 months after expiration
Issues will be rescheduled if they are open, in the milestone for reschedule and do not have workflowverification applied.
Open items
- What downstream tasks/logic are built off of the current opened milestone that we do not realize? (https://about.gitlab.com/upcoming-releases/)
Tasks
-
Solicit feedback and input from EMs/PMs -
Update move-milestone-forward to move open issues which do not have workflowverification on matching date in Proposal. -
Investigate closing milestone within an API call if application of missed-deliverable ~missed:x.y
andmove-milestone-forward
policy are successful. This can be iterated towards adding this into gitlab-triage -
Update https://about.gitlab.com/handbook/engineering/workflow/#milestone-cleanup -
Update https://about.gitlab.com/handbook/engineering/workflow/#product-development-timeline - #366 (comment 258923296)