[Announcement] Milo Stage & Prod Automation

[mokimo]

As we shipped most of the stage automation, here are all the updates in a single announcement

• Branches will now be automatically queued to merge into the stage once all checks pass, two approvals are given, and the 'Ready for Stage' label is applied.

- We have simplified our labels:

• The 'needs-verification', 'trivial', 'zero-impact', and other similar labels are no longer required.

• Every PR must be tested. QE should apply the 'Ready for Stage' label only after a PR has received approvals, all checks have passed, and testing is complete.

• The 'high impact' label will trigger a message in #milo-community & #milo-changelog for PRs that require additional review from consumers, GWP, design, etc.

• The 'high priority' label will prioritize PRs in the merge queue. Please reserve this label for JIRA BLOCKERS only.

• Automatic merges into production will commence once MWPW-148050: auto merge stage to main #2290 is merged.

• We have created a new Slack channel, #milo-changelog, which will feature all merges into stage and main (main merges will be featured once MWPW-148050: auto merge stage to main #2290 is merged).

These changes will significantly reduce the responsibilities of the "Milo Point of Contact" / MPOC. At the same time, they will make everyone accountable for production issues. Merges into production will occur during IST/EU/US working hours from Monday to Thursday, once four teams have signed off. As no single person is responsible, everyone is expected to step in case of production issues.

The CSO procedure for reverting PRs can be found in the opening post of the discussion: https://github.com/orgs/adobecom/discussions/2206

Thanks for your attention & cooperation in terms of the milo contributions! They are very well valued, and we hope this makes future milo contributions faster and less cumbersome.

Warm Regards, Okan

PS: I'll be hosting a deep dive session on the 29th May with the following agenda, going over all the changes & automation.
Milo refined PR process, new labels & automation

• Introduction to the new simplified PR labeling
• Explanation of re-used old labels & automated messages on slack
• Deep dive into the automated workflows that were introduced on the Github UI & the code

[overmyheadandbody]

Great summary! Since this is already activated, the Wiki should also reflect these changes. I've just linked the labels part, there may be other sections in need of updates.

Secondly, with the upcoming workflow to announce high impact PRs early, before being merged to stage, does it still make sense to send another notification when such a PR gets merged?

[mokimo]

I'll reserve some time to go over the wiki and reflect the recent changes. Feel free to remove announcement when merged into stage and just do them when the label is applied on a branch