QA and Release 0.6.1

[apyrgio]

Pre-release

Before making a release, all of these should be complete:

• [x] Copy the entirety of these instructions onto a new issue and call it QA and Release version \<VERSION>
• [x] Add new Linux platforms and remove obsolete ones
• [x] Bump the Python dependencies using poetry lock
• [x] Check for official PySide6 versions
  • :warning: Stuck with 6.6.3.1, but it's not an immediate concern (https://github.com/freedomofpress/dangerzone/issues/785#issuecomment-2073099854)
• [x] Update version in pyproject.toml
• [x] Update share/version.txt
• [x] Update the "Version" field in install/linux/dangerzone.spec
• [x] Update screenshot in README.md, if necessary
• [x] CHANGELOG.md should be updated to include a list of all major changes since the last release
• [x] Create a PGP-signed git tag for the version, e.g. for dangerzone v0.1.0, the is created with:

QA

To ensure that new releases do not introduce regressions, and support existing and newer platforms, we have to do the following:

• [x] Make sure that the tip of the main branch passes the CI tests.
• [x] Make sure that the Apple account has a valid application password and has agreed to the latest Apple terms (see macOS release section).
• [x] Create a test build in Windows and make sure it works:
  • [x] Check if the suggested Python version is still supported.
  • [x] Create a new development environment with Poetry.
  • [x] Build the container image and ensure the development environment uses the new image.
  • [x] Run the Dangerzone tests.
  • [x] Build and run the Dangerzone .exe
  • [x] Test some QA scenarios (see Scenarios below).
• [x] Create a test build in macOS (Intel CPU) and make sure it works:
  • [x] Check if the suggested Python version is still supported.
  • [x] Create a new development environment with Poetry.
  • [x] Build the container image and ensure the development environment uses the new image.
  • [x] Run the Dangerzone tests.
  • [x] Create and run an app bundle.
  • [x] Test some QA scenarios (see Scenarios below).
• [x] Create a test build in macOS (M1/2 CPU) and make sure it works:
  • [x] Check if the suggested Python version is still supported.
  • [x] Create a new development environment with Poetry.
  • [x] Build the container image and ensure the development environment uses the new image.
  • [x] Run the Dangerzone tests.
  • [x] Create and run an app bundle.
  • [x] Test some QA scenarios (see Scenarios below).
• [x] Create a test build in the most recent Ubuntu LTS platform (Ubuntu 24.04 as of writing this) and make sure it works:
  • [x] Create a new development environment with Poetry.
  • [x] Build the container image and ensure the development environment uses the new image.
  • [x] Run the Dangerzone tests.
  • [ ] Create a .deb package and install it system-wide.
  • :x: We cannot do so due to https://github.com/freedomofpress/dangerzone/issues/773
  • [x] Test some QA scenarios (see Scenarios below).
• [x] Create a test build in the most recent Fedora platform (Fedora 40 as of writing this) and make sure it works:
  • [x] Create a new development environment with Poetry.
  • [x] Build the container image and ensure the development environment uses the new image.
  • [x] Run the Dangerzone tests.
  • [x] Create an .rpm package and install it system-wide.
  • [x] Test some QA scenarios (see Scenarios below).
• [x] Create a test build in the most recent Qubes Fedora template (Fedora 39 as of writing this) and make sure it works:
  • [x] Create a new development environment with Poetry.
  • [x] Run the Dangerzone tests.
  • [x] Create a Qubes .rpm package and install it system-wide.
  • [x] Ensure that the Dangerzone application appears in the "Applications" tab.
  • [x] Test some QA scenarios (see Scenarios below) and make sure they spawn disposable qubes.

Publishing the Release

To publish the release:

• [x] Run container scan on the produced container images (some time may have passed since the artifacts were built)
• [x] Collect the assets in a single directory, calculate their SHA-256 hashes, and sign them.
  • You can use ./dev_scripts/sign-assets.py, if you want to automate this task)
• [x] Create a new draft release on GitHub and upload the macOS and Windows installers.
  • Copy the release notes text from the template at docs/templates/release-notes
  • You can use ./dev_scripts/upload-asset.py, if you want to upload an asset using an access token.
• [x] Upload the container.tar.gz i686 image that was created in the previous step
• [x] Upload the detached signatures (.asc) and checksum file.
• [x] Update the Dangerzone website to link to the new installers and signatures
• [x] Update the brew cask release of Dangerzone with a PR like this one
• [x] Update version and download links in README.md

(see also the previous QA and Release for 0.6.0)

[apyrgio]

Regarding our PySide6 versions, it seems that we are currently stuck with 6.6.3.1 in all platforms.

• For Fedora 39+, that's because 6.7.0 is in Fedora Rawhide, and will be soon backported, so we don't want to step on their toes (https://github.com/freedomofpress/maint-dangerzone-pyside6/issues/5)
• For Windows and macOS, that's because PySide6 6.7.0 is not compatible with Python 3.8, which is what Ubuntu Focal still installs by default. As a result, Poetry's dependency resolution does not include the latest PySide6 version (https://github.com/freedomofpress/dangerzone/issues/773)

[apyrgio]

Our Windows QA was quite eventful. We have uncovered several issues, both new and old, as well as a noticeable termination delay in some edge cases (#791). I'll send a PR soon that fixes these issue, and unblock our release.

[apyrgio]

Dangerzone 0.6.1 is out :partying_face:. All subtasks have been resolved, so we can now close this issue.