Release checklist: minor updates to the publicize section #2567
Conversation
- Clarify which account to use when posting to social media about the release. - Clarify which Slack channel to post to. - Replace "Month in WordPress" with a Marketing team amplify request as the former doesn't exist anymore and was replaced by the latter
jrfnl
left a comment
jrfnl
left a comment
There was a problem hiding this comment.
OMG.... just realized that I left a comment and then forgot to "finish" the review, so the comment is visible only to me and nobody else... darn... my bad....
.github/release-checklist.md
Outdated
| - [ ] 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. |
There was a problem hiding this comment.
Should this also mention posting in other channels when relevant ? Think: #plugin-review if a sniff was added in a release which was requested by the plugin review team, #core-docs if significant updates were made to the documentation ruleset ?
And that there is no need to post in the #core-coding-standard channel as that gets an automated release notification ?
I think the wording can be kept quite generic.
Plus fixes a line break issue in one of the items of the release section by adding to spaces to the line before it to force a soft line break.
jrfnl
left a comment
jrfnl
left a comment
There was a problem hiding this comment.
Thanks for making the update @rodrigoprimo ! LGTM! Will merge once the build has finished.
3 participants
As discussed in #2558 (comment), I'm opening this PR to suggest a few updates/clarifications to the release checklist document: