3.6.1 - Step 2 #2268
Merged
3.6.1 - Step 2 #2268
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reindex needed after upgrading to 3.6.0
Fix/issue 2245
Prep 3.6.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
$reindex_versionsarray in theElasticPress\Upgrades::check_reindex_needed()method. If it is the case, remember to add that information to the Changelog listings inreadme.txtandCHANGELOG.md.develop, cut a release branch namedrelease/X.Y.Zfor your changes.elasticpress.php,package.json,readme.txt, and any other relevant files if it does not already reflect the version being released. Inelasticpress.phpupdate both the plugin "Version:" property and the pluginEP_VERSIONconstant.CHANGELOG.mdandreadme.txt, ensuring to link the [X.Y.Z] release reference in the footer ofCHANGELOG.md(e.g., X.Y.Z-1...X.Y.Z).CREDITS.mdfile with any new contributors, confirm maintainers are accurate.README.mdis geared toward GitHub andreadme.txtcontains WordPress.org-specific content. The two are slightly different..gitattributes.CHANGELOG.mddevelop, then make a non-fast-forward merge fromdevelopintomaster(git checkout master && git merge --no-ff develop).mastercontains the stable development version.masterbranch, test for functionality locally.masterbranch to GitHub (e.g.git push origin master).masterbranch. Paste the release changelog fromCHANGELOG.mdinto the body of the release and include a link to the closed issues on the milestone.Due date (optional)field) and link to GitHub release (in theDescriptionfield), then close the milestone.X.Y.Zdo not make it into the release, update their milestone toX.Y.Z+1,X.Y+1.0,X+1.0.0orFuture Release.