Closed github-actions[bot] closed 9 months ago
@dkotter @peterwilsoncc are there additional issues/PRs we want to hold for in this release?
@dkotter @peterwilsoncc are there additional issues/PRs we want to hold for in this release?
Nothing on my end
@jeffpaul Nothing from my end either.
develop
, create a release branch namedrelease/X.Y.Z
for your changes.distributor.php
,package.json
,readme.txt
andtests/php/bootstrap.php
if it does not already reflect the version being released. Indistributor.php
update both the plugin "Version:" property and the pluginDT_VERSION
constant.webpack.config.release.js
.CHANGELOG.md
.CREDITS.md
file with any new contributors, confirm maintainers are accurate.README.md
is geared toward GitHub andreadme.txt
contains WordPress.org-specific content. The two are slightly different.@since
tags indicate the new version, replacingx.x.x
,n.e.x.t
and other placeholders.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.draft
toready to merge
.stable
branch to ensure the contents of the diffs are as expected.stable
branch and test it locally to ensure everything works as expected. It is recommended that you rename the existingdistributor
directory and check outstable
fresh because switching branches does not delete files. This can be done withgit clone --single-branch --branch stable git@github.com:10up/distributor.git
stable
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.stable
branch.Due date (optional)
field) and link to GitHub release (in theDescription
field), then close the milestone.X.Y.Z
do not make it into the release, update their milestone toX.Y.Z+1
,X.Y+1.0
,X+1.0.0
, orFuture Release
.