Release version 7.3.3
Sidsector9 opened this issue · 0 comments
Sidsector9 commented
This issue is for tracking changes for the 7.3.3 release. Target release date: 31st October 2022.
Release steps
- Branch: Starting from
develop
, cut a release branch namedrelease/7.3.3
for your changes. - Version bump: Bump the version number in
package.json
,restricted_site_access.php
, andreadme.txt
if it does not already reflect the version being released. - Changelog: Add/update the changelog in
readme.txt
andCHANGELOG.md
. - Props: update
CREDITS.md
file with any new contributors, confirm maintainers are accurate - New files: Check to be sure any new files/paths that are unnecessary in the production version are included in
.gitattributes
. - Readme updates: Make any other readme changes as necessary.
README.md
is geared toward GitHub andreadme.txt
contains WordPress.org-specific content. The two are slightly different. - Merge: Make a non-fast-forward merge from your release branch to
develop
(or merge the pull request), then do the same fordevelop
intotrunk
(git checkout trunk && git merge --no-ff develop
).trunk
contains the stable development version. - Push: Push your
trunk
branch to GitHub (e.g.git push origin trunk
). - Release: Create a new release, naming the tag and the release with the new version number, and targeting the
trunk
branch. Paste the changelog fromCHANGELOG.md
into the body of the release and include a link to the closed issues on the milestone. The release should now appear under releases and in the WordPress admin as an update as well. - SVN: Wait for the GitHub Action to finish deploying to the WordPress.org repository. If all goes well, users with SVN commit access for that plugin will receive an emailed diff of changes.
- Check WordPress.org: Ensure that the changes are live on https://wordpress.org/plugins/restricted-site-access/. This may take a few minutes.
- Close milestone: Edit the milestone with release date (in the
Due date (optional)
field) and link to GitHub release (in theDescription field
), then close the milestone. - Punt incomplete items: If any open issues or PRs which were milestoned for
7.3.3
do not make it into the release, update their milestone to7.3.4
,7.4.0
,8.0.0
, orFuture Release
.