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

  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.6.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 to GitHub
  3. Create and push a signed tag of the release commit
  4. 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
  5. Publicize the release

5.6.3. Post Release Steps

  1. Open a new issue with the Kali bug tracker notifying them of the release
  2. Increment the version number on the dev branch and reset the version label
  3. Update the Python packages list in Pipfile
    1. List the outdated packages with: pipenv update --outdated
    2. Update each one with: pipenv install PACKAGE==VERSION
    3. Manually synchronize docs/requirements.txt