[DOCS ] Separate release notes files #1034
Merged
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
lcawl
force-pushed
the
release-notes-files
branch
from
2f2c404 to
c30923a
Compare
lcawl
added a commit
to lcawl/security-docs
that referenced
this pull request
Sep 15, 2021
lcawl
added a commit
to lcawl/security-docs
that referenced
this pull request
Sep 15, 2021
This was referenced Sep 15, 2021
lcawl
added a commit
that referenced
this pull request
Sep 15, 2021
lcawl
added a commit
that referenced
this pull request
Sep 15, 2021
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.
This PR models a split of the release notes source file into multiple version-specific files, based on the way they do it in Elasticsearch: https://github.com/elastic/elasticsearch/tree/7.x/docs/reference/release-notes
This might make backporting less prone to merge conflicts.