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

  1. Test and fix any issues with the Windows MSI build
  2. Ensure unit tests pass with Python 3.4+
  3. Remove the version label
  4. Create the final Windows MSI build
  5. Update the change log

5.5.2. Release Steps

  1. Create a final signed commit on the dev branch and push it to GitHub
  2. Merge dev into master and push master and push the changes
  3. Create and push a signed tag of the release commit
  4. Merge dev into master for the plugins repository and push the changes
  5. Create a new release on GitHub
    1. Upload the final Windows build
    2. Insert the changes from the change log
    3. Insert the MD5, SHA1 and SHA512 hashes of the Windows build
  6. Publicize the release

5.5.3. Post Release Steps

  1. Increment the version number on the dev branch and re-set the version label
  2. 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 }'