Add a CHANGELOG file for release notes #78
Merged
Conversation
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
droberts195
approved these changes
Apr 30, 2018
droberts195
left a comment
droberts195
left a comment
There was a problem hiding this comment.
LGTM
I noted a redundant section that you may want to remove, or can leave if consistent section order between the repos is important.
docs/CHANGELOG.asciidoc
Outdated
|
|
||
| === Breaking Changes | ||
|
|
||
| === Breaking Java Changes |
There was a problem hiding this comment.
This section will always be empty in this repo. But I'll leave it up to you whether you remove it or leave it for consistency with the elasticsearch repo.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
In order to improve the quality of our release notes, we're going to start using a CHANGELOG file, per elastic/elasticsearch#29450
This content will be integrated into the Elasticsearch release notes before each new release.