Version 5 (modified by Cas, 10 years ago) (diff) |
---|
A collection of ideas or improvements for Deluge 2.0 release process:
- Streamline and automate the process further.
- Add git archive line to the make_release script.
- git archive should produce a pristine tar so no need to attempt to modify contents as in current make_release.
- Change to use just sha256sum for file hash verification.
- Create a shasums.txt file
- Reduce number of tarballs provided, so either drop gzip or bzip2 (or both).
- Rename lzma tarball to xz.
- Verify WebUI compressed js files are all included.
- Create the RELEASE_VERSION file in make_release script.
- Add the make_release script to git repo.
- Put all the tarballs, packages and shasum file into one release version folder.
- Do we need both ReleaseNotes and Changelog, could put details from ReleaseNotes into the Changelog.
- Does it make sense to update version and date for the man pages in setup.py?