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
<https://chromium.googlesource.com/chromium/src.git/+/master/docs/process/merge_request.md>
-
Chromium Docs - Release Blockers
<https://chromium.googlesource.com/chromium/src.git/+/master/docs/process/release_blockers.md>
Please let us know if you have any questions or concerns.
Thanks,
Harry, on behalf of the Chrome Release team
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOC0RHDhzr706qfaSGeHXmrrRE2Z-BgkSpupZSo75bsr3-5jxA%40mail.gmail.com.
