-
Notifications
You must be signed in to change notification settings - Fork 686
Standup Notes 2019 04 24
Participants (alphabetical): Allie, Conor, Erik, Heartsucker, Jen, John, Kevin, Kushal, Mike (async), Mickael
(Mickael/John) Release update
Two unrelated pinentry issues:
-
OSSEC alerts on pinentry-gtk2 which was not permitted within AppArmor profile
-
PINENTRY_LAUNCHED issue when deleting a source - GPG library would not understand response when deleting a secret key
Plan to prepare RC2 by EOD
Yesterday:
- worked on issue 280, including code documentation and test
Today:
- sync with kushal on issue 241
- submit PR for issue 280
- start on issue 300
- submit some small fixes for #301 and dropdown arrow
- break down issu 272 conversation styling -- sync with nina
Blockers:
- none
Yesterday:
- Working in Seattle on infra stuff
Today:
- Working in Seattle on infra stuff, standing by for release
Blockers: None
Yesterday:
- Support tasks
- First draft of release notes - https://docs.google.com/document/d/1BtMUu8in3OHoI-GZSyBC45JL19-dHWdEOv54gNd6w-0/edit#
- Repro on https://github.com/freedomofpress/securedrop/issues/4362
Today:
- Finish up release comms & upgrade guide
- Support tasks
Blockers:
None
Today:
- Digging into how we're handling API calls and threading in the client, may want to change architecture and offload timeout handling into the SDK
Tomorrow: Back on Monday
Blockers: None
Yesterday:
- Did none of the things I said I would due to upcoming release getting spicy
- made PR to handle that Pinentry valueerror, marked wip such that we can understand the pinentry-gtk/curses behavior
- last night installed Trusty fresh on my Mac minis, and installed 0.12.1 in prep for cron-apt simulated upgrade to 0.12.2~rc1 today for QA
Today:
- Understand the pinentry gtk/curses behavior (i.e. why Kushal didn't see this error when installing pinentry-gtk) such that we can merge #4365
- Other 0.12.2 issues as needed
- QA 0.12.2~rc1
- THEN back to tasks from yesterday if there is more time in the day
Blockers:
Yesterday: Release testing and PRs as noted above
Today: ^^
Blockers: None
Yesterday: client onsite Today: In transit, working on miscellaneous docs tickets due to lack of access to QA hardware
Blockers: departures terminal boredom
Yesterday:
- Reproducing reported release issues - pinentry as discussed
- Was not able to repro session issue
Today:
- Sync with Allie
Blockers: None
Yesterday:
Today:
Blockers:
Yesterday: Fighting my workstation
Today: Hunting for the next kubernetes whale
Blockers: Release changes tweak the redmine roll-out so punting that to next Tuesday (april 30th)