Skip to content

Sprint Planning Meeting 2022 04 27

Jump to bottom
Erik Moeller edited this page Apr 28, 2022 · 2 revisions

Sprint Planning Meeting, SecureDrop, 2022-04-27

Sprint timeframe: Mid-Day (PST) 2022-04-27 to Mid-Day (PST) 2022-05-11

1) Review previous sprint priorities
  • Complete SecureDrop Workstation release train

Status: SecureDrop Client 0.7.0 released

  • Land first round of Qubes 4.1 compatibility improvements

Status:

Status: https://github.com/freedomofpress/securedrop/pull/6315 undergoing final review.

Other notes:

  • fwupd warnings should no longer occur; may revisit fwupd use in future
2) Retrospective

(Focus on SecureDrop Client 0.7.0 release)

What worked well:

  • Great proposal, revision, and coordination of per-RC test plans
  • pairing on release mechanics was really helpful/good learning experience(+1 as in let's do it again now that I'm back! :P) (+1, also looking forward)
  • Best QA we've ever had +1 thank you all!

What can be improved:

  • Some confusion about RC-level regressions versus standing bugs (which led to reversions) (+1)

  • a bit more planning ahead re: decision to pause nightlies or not (although it sounds like kunal's PR has solved/partially solved this)

  • We are 'double-testing' PRs/features (this applies everywhere)--maybe we can decide on a rigorous test strategy for PRs and a regression-testing strategy during release QA? Or another solution? (Test plan for QA often duplicates test plan for PRs, not sure if this is best use of time?)

  • [cfm] I thought one of the revisions helped with this, effectively by letting stress-testing stand in for step-by-step testing of its constituent flows. :)

  • [group] exploratory "how can I break this" testing (user-level test-plan fuzzing :-)

  • an opportunity to make testing a creative rather than rote encounter

  • Small tweaks in the packaging logic to reduce number of manual steps (kunal has started some work on this already) +1, a lot can be automated I think

  • Documentation can be cleaner for workstation config and component releases (in part this is because process has changed a lot each iteration)

What's still a mystery:

  • replicable, shareable end-to-end test scenarios at loaddata.py scale
3) Key dates and time commitments
  • Erik alternating 48+PTO / 410, always off Fridays
  • Cory @ 4*10 Mon-Thu
  • Allie @ 3*10 Mon-Wed
  • Ro @ ~4*8-10 Mon-Thu
  • Giulio ~20 hours/week
  • Gonzalo back at ~20 hours/week Mon-Wed
  • Abigail PTO Friday 5/3/2022
  • Tina @ 4*10 / Mon-Thur
2022-04-28   : Conor's last day :-(
2022-05-03   : Tails 4.30 or 5.0 (see https://tails.boum.org/contribute/calendar/)
               QA begins for SecureDrop 2.4.0

After sprint:

2022-05-17   : SecureDrop 2.4.0 release
2022-05-18/19: Ro PTO
2022-05-26/27: Kunal PTO
2022-06-??   : birthday PTO for some of the first week, tbd.:tada:
Early May    : Potential translation launch for SecureDrop Client
2022-05-31   : QA begins for SecureDrop Workstation releases
2022-06-??   : Ro PTO (1.5wk?) to move
2022-06-07   : SecureDrop Workstation releases
2022-07-04   : SecureDrop release key expires
2022-08-02   : Debian Buster EOL / Qubes 4.0 EOL

Vulnerabilities triage: Kev Support triage: Allie/Gonzalo

4) Review top sprint priorities
1) Complete key deliverables for SecureDrop 2.4.0 and begin QA

Rationale: Release trains always take priority over non-critical ongoing work.

  • RM: TBD / maybe Kev
  • Deputy RM: Michael
  • LM: Cory
  • CM: Erik
2) Land initial SecureDrop Workstation 4.1 compatibility PR, and complete a round of testing on sys-USB changes

Rationale: 4.0 EOL coming up in August.

  • Gonzalo: 4.1 very fresh install testing
  • Allie: Template testing
  • Allie/[TBD, Ro/Gonzalo]: sys-usb testing
5) Review project board

https://github.com/orgs/freedomofpress/projects/1

Clone this wiki locally