Skip to content

Commit

Permalink
Improve the instructions for QA step 10
Browse files Browse the repository at this point in the history
Clarify how can a tester install the previous version of Dangerzone in
the step 10 of the QA.

Closes #597
  • Loading branch information
apyrgio committed Oct 13, 2023
1 parent f02597a commit 8fbed31
Showing 1 changed file with 15 additions and 7 deletions.
22 changes: 15 additions & 7 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -158,9 +158,16 @@ should point the user to the Qubes notifications in the top-right corner:
_(Applies to Linux/Windows/MacOS. For MacOS/Windows, it requires an installer
for the new version)_

Install the previous version of Dangerzone system-wide. Open the Dangerzone
application and enable some non-default settings. Close the Dangerzone
application and get the container image for that version. For example
Install the previous version of Dangerzone system-wide:

* For MacOS/Windows, use the version from the website.
* For Linux, install the previous version using our [installation instructions](INSTALL.md).
In order to run commands as root, execute into the container as root with
`podman -it -u root <container ID> bash`.

Open the Dangerzone application and enable some non-default settings. Close the
Dangerzone application and get the container image for that version. For
example:

```
$ podman images dangerzone.rocks/dangerzone:latest
Expand All @@ -170,10 +177,11 @@ dangerzone.rocks/dangerzone latest <image ID> <date> <size>

_(use `docker` on Windows/MacOS)_

Install the new version of Dangerzone system-wide. Open the Dangerzone
application and make sure that the previously enabled settings still show up.
Also, ensure that Dangerzone reports that the new image has been installed, and
verify that it's different from the old one by doing:
Install the new version of Dangerzone system-wide. For Linux, copy the package
back into the container. Open the Dangerzone application and make sure that the
previously enabled settings still show up. Also, ensure that Dangerzone reports
that the new image has been installed, and verify that it's different from the
old one by doing:

```
$ podman images dangerzone.rocks/dangerzone:latest
Expand Down

0 comments on commit 8fbed31

Please sign in to comment.