Skip to content
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.2.0 and securedrop-proxy 0.3.0 #547

Closed
5 tasks done
redshiftzero opened this issue May 6, 2020 · 2 comments
Closed
5 tasks done

Release securedrop-client 0.2.0 and securedrop-proxy 0.3.0 #547

redshiftzero opened this issue May 6, 2020 · 2 comments

Comments

@redshiftzero
Copy link
Contributor

redshiftzero commented May 6, 2020

There are two packages for the workstation subprojects that are ready for pre-release QA:

Next steps:

  • Define test plan based on changelogs in those above PRs. That will be linked here.
  • Perform QA using nightly packages (if something else is ready for merge in proxy/client we can stop the nightlies temporarily). QA reports should be posted as responses to this ticket and tickets filed in the appropriate repositories for any issues (if you're not sure where a bug report should go please ask and we can point you in the right direction).
  • Final package release https://github.com/freedomofpress/securedrop-debian-packaging/releases/tag/0.2.9
  • Merge docs
  • Let pilot orgs know of any fixes that are relevant for them
@eloquence
Copy link
Member

eloquence commented May 6, 2020

FYI I started putting outlines for testing in https://github.com/freedomofpress/securedrop-workstation/wiki/Workstation-Beta-Acceptance-Tests#release-specific-test-plans ; happy to help flesh those out further and add to relevant PRs.

@emkll
Copy link
Contributor

emkll commented Jun 1, 2020

Client and proxy packages, as well as communications and docs have been published.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants