Destroyed Release Checklist (markdown)

Jeremy Stretch 2018-08-02 11:53:52 -04:00
parent a52f218fc6
commit 984119f09e

@ -1,31 +0,0 @@
# Pre-Release
## Minor Version Bumps
* Update `requirements.txt` as appropriate
* Update all static CSS/JS libraries to their latest stable versions
* Perform a new install of the `develop` branch following [the current documentation](http://netbox.readthedocs.io/en/latest/)
## All Releases
* Verify that the `develop` branch is completing CI successfully
* Update `VERSION` in settings.py to reflect the number of the new release
* Submit a PR to merge `develop` into `master`
* Title the PR "Release vX.Y.Z"
* Include a brief change log listing the features, improvements, and/or bugs addressed in the release
* Merge PR once CI has finished successfully
* Create a new release
* **Select the MASTER branch**
* Create a new tag for the version number in the format `vX.Y.Z`
* Name the release in the format `vX.Y.Z - YYYY-MM-DD`
# Post-Release
## Minor Version Bumps
* Close out the release milestone
## All Releases
* Update `VERSION` in settings.py to reflect the upcoming release (e.g. `1.2.3-dev`)
* Announce the release on the [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss)