Skip to content

Docs: Fix broken links in Gutenberg release checklist #71611

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
t-hamano merged 1 commit into from
Sep 11, 2025
Merged

Docs: Fix broken links in Gutenberg release checklist #71611

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions .github/ISSUE_TEMPLATE/New_release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,11 +25,11 @@ This issue is to provide visibility on the progress of the release process of Gu
### RC Day - {WEEKDAY}, {MONTH}, {DATE}

- [ ] Post a message in `#core-editor` channel to let folks know you are starting the RC release process
- [ ] [Organize and Label PRs](https://developer.wordpress.org/block-editor/contributors/code/release/#organizing-and-labeling-milestone-prs) on the relevant milestone
- [ ] Start the release process by triggering the `rc` [workflow](https://developer.wordpress.org/block-editor/contributors/code/release/#running-the-release-workflow)
- [ ] [Update the created Draft Release accordingly](https://developer.wordpress.org/block-editor/contributors/code/release/#viewing-the-release-draft)
- [ ] [Curate the changelog](https://developer.wordpress.org/block-editor/contributors/code/release/#curating-the-release-changelog) before publishing
- [ ] [Publish Release](https://developer.wordpress.org/block-editor/contributors/code/release/#publishing-the-release)
- [ ] [Organize and Label PRs](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/#organizing-and-labeling-milestone-prs) on the relevant milestone
- [ ] Start the release process by triggering the `rc` [workflow](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/#running-the-release-workflow)
- [ ] [Update the created Draft Release accordingly](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/#viewing-the-release-draft)
- [ ] [Curate the changelog](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/#curating-the-release-changelog) before publishing
- [ ] [Publish Release](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/#publishing-the-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))_
Expand All @@ -42,14 +42,14 @@ This issue is to provide visibility on the progress of the release process of Gu
- [ ] Get assets from [Design Team](https://make.wordpress.org/design/) for the post if required
- [ ] Reach out to Highlight Authors to draft sections (if necessary)

### Release Day - {Weekday, Month, Date}
### Release Day - {WEEKDAY}, {MONTH}, {DATE}

- [ ] 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-the-release-workflow)
- [ ] Start the release process by triggering the `stable` [workflow](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/#running-the-release-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](https://developer.wordpress.org/block-editor/contributors/code/release/#publishing-the-release)
- [ ] [Publish Release](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/#publishing-the-release)
- [ ] Trigger the update to the plugin directory. _(Get approval from a member of [Gutenberg Release team](https://github.com/orgs/WordPress/teams/gutenberg-release/members) if necessary)_
- [ ] Announce in `#core-editor` channel that the plugin has been released
- [ ] Reach out to other contributors to help get the post reviewed
- [ ] [Publish Release post](https://developer.wordpress.org/block-editor/contributors/code/release/#publishing-the-release-post) on Make Core blog
- [ ] Post in the `#core-editor` channel [requesting a volunteer for the next Gutenberg release](https://developer.wordpress.org/block-editor/contributors/code/release/#call-for-volunteer-for-the-next-release).
- [ ] [Publish Release post](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/#publishing-the-release-post) on Make Core blog
- [ ] Post in the `#core-editor` channel [requesting a volunteer for the next Gutenberg release](https://developer.wordpress.org/block-editor/contributors/code/release/plugin-release/#call-for-volunteer-for-the-next-release).
Loading