Closed acicovic closed 1 month ago
Noting here that we had issues merging trunk
into develop
without being forced to merge develop
into trunk
, which is not ideal. This was addressed by creating an intermediary PR to handle this merge (#2680). Steps followed by @acicovic:
git merge trunk
into it
This is an issue for tracking the next
wp-parsely
release. This ticket is to be opened the week before the actual release, so we have enough time to complete all the related tasks.The actual release of the plugin should be done on Mondays so we can catch the Tuesday WordPress VIP release window.
Before releasing
1. Merge all outstanding work
develop
).Changelog
tag. PRs without aChangelog
tag won't be added to the changelog.2. Conduct additional testing We've got automated testing in place and also test under our local development environment during development. For impactful releases we should also:
3. Communicate
The following additional tasks might be needed depending on the release and its impact:
Release process
1. Update version numbers and changelog
php bin/release.php $OLD_VERSION $NEW_VERSION
to update version numbers, the changelog, and to push the PR to GitHub. Copy the changelog's new release text for later use.develop
).2. Merge develop into trunk
develop
) intotrunk
, named Release wp-parsely x.y.z.trunk
.3. Create the GitHub release
trunk
.bin/release.php
script into the PR in step 1.4. Deploy the release to wordpress.org
After releasing
1. Communicate
2. Merge trunk back into develop
trunk
intodevelop
, named Merge trunk into develop after the wp-parsely x.y.z release.develop
.3. Manage milestones
4. Release to other platforms
vip-go-mu-plugins
submodule to the latest version.