Skip to content

Release checklist: fix typo #1020

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

Open
jrfnl wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Release checklist: fix typo #1020

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
5 changes: 3 additions & 2 deletions .github/release-checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,10 @@ PR for tracking changes for the x.x.x release.

Target release date: **DOW MONTH DAY YEAR**.

Actions marked with ** only need to be executre for "cherrypick" releases (`develop` is the next minor/major and not ready for release).
Actions marked with ** only need to be executed for "cherrypick" releases (`develop` is the next minor/major and not ready for release).

- [ ] Check if any dependencies need updating.
- [ ] ** Create a `release-x.x.x` branch.
- [ ] ** Create a `release/vx.x.x` branch.
- [ ] ** Cherrypick any relevant commits from `develop` to the release branch, including commits related to CI updates.
- [ ] Update the version constant in `src/Requests.php` - PR #xxx.
- [ ] Add changelog for the release - PR #xxx
Expand All @@ -28,6 +28,7 @@ Actions marked with ** only need to be executre for "cherrypick" releases (`deve
- [ ] Close the milestone.
- [ ] Open a new milestone for the next release.
- [ ] If any open PRs/issues which were milestoned for the release did not make it into the release, update their milestone.
- [ ] ** Cherrypick the changelog commit from `stable` into the `develop` branch.
- [ ] Tweet about the release.
- [ ] Post about it in the WP #core Slack channel.
- [ ] Open a Trac ticket for WordPress Core to update their copy.
Expand Down