-
Notifications
You must be signed in to change notification settings - Fork 685
Sprint Planning Meeting 2019 03 06
https://github.com/orgs/freedomofpress/projects/1
Release feedback
(Erik) Hooray to successful 0.12.0 release! Going forward, I recommend clearer roles/responsibilities. Jen suggested a "deputy" for the RM; I would also recommend official (meaning we have to determine it for each release, and may allow for rotation) QA Lead designation (responsible for reviewing QA matrix at the begginning of stand-up). We can implement light changes for point release.
(Jen) Three roles per release: RM, deputy RM, deputy LM to pair with Kushal so that knowledge of the localization flow is shared around the team
We actually released unreviewed strings in non-English languages for the second time. Move back string freeze. We don't have the smoothest localization process right now, we need to improve this, and in the meantime, we might want to consider moving back string freeze.
+5 to the above comment about moving back string freeze (Kushal), we had trouble to find translators at the last moment this release.
We should consider having the cut tagged earlier in the day to ensure ample time for QA/preflight :+1: from Jen, we need all translations merged in by the beginning of release day to enable this.
(Conor) +1 on knowledge shares for Weblate/localization workflows
Substantial testing/QA load! We lean on Kev heavily for testing/QA; would be great to use Kev more heavily during sprints (pending support obligations), and farm out testing/QA across the team for pre-release checks. Timing of release ceremony: typically it's just the PT folks left logged in (else other timezones are working very long hours)
heartsucker:
- It was extremely tedious to review the translations and we should automate this process before the next release
- Because of timezones, I as the release manager was unable to fulfill all duties. As noted, we should split the release manager role among multiple people in multiple timezones
Jen: To be fair, there is a fair bit of manual work associated with releases, we need to improve all of these things, many of which are in the roadmap for the next few months:
- Builder container updates (manual)
- Application/functional test time (too long)
- Backporting of PRs (manual)
- Application acceptance testing for QA (manual)
- Building of test debian packages (manual)
- Upgrade testing (mostly manual, though facilitated by the molecule upgrade scenario)
- Translation diff review (manual, but only once per release cycle and only really bad when we add languages)
- Testing server state on prod machines (manual)
QA:
- Could leverage QA Matrix (or similar) more to identify testing scenarios and track progress.
- Could automate basic server testing (with testinfra or similar - there's a ticket in for this IIRC)
2019-03-04 : Warning appears in journalist interface: :skull: Time to upgrade to Xenial
2019-03-06 : Official "no earlier than" recommended date for upgrading to Xenial
2019-03-11 to 2019-03-15: Allie in San Francisco, co-working with Conor and Jen
2019-03-12 : SecureDrop 0.12.1 QA begins -- feature/string freeze for release. (No pre-release announcements for point releases.)
2019-03-13 : Allie, Jen at on-site
2019-03-19 : SecureDrop 0.12.1 Release; Tails 3.1 release
Through March, April : Additional outreach, remote support windows and on-sites for Xenial upgrade
Time check: https://docs.google.com/spreadsheets/d/1dh8m1QAuHRmVhJFOdAoU4bbxlTJ98_tUxQr55R9K9lE/edit#gid=0
Proposed:
-
Merge critical documentation updates related to Xenial upgrade procedures ASAP, as upgrades are now underway
-
Release 0.12.1 with most critical Xenial fixes (prioritizing issues likely to cause upgrade failures) && kernel w/ support for 7th gen NUCs (provided no upstream changes required)
-
Create visual design->implementation pipeline, starting with basic client window / source list / conversation view design (just messages, no files)
https://docs.google.com/spreadsheets/d/1RNPKas1OuaqnIOs8jVUjyAokq3TozXy-lahIqpxiE6U/edit#gid=0
(Async updatE)
Yesterday:
- [SD] Network firewall setup
- [SD] PR for removing cssmin dependency was merged into SD
- weblate and localization lab orientation with Kushal
- [SDC] Client UX meeting - plan to focus on the visual design of the client to look more like nina's wireframes rather than adding new features
Today:
- [SDC] Meet up with Nina midday - discuss main window design
- [SD] Network firewall (redo setup)
- [SDC] Timebox segfault client issue #248 to 2 hours
Blockers:
- I was setting up my network firewall last night and am no longer able to connect to the firewall admin interface (plan to reset and start over)
Yesterday:
- On-site for Xenial upgrade
- PTO for long weekend
Today:
- Start porting of Upgrade box logic to Xenial
- Review wifi package removal PR
- Non-SD meetings
Blockers:
Yesterday:
- Support client followup
Today:
- Main task: Xenial followup with clients
- Preparing bulk announcement messaging
- Xenial scheduling with clients
- Standard support
- Client prospect followup
Blockers:
(None)
Yesterday: Mostly at onsite doing a Xenial upgrade yesterday
Today:
- Might do another organization's Xenial upgrade (LPL)
Blockers:
None
Yesterday:
- Xenial upgrade issues
- Localization orientation
Today:
- Xenial upgrade issues
- Meetings
Blockers:
- None
Today:
- Started moving the SecureDrop Application code base into Python3 https://github.com/freedomofpress/securedrop/pull/4239 Tomorrow:
Blockers:
- None
Yesterday: Upgraded the discourse forum
Today: All web dev container work
Blockers: None
Yesterday:
- Met with Allie/Erik/Jen to coordinate Client UX things
- Began work on updating Download & Briefcase flows per feedback in prior UX meetings
Today:
- Sprint Planning
- Meeting with Allie in Portland to pick-apart/scope how to get UX reflected in existing Client build with as-is features
- Closing Download, Briefcase tickets
- Continuing work on VisDe progress
Blockers:
- None!