Streamlining the New Release Issue Template. #49618
Conversation
ryanwelcher
added
[Type] Project Management
|
Oh good, that you take another stab at it @ryanwelcher
I see that's already fixed. Ignore me |
| - 📽 Watch: [Gutenberg Plugin: New Release Workflow](https://www.youtube.com/watch?v=TnSgJd3zpJY) | ||
| - 📽 Watch: [Creating the Gutenberg plugin v12.0 Release Candidate](https://www.youtube.com/watch?v=FLkLHKecxWg) | ||
| - 📽 Watch: [Gutenberg plugin v12.0.0 Release Party!](https://www.youtube.com/watch?v=4SDtpVPDsLc) | ||
|
|
||
| ## Checklist | ||
|
|
||
| ### RC Day - Wednesday, March 15 | ||
| ### RC Day - {Weekday, Month, Date} | ||
|
|
||
| - [ ] _Optional:_ Attend `#core-editor` meeting (14:00UTC) | ||
| - [ ] Post a message in `#core-editor` channel to let folks know you are starting the RC release process | ||
| - [ ] Organize and Label PRs on the relevant milestone |
There was a problem hiding this comment.
I'm not sure I understand. These are the steps that need to be taken during the RC release process.
| - [ ] Get assets from [Design Team](https://make.wordpress.org/design/) for the post | ||
| - [ ] Reach out to Highlight Authors to draft sections _(if necessary)_ |
There was a problem hiding this comment.
Not sure why you're dropping this too? Reaching out to authors of highlighted items to get them draft that part of the post could be useful, esp. if the item is particularly technical, or the release lead is less technical.
There was a problem hiding this comment.
We've never done this in any release that either myself or @justintadlock have done. It seemed extraneous.
| @@ -14,36 +14,34 @@ This issue is to provide visibility on the progress of the release process of Gu | |||
| ## Resources | |||
|
|
|||
| - 📖 Read: [Gutenberg Release Process](https://developer.wordpress.org/block-editor/contributors/code/release/) | |||
| - 📖 Read: [Leading a Gutenberg Plugin Release](https://codep2.wordpress.com/2021/07/22/leading-a-gutenberg-plugin-release/) | |||
There was a problem hiding this comment.
This link should be removed as it's inaccessible for the community
There was a problem hiding this comment.
It has been removed :)
|
|
||
| ### Between RC and Release | ||
|
|
||
| - [ ] [Backport to RC](https://github.com/WordPress/gutenberg/pulls?q=is%3Apr+label%3A%22Backport+to+Gutenberg+RC%22+is%3Aclosed) | ||
| - [ ] [Draft Release Post Highlights and Change Log](https://docs.google.com/document/d/1Hh25EYXSvRd5K45gq0VFN7yfN5l9om2FpX-_KqpVW7g/edit#) | ||
| - [ ] [Draft Release Post Highlights and Change Log](https://docs.google.com/document/d/1D-MTOCmL9eMlP9TDTXqlzuKVOg_ghCPm9_whHFViqMk/edit) |
There was a problem hiding this comment.
Thanks for making it a reusable template :-)
|
Flaky tests detected in 22ef82b. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/4620487000
|
bph
added
[Type] Developer Documentation
What?
This PR makes some small changes to the issue template based on using it for the last two releases of the Gutenberg plugin.