Skip to content
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

Prepare Changelog for Automation [skip-ci] #509

Merged
merged 1 commit into from
Feb 1, 2021
Merged

Prepare Changelog for Automation [skip-ci] #509

merged 1 commit into from
Feb 1, 2021

Conversation

ajschmidt8
Copy link
Member

This PR prepares the changelog to be automatically updated during releases by updating it to markdown and making it adhere to the same format as other repos' CHANGELOG.md.

@ajschmidt8 ajschmidt8 added improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels Feb 1, 2021
@@ -0,0 +1,187 @@
# 0.18.0

Please see https://github.com/rapidsai/dask-cuda/releases/tag/branch-0.18-latest for the latest changes to this development branch.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean there will be no summary in CHANGELOG.md starting from 0.18?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @pentschev. That's correct. During development, the changes will be recorded in the GitHub Pre-release that's linked. Then at release time, the body of the pre-release will be copied into this file and committed to the repo.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, got it, so it will be done later. Thanks for the info!

@ajschmidt8 ajschmidt8 merged commit e956c3a into rapidsai:branch-0.18 Feb 1, 2021
@ajschmidt8 ajschmidt8 deleted the prepare-changelog branch March 1, 2021 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement / enhancement to an existing function non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants