-
Notifications
You must be signed in to change notification settings - Fork 311
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.
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
[Release] 5.1.0 #3872
Milestone
Comments
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
$reindex_versions
array in theElasticPress\Upgrades::check_reindex_needed()
method. If it is the case, remember to add that information to the Changelog listings inreadme.txt
andCHANGELOG.md
.develop
, cut a release branch namedrelease/5.1.0
for your changes.elasticpress.php
,package.json
,package-lock.json
,readme.txt
, and any other relevant files if it does not already reflect the version being released. Inelasticpress.php
update both the plugin "Version:" property and the pluginEP_VERSION
constant.CHANGELOG.md
andreadme.txt
, ensuring to link the [5.1.0] release reference in the footer ofCHANGELOG.md
(e.g., 5.0.2...5.1.0).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..distignore
.wp i18n make-pot . lang/elasticpress.pot
and commit the file. In case of errors, try to disable Xdebug (see #3079.)develop
, then make a non-fast-forward merge fromdevelop
intotrunk
(git checkout trunk && git merge --no-ff develop
).trunk
contains the stable development version.trunk
branch, test for functionality locally.trunk
branch to GitHub (e.g.git push origin trunk
).Version X.Y.Z
CHANGELOG.md
+See: https:/10up/ElasticPress/milestone/79?closed=1
Due date (optional)
field) and link to GitHub release (in theDescription
field), then close the milestone.5.1.0
do not make it into the release, update their milestone to5.1.1
,5.2.0
,6.0.0
orFuture Release
.The text was updated successfully, but these errors were encountered: