Changes to release workflows in the new Chromium Issue Tracker

[Harry Souders]

Hi all,

Chromium has moved to its new issue tracker, and critical release information has been migrated from labels to custom fields . Release workflows have been updated to support these new fields:

• How to request a merge: add the applicable milestone(s) to the issue’s Merge-Request custom field:

• How to tag an affected milestone: Add the applicable milestone(s) to the issue’s Milestone custom field:

*** Note the Milestone custom field replaces the M-{milestone} and Target-{milestone} labels.

• How to flag a release blocking bug: update the issue’s ReleaseBlock custom field with {Dev|Beta|Stable}:

• How to tag an affected OS: Add the applicable platforms to the issue’s OS custom field:

We have updated the following documentation to reflect these changes:

• Chromium Docs - Merge Request Process

• Chromium Docs - Release Blockers

Please let us know if you have any questions or concerns.

Thanks,

Harry, on behalf of the Chrome Release team