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

Ginkgo 1.1.0 minor release #362

Closed
24 of 26 tasks
tcojean opened this issue Oct 14, 2019 · 1 comment
Closed
24 of 26 tasks

Ginkgo 1.1.0 minor release #362

tcojean opened this issue Oct 14, 2019 · 1 comment
Assignees
Milestone

Comments

@tcojean
Copy link
Member

tcojean commented Oct 14, 2019

This issue is here to track the creation of the first Ginkgo release, which could be version 1.0.0 if we can get several CUDA conversions.

I created a milestone to track the release process, I added every issue and PR that we want for the release to this milestone. If you want something in particular to be part of this release, add an issue and add it to the release milestone.

TODO

  • Create a release milestone and issue.
  • Update and check Current NOT_IMPLEMENTED kernels #286
  • Review and potentially update the wiki page for how to release Ginkgo.
  • Create PRs to fix the open bugs which can be fixed, at least partially.
  • Update the known issues page
  • Compile a list of functionalities present in the future release.
  • Update the external library's commit version.
  • Merge the relevant open pull rquests
  • Ensure the milestone reached completion.
  • Create a release/1.1.0 branch
  • Update the version number everywhere appropriate. Double check any link.
  • Run the CI pipelines and ensure there are no unexpected problems.
  • Ensure there are no quick simple to fix problems (iwyu, sonarqube, clang-tidy)
  • Ensure the release/1.1.0 branch compiles with Windows (MINGW, maybe Visual studio if merged)
  • Update any explicit reference to develop in the Readme or the CMakeLists.txt to master.
  • Create a PR for merging the release branch into master.
  • Add a tag to master to the new release.
  • Compile both release and debug linux binaries with CPack, ensure they pass all tests and are complete.
  • Use Github's release system to create a new release with the previously created tag. Add the release notes (functionalities present in this release) and compiled binaries.
  • Merge back from master to develop. Do not select the changes replacing develop to master.
  • Update the website to point on the master branch's documentation instead of develop?
  • Update the website to advertise the release?
@tcojean tcojean added this to the v1.1.0 milestone Oct 14, 2019
@tcojean tcojean self-assigned this Oct 14, 2019
@tcojean
Copy link
Member Author

tcojean commented Oct 16, 2019

Here is an initial version of the 1.1.0 release notes. Feel free to contribute.

https://github.com/ginkgo-project/ginkgo/wiki/Release-1.1.0-Notes

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

No branches or pull requests

1 participant