Skip to content

Release checklist: minor updates to the publicize section #2567

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
jrfnl merged 2 commits into from
Sep 3, 2025
Merged

Release checklist: minor updates to the publicize section #2567

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a782161
Release checklist: minor updates to the publicize section
rodrigoprimo Aug 4, 2025
dabefb4
Address PR review feedback
rodrigoprimo Sep 3, 2025
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
13 changes: 8 additions & 5 deletions .github/release-checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ PR for tracking changes for the x.x.x release. Target release date: **DOW MONTH

- [ ] Merge this PR.
- [ ] Make sure all CI builds are green.
- [ ] Tag and create a release against `main` (careful, GH defaults to `develop`!) & copy & paste the changelog to it.
- [ ] Tag and create a release against `main` (careful, GH defaults to `develop`!) & copy & paste the changelog to it.
:pencil2: Check if anything from the link collection at the bottom of the changelog needs to be copied in!
- Remove square brackets from all ticket links or make them proper full links (as GH markdown parser doesn't parse these correctly).
- Change all contributor links to full inline links (as GH markdown parser on the Releases page doesn't parse these correctly).
Expand All @@ -62,13 +62,16 @@ PR for tracking changes for the x.x.x release. Target release date: **DOW MONTH
### Publicize

- [ ] [Major releases only] Publish post about the release on Make WordPress.
- [ ] Tweet, toot, etc about the release.
- [ ] Post about it in Slack.
- [ ] Submit for ["Month in WordPress"][month-in-wp].
- [ ] Tweet, toot, etc about the release from your personal account (there is no official WPCS account).
- [ ] Post about it in #core channel on the WordPress.org Slack.
:pencil2: No need to post in the #core-coding-standard channel as that gets an automated release notification anyway.
- [ ] Optionally post in #plugin-review if a sniff was added in a release which was requested by the plugin review team.
- [ ] Optionally post in #core-docs if significant updates were made to the documentation ruleset.
- [ ] Create a Marketing team ["amplify request"][amplify-request].
- [ ] Submit for the ["Monthy Dev Roundup"][dev-roundup].

[phpcs-releases]: https://github.com/PHPCSStandards/PHP_CodeSniffer/releases
[phpcsutils-releases]: https://github.com/PHPCSStandards/PHPCSUtils/releases
[phpcsextra-releases]: https://github.com/PHPCSStandards/PHPCSExtra/releases
[month-in-wp]: https://make.wordpress.org/community/month-in-wordpress-submissions/
[amplify-request]: https://github.com/WordPress/Marketing-Team/issues/new?template=2-request-for-amplification-template.yml
[dev-roundup]: https://github.com/WordPress/developer-blog-content/issues?q=is%3Aissue+label%3A%22Monthly+Roundup%22
Loading