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

[RELEASE] cugraph v0.15 #1116

Merged
merged 878 commits into from
Aug 26, 2020
Merged

[RELEASE] cugraph v0.15 #1116

merged 878 commits into from
Aug 26, 2020

Conversation

GPUtester
Copy link
Contributor

❄️ Code freeze for branch-0.15 and v0.15 release

What does this mean?

Only critical/hotfix level issues should be merged into branch-0.15 until release (merging of this PR).

What is the purpose of this PR?

  • Update documentation
  • Allow testing for the new release
  • Enable a means to merge branch-0.15 into main for the release

raydouglass and others added 18 commits August 19, 2020 12:59
…gression. Fixed some search-and-replace errors in comments, added more detail about k to the BC docstring.
[BUG] Removed unnecessary device-to-host copy which caused a performance regression
[REVIEW] New build process script changes
[REVIEW][skip-ci] new notebook for benchmarking
[REVIEW] Update CI scripts to remove references to master [skip ci]
The change log check was updated in branch-0.15 but both master and main have an older version of the ci/checks/changelog.sh. Without the forced checkout this will break and not complete the check successfully.
[BUG] Added new release.ipynb to notebook test skip list
@GPUtester GPUtester requested review from a team as code owners August 24, 2020 18:57
@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

Review Jupyter notebook visual diffs & provide feedback on notebooks.


Powered by ReviewNB

@BradReesWork BradReesWork merged commit 652160e into main Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.