5.6. Release Steps¶
This document contains the steps that are followed for each point version release of King Phisher.
5.6.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.6.2. Release Steps¶
Create a final signed commit on the dev branch and push it to GitHub
Merge dev into master and push master to GitHub
Create and push a signed tag of the release commit
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.6.3. Post Release Steps¶
Open a new issue with the Kali bug tracker notifying them of the release
Increment the version number on the dev branch and reset the version label
Update the Python packages list in Pipfile
List the outdated packages with:
pipenv update --outdated
Update each one with:
pipenv install PACKAGE==VERSION
Manually synchronize
docs/requirements.txt