3 Releasing a New Version, Things to do - nodogsplash/nodogsplash GitHub Wiki
When ready to do a release, do the following:
- conf.h - update version number and copyright eg current year
- Changelog - list changes
- debian/changelog - list changes
- debian/copyright - update copyright dates as required eg current year
- docs/source/conf.py openwrt/Makefile - update copyright notice eg current year, version and release numbers as applicable
- resources/splash.html and resources/status.html - update copyright dates as required eg current year
- "cd docs" then "make man". Copy resulting docs/build/man/nodogsplash.1 to overwrite old debian/doc/nodogsplash.1
- remove /docs/build directory created in step 6
- Push to origin
- Github - Create Pull Request and Merge to master
- Github proceed to "Draft New Release"
- Github tag release as eg. v3.3.0 (remembering the leading "v"") (or use git tag -a v3.3.0 -m "nodogsplash release 3.3.0 " and git push --tags.)
- In your local repository, make a new branch called "stable"
- Push branch "stable" to origin, overwriting the existing "stable". Branch stable is the source for the readthedocs stable documentation at https://nodogsplashdocs.readthedocs.io/en/stable/
- In Master, set version to -beta eg 3.1.1-beta in conf.h, conf.py, openwrt/Makefile