Gecko 102 goes to beta on May 30, 2022; we should probably aim to have mozilla-esr102 ready by mid June.

Prior art: bug 1717527

For ESR91, we filed bug 1717541 and bug 1717542 for balrog updates, but then didn't make any changes in those bugs -- I've skipped them for ESR102, but we should double-check those issues later.

:ryanvm asked :dkl to deactivate mozilla-approval-esr102 (bug 1766882) as that won't be needed for at least another 4 weeks. We should ping :dkl to reactivate it later.

Consider filing the bugzilla flags bug later in the process for the next esr.

Linking shipit changes here for future reference

• https://github.com/mozilla-releng/shipit/issues/1066
• https://github.com/mozilla-releng/shipit/pull/1069

https://github.com/mozilla-releng/scriptworker/pull/541 to create scriptworker release; pushed to pypi.
Next steps:

• run pin.sh in scriptworker-scripts, PR, merge, deploy to production branch
• update scriptworker_revision in ronin-puppet, PR, merge to master, deploy to production-mac-signing branch to roll out to mac signers

(In reply to Aki Sasaki [:aki] (he/him) (UTC-6) from comment #4)

https://github.com/mozilla-platform-ops/ronin_puppet/pull/385

:jcristau - Most of the initial esr102 changes have landed. Is there anything else we should be doing now? Do we just wait for sheriffs to start merging to esr102, and if so, when does that begin?

I've just pushed the tip of beta to esr102 so we get tasks going and can look for any unexpected breakage:
https://treeherder.mozilla.org/jobs?repo=mozilla-esr102&revision=e249c0dc507f77b1637efb6fcf12838add374cac