v2.0-rc-4
Pre-release
Pre-release
v2.0-rc-4 is mainly an update to documentation in preparation to the official v2.0 release.
Highlights include:
- Updated logo
- Improved organization of docs
- More resources for docs (figures/diagrams, etc)
- Removed minor bug in Result.get_values
Notes:
Release Notes - Resilience Analysis and Design - Version fmdtools 2.0-rc-4
Story
- [RAD-241] - Release documentation update
Full Changelog: v2.0-rc-3...v2.0-rc-4
<style> </style>Step | Description | Complete? | Comment |
---|---|---|---|
1 | Sync appropriate branches into release branch | x | |
1a | "Internal branches (e.g. main dev)" | x | |
1b | "External branches (e.g. main)" | x | |
2 | Run script run_all_tests.py and verify test results are appropriate | x | |
2a | "Run full tests" | x | |
2b | "Regenerate badge" | x | |
3 | Update version numbers in appropriate files | x | updated to 2.0-rc-4 |
3a | "Check files conf.py LICENSE.py README.py Intro_to_fmdtools.md pyproject.toml" | x | |
3b | "Run a repository-wide search for the version number" | x | |
4 | Generate the documentation using "./make html" | x | |
5 | Commit and tag branch with the appropriate version. | x | |
5a | "git tag -a v2.x.x -m 'version 2.x.x'" | x | |
6 | Sync to remotes | x | |
6a | "Push release branch to github and internal remotes" | x | |
6b | "Push docs using git subtree push --prefix=_build/html public gh-pages " |
x | |
7 | Create a release in GitHub | x | |
7a | "incorporate a narrative summary of features and changes" | x | |
7b | "incorporate the auto-generated bitbucket release notes." | x | |
8 | "Update project plan" | x | |
8a | "Include any changed dependencies" | x | |
8b | "Include version in schedule" | x | |
8c | "Identify and include additional changes/activities" | x | |
9 | Update/check external CI resources as needed | x | |
9a | "CodeFactor" | x | |
10 | If release is 'stable' Upload to PyPI (see below | x |