5.5. Release Steps¶
This document contains the steps that are followed for each point version release of King Phisher.
5.5.1. Pre Release Steps¶
- Test and fix any issues with the Windows MSI build
- Ensure unit tests pass with Python 3.4+
- Remove the version label
- Create the final Windows MSI build
- Update the change log
5.5.2. Release Steps¶
- Create a final signed commit on the dev branch and push it to GitHub
- Merge dev into master and push master and push the changes
- Create and push a signed tag of the release commit
- Merge dev into master for the plugins repository and push the changes
- Create a new release on GitHub
- Upload the final Windows build
- Insert the changes from the change log
- Insert the MD5, SHA1 and SHA512 hashes of the Windows build
- Publicize the release
5.5.3. Post Release Steps¶
- Increment the version number on the dev branch and re-set the version label
- Update Python packages list for pip in requirements.txt with piprot
python3 -m pip install -U piprot
sed -e 's/>=/==/g' requirements.txt | \
piprot -x - | \
awk '/# Latest/ {print substr($1, 0, index($1, "==") + 1) $4 }'