-
Notifications
You must be signed in to change notification settings - Fork 686
Standup Notes 2018 09 07
Participants (alphabetical): Conor, Emmanuel, Erik,, Jen, Kevin, Kushal, Mike, Mickael, Nina
No reports so far
Yesterday: 0.9.1, some review on the workstation front
Today: Focusing on SD, Xenial staging VMs; workstation review
Blockers: Review on an outstanding PR for Xenial, but no urgency; Mickael, could use help with salt config review
Yesterday: SD Support, assisting team with writing for 0.9.1
Today: SD Support re 0.9.1 as needed, non-SD work otherwise
Blockers: None
Yesterday: 0.9.1, hiring. Also walked through Qubes experience with Nina and reviewed her first sketches. Great ideas - most important conceptually the idea of trash state (vs. permanent deletion). Will be scheduling design review session with the whole team next week.
Today: More hiring fun. Fixing forum links. Cross-project review of backlogs and timelines.
Blockers: None
Yesterday: 091, looked into why CI job for GUI was flaky. Looked into CI rebase issue that I hit during 090.
Today: ^^, work on client
Blockers: None
Yesterday: 091, support
Today: 091, docs changes, functional testing
Blockers: None
Yesterday: Had a call with Jen about proxy design. Trying to figure out how to keep templates in Qubes up-to-date.
Today: Will update issue re: updates with my initial findings on how to manage updates.
Blockers: None
*Yesterday: Launched forum on our infrastructure. Had issue with setting up redirects.
Today: Have to do proper 302 redirect. May have to have brief downtime on .club.
Blockers: None
Yesterday: 091; opened two small PRs, one to automatically update the bandit/safety checks in CI, the other was backporting 091 changelog into develop
Today: Working on OSSEC upgrade. Will have fixes in shortly.
Blockers: None
Yesterday: Reviewing wireframes/Qubes.
Today: Will be posting those to wiki with summary and notes. Share at design review next week.
Blockers:
- dev/staging and prod deviation
Installing test dependencies in staging is the root cause. In future revision we would use test CI job that would run those application tests in container.
Functional testing push would have caught it. They would have been run outside the server.
Conor: Need to ensure multiple requirements files updated in PRs.
Kushal: Potentially move more to using packages instead of pip.
- updater bug
We were testing via CLI, not via network hook.
Integration tests for securedrop-admin -- specific tests for cwd
Kev: Keeping track of manual testing plans in tickets is painful.
Jen: Open to other ways of doing it.
Graphical updater: We do have coverage of update-related CLI functions. We don't test network hook and working directories.
Additions to standard test plans:
- make sure updater pops up
- make sure that update occurs without issue
- formal test plan for API