From 07bd4261f58e806b74ea7c3242b234e47e025b8b Mon Sep 17 00:00:00 2001 From: Matthias Maier Date: Tue, 24 Apr 2018 13:11:32 -0500 Subject: [PATCH] add a short release step list to use as a github check box --- release-tasks-github-list | 58 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) create mode 100644 release-tasks-github-list diff --git a/release-tasks-github-list b/release-tasks-github-list new file mode 100644 index 0000000..4f93acd --- /dev/null +++ b/release-tasks-github-list @@ -0,0 +1,58 @@ +Check list for https://github.com/dealii/release-papers/blob/master/release-tasks +================================================================================= + +Release preparation steps: https://github.com/dealii/release-papers/blob/master/release-tasks + +- [ ] -3 Send out notice to the mailinglist if anyone has outstanding issues or patches. +- [ ] -2 Check all issues and pull-request on github. Create a list of things to fix before the release. +- [ ] -1 Update the list of publications. (Send standard e-mail) +- [ ] -1a Start release paper process with email to all current (principal) developers +- [ ] -1b Update the authors list on the homepage authors.html +- [ ] -1c Update the list of contributors in the release paper +- [ ] 0 Do some basic testing as always +- [ ] 0a Rerun cppcheck across the source files +- [ ] 0b Check for doxygen formatting problems +- [ ] 0c Fix formatting bugs reported by various command line queries +- [ ] 0d Check that doxygen produces no errors when generating offline docs. +- [ ] 0e Run the copyright script +- [ ] 0f Update Trilinos and PETSc to the latest release on the tester and update documentation of supported version. +- [ ] 0g Run codespell + +Release steps: + +- [ ] * Nominate a "release officer" that is in charge of (almost all) of the following steps + +- [ ] 1 Create new changes file +- [ ] 1a Adjust doc/users/doxygen.html to link to the to-be-created TAG file. +- [ ] 4 Create a release branch +- [ ] 5 Update the VERSION from 9.0.0-pre to 9.1.0-pre on master +- [ ] 6 Update the official tester to test on the release branch dealii-9.0 +- [ ] 6a On mainline, update deal.II dependencies of examples +- [ ] 7 Create an AUTHORS file +- [ ] 7a Send prerelease announcement to dealii@googlegroups.com +- [ ] 8 Remove unfinished tutorial programs. +- [ ] 9 Write up a short release note and save it as announce-9.0 +- [ ] 9a Write the release paper +- [ ] 10 Test the branch thoroughly +- [ ] 10a Do the same for the code gallery examples +- [ ] 11 Create documentation and verify + +- [ ] 12 Push the button + - Change VERSION to 9.0.0 for a release and to 9.0.0-rc1 for a pre-release + - Create a signed tag of exactly this commit + - Push changes to github +- [ ] 13 Create the tar files + - Download the source tarball from github, verify that its contents is what we expect + - Cryptographically sign it (detached, armored signature) + - Create full offline_doc tarball and sign it +- [ ] 14a Create a pre-release on github and upload files (and detached signatures) +- [ ] 15 Generate the documentation on the webserver. +- [ ] 16 Adjust header.include on homepage +- [ ] 17 Ask Luca for Mac packages +- [ ] 18 Finish writing the announcement +- [ ] 18b Adjust news.html in the deal.II homepage repo +- [ ] 19 Announce the release via e-mail +- [ ] 19a Send a note to the Facebook and Google+ accounts +- [ ] 19b Update the deal.II wikipedia page +- [ ] 19d Send thank-you email and list the people already referenced in step -1b above +- [ ] 20 Celebrate! -- 2.39.5