From 41ed031608e3acf26d99c9c51544802ff3ee0f6e Mon Sep 17 00:00:00 2001 From: Kyle Gabriel Date: Sun, 29 Aug 2021 19:12:59 -0400 Subject: [PATCH] update release checklist --- release-checklist.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/release-checklist.md b/release-checklist.md index 7e25fa75e..517ff0fa5 100644 --- a/release-checklist.md +++ b/release-checklist.md @@ -15,9 +15,9 @@ Notes to keep track of the steps involved in making a new release. - Section headers "### Bugfixes", "### Features", and "### Miscellaneous". - Changes as bullet list under each section header, with a link to issue(s) at the end of each short description (if applicable). - [ ] Ensure mkdocs pip requirements are installed by running Mycodo/env/bin/python -m pip install -r Mycodo/docs/requirements.txt - - [ ] Run ```mkdocs build``` to generate Mycodo/site/mycodo-manual.pdf - - [ ] Copy Mycodo/site/mycodo-manual.pdf to Mycodo/docs/mycodo-manual.pdf + - [ ] Run ```mkdocs build``` to generate Mycodo/docs/mycodo-manual.pdf - [ ] Commit changes and wait for TravisCI to finish running pytests and verify all were successful. + - [ ] Clone Mycodo fresh to a new directory and ensure mkdocs pip requirements are installed by running: sudo Mycodo/mycodo/scripts/upgrade_commands.sh setup-virtualenv && Mycodo/env/bin/python -m pip install -r Mycodo/docs/requirements.txt - [ ] Run ```mkdocs gh-deploy``` to generate and push docs to gh-pages branch (for https://kizniche.github.io/Mycodo) - [ ] Optionally, a naive Mycodo system with code prior to the yet-to-be released version can be upgraded to master to test its ability to upgrade (useful if experimental database schema changes are being performed during the upgrade). - [ ] Make GitHub Release