[DOCS] Adds release highlight pages#30590
Merged
lcawl merged 2 commits intoelastic:masterfrom May 14, 2018
Merged
Conversation
pcsanwald
reviewed
May 14, 2018
Contributor
pcsanwald
left a comment
pcsanwald
left a comment
There was a problem hiding this comment.
These changes LGTM, but don't we also need 6.3 and 6.4? or were you going to do those in their respective branches?
Contributor
Author
|
I was going to create similar pages in the 6.4, 6.3, and 5.6 branches at this point. If that's not what you had in mind, let me know! |
pcsanwald
approved these changes
May 14, 2018
Contributor
pcsanwald
left a comment
pcsanwald
left a comment
There was a problem hiding this comment.
that sounds fine to me. reason I ask is there's an item we wanted to add for 6.4
lcawl
added a commit
that referenced
this pull request
May 14, 2018
lcawl
added a commit
that referenced
this pull request
May 14, 2018
lcawl
added a commit
that referenced
this pull request
May 14, 2018
Contributor
dnhatn
added a commit
that referenced
this pull request
May 15, 2018
* 6.x: Revert "Silence IndexUpgradeIT test failures. (#30430)" [DOCS] Remove references to changelog and to highlights Revert "Mute ML upgrade test (#30458)" [ML] Fix BWC version for backport of #30125 [Docs] Improve section detailing translog usage (#30573) [Tests] Relax allowed delta in extended_stats aggregation (#30569) Fail if reading from closed KeyStoreWrapper (#30394) [ML] Reverse engineer Grok patterns from categorization results (#30125) Derive max composite buffers from max content len Update build file due to doc file rename SQL: Extract SQL request and response classes (#30457) Remove the changelog (#30593) Revert "Add deprecation warning for default shards (#30587)" Silence IndexUpgradeIT test failures. (#30430) Add deprecation warning for default shards (#30587) [DOCS] Adds 6.4.0 release highlight pages [DOCS] Adds release highlight pages (#30590) Docs: Document how to rebuild analyzers (#30498) [DOCS] Fixes title capitalization in security content LLRest: Add equals and hashcode tests for Request (#30584) [DOCS] Fix realm setting names (#30499) [DOCS] Fix path info for various security files (#30502) Docs: document precision limitations of geo_bounding_box (#30540) Fix non existing javadocs link in RestClientTests Auto-expand replicas only after failing nodes (#30553)
Contributor
Author
|
Thanks, I've re-added it now that the builds are clean again: elastic/elasticsearch@ c0d639e2778a076e22a88b02028d7fb64bc915eb |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This PR creates the file structure for a new set of "release highlight" pages.
These highlight pages will summarize the most significant changes in each release (starting in 6.3.0).
At this time I have created the highlights at the same level as the release notes in the Elasticsearch Reference's table of contents:
However, once we know the final implementation for the changelog files, we can restructure the table of contents as necessary.
NOTE: At this time, these highlight pages are not meant to replace the blogs that go out with releases (e.g. https://www.elastic.co/blog/elasticsearch-6-2-0-released) though some of the same items might be covered in both places.