-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Introduce next Changelog file #9767
Conversation
This introduces CHANGELOG.next.asciidoc and CHANGELOG-developer.next.asciidoc. These changelog files will document yet unreleased changes. Having a separate changelog file reduces the work required to cleanup the changelog, as rebasing and cherry-picking on backports sometimes moves changelog entries into the wrong place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I didn't check the changelog entries cleanup.
Should we introduce a CHANGELOG.next.asciidoc also in 6.x. This will make backports easier.
+1 to introduce it to 6.x and maybe 6.5 if possible since both of theses branches are currently actives. |
I will introduce the change to 6.x, 6.6, and 6.5 branches. |
This introduces CHANGELOG.next.asciidoc and CHANGELOG-developer.next.asciidoc. These changelog files will document yet unreleased changes. Having a separate changelog file reduces the work required to cleanup the changelog, as rebasing and cherry-picking on backports sometimes moves changelog entries into the wrong place. (cherry picked from commit eae3bff)
This introduces CHANGELOG.next.asciidoc and CHANGELOG-developer.next.asciidoc. These changelog files will document yet unreleased changes. Having a separate changelog file reduces the work required to cleanup the changelog, as rebasing and cherry-picking on backports sometimes moves changelog entries into the wrong place. (cherry picked from commit eae3bff)
This introduces CHANGELOG.next.asciidoc and CHANGELOG-developer.next.asciidoc. These changelog files will document yet unreleased changes. Having a separate changelog file reduces the work required to cleanup the changelog, as rebasing and cherry-picking on backports sometimes moves changelog entries into the wrong place. (cherry picked from commit eae3bff)
Cherry-pick of PR #9767 to 6.6 branch. Original message: This introduces CHANGELOG.next.asciidoc and CHANGELOG-developer.next.asciidoc. These changelog files will document yet unreleased changes. Having a separate changelog file reduces the work required to cleanup the changelog, as rebasing and cherry-picking on backports sometimes moves changelog entries into the wrong place. I don't mean all PRs to be updated/changed to use the CHANGELOG.next.asciidoc yet. We will continue cleaning up the changelog, until things eventually get more stabilisied by everyone using CHANGELOG.next.asciidoc in the future. In order to reduce some friction for other PRs we still have the current changelog entries in CHANGELOG.asciidoc. We will remove the template from CHANGELOG.asciidoc during the next releases. Note: the developers changelog requires quite some cleanup. Switching to CHANGELOG-developer.next.asciidoc will make our lives easier here as well.
* Introduce next Changelog file (#9767) This introduces CHANGELOG.next.asciidoc and CHANGELOG-developer.next.asciidoc. These changelog files will document yet unreleased changes. Having a separate changelog file reduces the work required to cleanup the changelog, as rebasing and cherry-picking on backports sometimes moves changelog entries into the wrong place. (cherry picked from commit eae3bff) * Adapt changelog to 6.x
* Introduce next Changelog file (#9767) This introduces CHANGELOG.next.asciidoc and CHANGELOG-developer.next.asciidoc. These changelog files will document yet unreleased changes. Having a separate changelog file reduces the work required to cleanup the changelog, as rebasing and cherry-picking on backports sometimes moves changelog entries into the wrong place. (cherry picked from commit eae3bff) * Adapt changelog to 6.5 branch
…ic#9808) Cherry-pick of PR elastic#9767 to 6.6 branch. Original message: This introduces CHANGELOG.next.asciidoc and CHANGELOG-developer.next.asciidoc. These changelog files will document yet unreleased changes. Having a separate changelog file reduces the work required to cleanup the changelog, as rebasing and cherry-picking on backports sometimes moves changelog entries into the wrong place. I don't mean all PRs to be updated/changed to use the CHANGELOG.next.asciidoc yet. We will continue cleaning up the changelog, until things eventually get more stabilisied by everyone using CHANGELOG.next.asciidoc in the future. In order to reduce some friction for other PRs we still have the current changelog entries in CHANGELOG.asciidoc. We will remove the template from CHANGELOG.asciidoc during the next releases. Note: the developers changelog requires quite some cleanup. Switching to CHANGELOG-developer.next.asciidoc will make our lives easier here as well.
…ic#9807) * Introduce next Changelog file (elastic#9767) This introduces CHANGELOG.next.asciidoc and CHANGELOG-developer.next.asciidoc. These changelog files will document yet unreleased changes. Having a separate changelog file reduces the work required to cleanup the changelog, as rebasing and cherry-picking on backports sometimes moves changelog entries into the wrong place. (cherry picked from commit faec604) * Adapt changelog to 6.5 branch
This introduces CHANGELOG.next.asciidoc and
CHANGELOG-developer.next.asciidoc. These changelog files will document
yet unreleased changes.
Having a separate changelog file reduces the work required to cleanup
the changelog, as rebasing and cherry-picking on backports sometimes
moves changelog entries into the wrong place.
I don't mean all PRs to be updated/changed to use the CHANGELOG.next.asciidoc yet. We will continue cleaning up the changelog, until things eventually get more stabilisied by everyone using CHANGELOG.next.asciidoc in the future. In order to reduce some friction for other PRs we still have the current changelog entries in CHANGELOG.asciidoc. We will remove the template from CHANGELOG.asciidoc during the next releases.
Note: the developers changelog requires quite some cleanup. Switching to CHANGELOG-developer.next.asciidoc will make our lives easier here as well.