Streamlining the New Release Issue Template. #49618
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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/) | ||
| - 📽 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 - {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. |
||
| - [ ] Start the release process by triggering the `rc` [workflow](https://developer.wordpress.org/block-editor/contributors/code/release/#running-workflow) | ||
| - [ ] [Update the created Draft Release accordingly](https://developer.wordpress.org/block-editor/contributors/code/release/#view-the-release-draft) | ||
| - [ ] Publish Release | ||
| - [ ] Announce in `#core-editor` channel that RC1 has been released and is ready for testing | ||
| - [ ] Ping any other relevant channels announcing that the RC is available | ||
| - [ ] Create Draft of Release post on Make Core blog _(initial draft in [Google doc](https://docs.google.com/document/d/1D-MTOCmL9eMlP9TDTXqlzuKVOg_ghCPm9_whHFViqMk/edit))_ | ||
|
|
||
| ### Between RC and Release | ||
|
|
||
ryanwelcher marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| - [ ] [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 :-) |
||
| - [ ] Get assets from [Design Team](https://make.wordpress.org/design/) for the post | ||
|
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. |
||
|
|
||
| ### Release Day - {Weekday, Month, Date} | ||
|
|
||
| - [ ] If there are any PRs marked as [Backport to RC](https://github.com/WordPress/gutenberg/pulls?q=is%3Apr+label%3A%22Backport+to+Gutenberg+RC%22+is%3Aclosed), run the [cherry-pick command to apply them](https://developer.wordpress.org/block-editor/contributors/code/release/auto-cherry-picking/#how-can-i-use-it-for-a-gutenberg-plugin-release) to the release branch. **This needs to be run locally** | ||
| - [ ] Post a message in `#core-editor` channel to let folks know you are starting the release process | ||
| - [ ] Start the release process by triggering the `stable` [workflow](https://developer.wordpress.org/block-editor/contributors/code/release/#running-workflow) | ||
| - [ ] Update the created Draft Release accordingly. Typically by copy/pasting the last RC release notes and add any changes/updates as needed. | ||
| - [ ] Publish Release | ||
| - [ ] Trigger the update to the plugin directory - SVN _(get approval from member of Core team if necessary)_ | ||
|
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link should be removed as it's inaccessible for the community
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It has been removed :)