-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release securedrop-client 0.9.0 #1637
Comments
The changes in https://github.com/freedomofpress/securedrop-builder/pull/402/files moved the We either have to back out the rename for 0.9.0, or ship an RPM at the same time that includes the change. Even if we ship an RPM, we'd have to carefully think through the order of update operations to avoid first-run errors. |
Looks like the workstation rpm with the change, 0.7.1, was staging-only to unbreak testing against nightlies. It wasn't tagged and the commit wasn't recorded in the build log 😢 so we can't use it as is and would have to cut a new one anyway. My vote would be to back out the change for now. |
I'd vote for releasing this with both the new |
RC2 installed and the icon thing is sorted. Test plan also coming together so I think we're pretty much go for QA. Will add some notes on switching to the RC version in a prod workstation. |
Test PlanInstructions: It is helpful to have real-world scenarios simulated in the test plan, so if you don't get through every single Export or Download scenario, that's fine. You are encouraged to creatively test the interactions between features (eg by prompting a download and then exporting, or interrupting network connectivity, etc). Basic acceptance test scenarios have not been enumerated, but can be found here if you are looking for a reference for expected client behaviour. You will need a LUKS-encrypted Transfer Device and/or an SDW compatible printer to complete the export or print testing portions. Test EnvironmentUse a modified prod setup as per parent comment. Hardware: document your hardware specs here TestingPR: #1639
PR: #1388
Export All/Export Transcript Assumptions (for general QA of export features):
PR:
PR: #1486
|
With Test Environment
Hardware:
TestingPR: #1639
[user@dom0 ~]$ $(cat ~/Desktop/securedrop-launcher.desktop | grep "^Exec=" | sed "s/Exec=//")
—where "localized" here means "adjusted for time-zone", per #1626 towards #1536.
sdadmin@app:~$ sudo -u www-data /var/www/securedrop/loaddata.py --source-count 2 --messages-per-source 12 --files-per-source 12 --replies-per-source 12
Created journalist (username=clarkkent, password=correct horse battery staple profanity oil chewy, otp_secret=JHCOGO7VCER3EJ4L, is_admin=False)
Created source 1/2 (codename: 'cosmos margarita conform reaffirm untoasted promoter connected', journalist designation 'grass-covered meat', files: 12, messages: 12, replies: 12)
Created source 2/2 (codename: 'goatskin pouring upturned extrovert laptop bullish grudge', journalist designation 'omnivorous confession', files: 12, messages: 12, replies: 12)
PR: #1388
Export All/Export Transcript Assumptions (for general QA of export features):
PR:
NB. Visible menu item is
amnesia@amnesia:~$ dd if=/dev/urandom of=Tor\ Browser/10mb bs=1024 count=10000
10000+0 records in
10000+0 records out
10240000 bytes (10 MB, 9.8 MiB) copied, 0.127465 s, 80.3 MB/s
amnesia@amnesia:~$ dd if=/dev/urandom of=Tor\ Browser/1mb bs=1024 count=1000
1000+0 records in
1000+0 records out
1024000 bytes (1.0 MB, 1000 KiB) copied, 0.0191366 s, 53.5 MB/s
amnesia@amnesia:~$ dd if=/dev/urandom of=Tor\ Browser/3kb bs=1024 count=3
3+0 records in
3+0 records out
3072 bytes (3.1 kB, 3.0 KiB) copied, 0.000355652 s, 8.6 MB/s
PR: #1486
|
@cfm For extra clarity: are you pointing out at the fact that #1626/#1636 is/are missing from the list of PRs in that testing step (my mistake), or that the PR is missing from the release (would be unexpected)? |
You got out of your way to test this! The adjusted test plan seems sound to me 👍 |
👍 Thanks @cfm. I was actually confused about that, thanks for pointing it out. Rewording: the timestamps/dates are still written "in English", but match your local time zone. |
Test PlanTest EnvironmentUse a modified prod setup as per parent comment. Hardware: Lenovo X1 Carbon 6th-gen TestingPR: #1639
PR: #1388
Export All/Export Transcript Assumptions (for general QA of export features):
PR:
PR: #1486
|
One error hit so far with transcripts. See: #1643 Otherwise the test plan checks out! |
Print update: No issues printing transcripts (as long as avoiding #1643) on both an HP-4001dn and on Brother HL-2360DW. |
Quick testing with RC3 indicates it does fix the transcript export/print crash issue. More testing TK. |
With Test Environment
Hardware:
TestingPR: #1639
Same as #1637 (comment).
PR: #1388
Export All/Export Transcript Assumptions (for general QA of export features):
Also confirmed that a transcript exported under
PR:
PR: #1486
|
The release is done. |
This issue tracks the SecureDrop Client release 0.9.0. It will be organized by:
This release includes the following changes:
SecureDrop maintainers and testers: As you QA this release, 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 release milestone for tracking (or ask a maintainer to do so).
Test plan
Available below. Please post results as a comment to this issue.
LANG=en_XA
) QA per https://github.com/freedomofpress/securedrop-workstation/wiki/Workstation-Acceptance-Tests#internationalization-referenceInstalling an RC in a production workstation:
sd-app
if it's runningcat <keyfile>
> testkey.sec" (qrexec policies prevent directqvm-copy
tosd-small-bullseye-template
)/etc/apt/sources.list.d/securedrop_workstation.list
, changingapt.freedom.press
toapt-test.freedom.press
Release tasks
main
MANIFEST.in
export LANG=es_ES.utf-8; dpkg-reconfigure locales
), run the Client, and confirm that the application is translated.The text was updated successfully, but these errors were encountered: