Closed emkll closed 3 years ago
For both upgrades and fresh installs, here is a list of functionality that requires testing. You can use this for copy/pasting into your QA report.
If you have submitted a QA report already for a 1.8.0 release candidate with successful basic server testing and application acceptance testing sections, then you can skip these sections in subsequent reports, unless otherwise indicated by the Release Manager. This is to ensure that you focus your QA effort on the 1.8.0-specific changes as well as changes since the previous release candidate.
There are OS-specific sections in the test plan - make sure you complete the appropriate section based on the server OS in your chosen test scenario.
./securedrop-admin verify
are passing:
cd ~/Persistent/securedrop && ./securedrop-admin setup -t
./securedrop-admin verify
(this will take a while)rm -rf admin/.venv3/ && ./securedrop-admin setup
After updating to this release candidate and running securedrop-admin tailsconfig
fwupd
related OSSEC alert emails on hardware install on Focal #5835. The following two lines contains the error message as examples.
Mar 1 13:22:53 app fwupd[133921]: 13:22:53:0576 FuEngine Failed to load SMBIOS: invalid DMI data size, got 2527 bytes, expected 2745
Mar 1 13:22:53 app fwupd[133921]: 13:22:53:0883 FuPluginUefi Error opening directory “/sys/firmware/efi/esrt/entries�: No such file or directory
./securedrop-admin verify
are passing:
cd ~/Persistent/securedrop && ./securedrop-admin setup -t
./securedrop-admin verify
(this will take a while)rm -rf admin/.venv3/ && ./securedrop-admin setup
After updating to this release candidate and running securedrop-admin tailsconfig
fwupd
related OSSEC alert emails on hardware install on Focal #5835. The following two lines contains the error message as examples.
Mar 1 13:22:53 app fwupd[133921]: 13:22:53:0576 FuEngine Failed to load SMBIOS: invalid DMI data size, got 2527 bytes, expected 2745
Mar 1 13:22:53 app fwupd[133921]: 13:22:53:0883 FuPluginUefi Error opening directory “/sys/firmware/efi/esrt/entries�: No such file or directory
For both upgrades and fresh installs, here is a list of functionality that requires testing. You can use this for copy/pasting into your QA report.
If you have submitted a QA report already for a 1.8.0 release candidate with successful basic server testing and application acceptance testing sections, then you can skip these sections in subsequent reports, unless otherwise indicated by the Release Manager. This is to ensure that you focus your QA effort on the 1.8.0-specific changes as well as changes since the previous release candidate.
There are OS-specific sections in the test plan - make sure you complete the appropriate section based on the server OS in your chosen test scenario.
./securedrop-admin verify
are passing:
cd ~/Persistent/securedrop && ./securedrop-admin setup -t
./securedrop-admin verify
(this will take a while)rm -rf admin/.venv3/ && ./securedrop-admin setup
SOME EXPECTED FAILURES NOTHING THE GOD OF CYBERNETICS WOULDNT LET YOU INTO HEAVEN FORAfter updating to this release candidate and running securedrop-admin tailsconfig
fwupd
related OSSEC alert emails on hardware install on Focal #5835. The following two lines contains the error message as examples.
Mar 1 13:22:53 app fwupd[133921]: 13:22:53:0576 FuEngine Failed to load SMBIOS: invalid DMI data size, got 2527 bytes, expected 2745
Mar 1 13:22:53 app fwupd[133921]: 13:22:53:0883 FuPluginUefi Error opening directory “/sys/firmware/efi/esrt/entries�: No such file or directory
This is a tracking issue for the release of SecureDrop 1.8.1. This minor release will provide improvements to the restore functionality, and update OSSEC rules to support the transition to Ubuntu 20.04 Focal.
Tentatively scheduled as follows:
String and feature freeze: 2021-04-07 Pre-release announcement: 2021-04-08 Release date: 2021-04-14
Release manager: @kushaldas
Deputy release manager: @emkll Communications manager:: @eloquence / @emkll
SecureDrop maintainers and testers: As you QA 1.8.1, please report back your testing results as comments on this ticket. File GitHub issues for any problems found, tag them "QA: Release", and associate them with the 1.8.1 milestone for tracking (or ask a maintainer to do so).
Test debian packages will be posted on https://apt-test.freedom.press signed with the test key. An Ansible playbook testing the upgrade path is here.
QA Matrix for 1.8.1
Test Plan for 1.8.1
Prepare release candidate (1.8.1~rc1)
1.8.1~rc1
on test apt server: https://github.com/freedomofpress/securedrop-dev-packages-lfs/pull/102Final release
release
branch in the LFS repo)release
branch in the LFS repo for the debs)main
in the LFS repo)main
and verify new docs build in securedrop-docs repoPost release
securedrop-docs
and Wagtaildevelop