Closed yidong72 closed 4 years ago
Please update the changelog in order to start CI tests.
View the gpuCI docs here.
We should add a "CHANGELOG.md". What do you think? I can merge this or maybe we should make one more PR on develop branch to add a changelog. Additionally, maybe we should fix up gpuCI scripts. I never got around to fixing those.
The changelog is good. I thought you have a way to automatically generate it. Let me spend some time to investigate it. Let's add the changelog in this PR. In the meanwhile, could you take a look into gpuCI ? That can be useful for the development branch.
I just played with the gren tool. It looks like we need to first release it then use it to genrate the chagnelog. This is the result I got when I run it under master branch:
Initial release.
Shall we first relase the v0.5 and generate the changelog?
It seems a bit backward to first make a release then generate a changelog.
Could you try this other tool. https://github.com/github-changelog-generator/github-changelog-generator
I ran it like this:
export CHANGELOG_GITHUB_TOKEN=<MY TOKEN>
github_changelog_generator --future-release=0.5 --release-branch=develop -u rapidsai -p gQuant
I used the develop as release branch to generate a log with latest commits on develop branch. Otherwise these don't show up. After generating the changelog it should be added to repo and then we make a release.
========================================================
Implemented enhancements:
Fixed bugs:
Closed issues:
Merged pull requests:
Merged pull requests:
Implemented enhancements:
Fixed bugs:
Closed issues:
Merged pull requests:
Implemented enhancements:
Fixed bugs:
Merged pull requests:
Implemented enhancements:
Fixed bugs:
Merged pull requests:
* This Changelog was automatically generated by github_changelog_generator
I added the change log
Let's have a RAPIDS 0.5 release since we have tested the notebooks thoroughly.