SecureDrop Client 0.2.1

[emkll]

Description

Towards #1125 .

Related packaging PR: freedomofpress/securedrop-builder#178

Test Plan

• Changelog is accurate
• Version strings are correctly updated with update_version.sh

[eloquence]

#974 was merged and not released since 0.2.0.

[eloquence]

(That was meant to say #975, sorry for the confusion)

[sssoleileraaa]

this looks like all the user-facing changes since 0.2.0

(waiting on merge, 🚀 on monday)

[eloquence]

Hm, there may have been some discussion that I missed - did we agree to exclude changes that aren't user-facing from the changelog.md? That would be a change compared with e.g. the 0.2.0 log. I personally think it's fine to err on being more comprehensive in the GitHub changelogs, and pare it down for other artifacts for public consumption (blog posts etc.).

[sssoleileraaa]

I think it makes sense to skip refactors, like moving code from one place to another, running black/isort, or just adding a bunch of tests. But I have no objections if we want to include the rest of the changes since we released 0.2.0, which are (see 0.2.0...main):

• Move CSS strings to CSS files and add new CSS tests: Move CSS to CSS files and add new tests for stylesheets #1082
• Reformat the code with black and isort: Add black and isort #1115
• Fix regression in reply box so that journalist designation no longer wraps: fix placeholder label->widget #1112 (this one went out immediately after the regression happened but could still be worth mentioning)

[eloquence]

There's also #975 which I think is significant (functional change, with user-facing implications - syncs may be slowed down by duplicate jobs - but no UI impact). For these two:

• Move CSS strings to CSS files and add new CSS tests: Move CSS to CSS files and add new tests for stylesheets #1082
• Reformat the code with black and isort: Add black and isort #1115

In SD Core we would probably group this under "Developer Workflow" since it does not change functionality.

e88da72 is the merge commit for #975 and should go into the changelog. also eloquence has advice on creating a developer workflow section for the refactors. sorry for all the back-and-fort, emkll!

[emkll]

Thanks for the reviews, CI is passing on the new tag, merging! (see freedomofpress/securedrop-builder#178)