-
Notifications
You must be signed in to change notification settings - Fork 686
Standup Notes 2018 05 17
Participants (alphabetical): Conor, Emmanuel, Erik, Freddy, Harris, Jen, Kushal, Mike, Mickael, Loic
Yesterday: Spinning up new apt server for 0.7.1
Today: Website and infra review to catch up on.
Blockers: None
Yesterday: Support
Today: Support. Some PR review.
Blockers: None
Yesterday: Sprint + 0.7.1 planning + hiring
Today: More sprint follow-up; more hiring work
Blockers: None
Yesterday: On Wednesday, updated kernel testing matrix.
Today: Will be at SF office, more kernel testing.
Blockers: None
Yesterday: Other things
Today: Icons for SecureDrop.org scanner
Blockers: None
Yesterday: A bunch of review. Merged PRs from PyCon. Bumped version numbers on develop. Caught up on IVFs.
Today: Will take a look at crypto library issue.
Blockers: None
No update today
Non-SD work
Today: Config for new SD kernel, using Kevin's patches. Prepping builds
Blockers: None
- Improving formal test plans
- People writing PRs should have a detailed test plan (we have been better about this but not always)
- People reviewing PRs should ask the PR submitter for a test plan or write one themselves
- We should be more strict about this going forward
- The test plan is useful for posterity: what was tested, what was not, etc. We can see when a regression occurs why our test plans were insufficient and make corrections going forward.
- Also describe what the automated tests do. What are the assumptions in the automated tests!
Action items:
- Systematize QA planning for 0.7.1, using the wiki where appropriateional test TBB branch?
Lower priority:
- Parellelize test suite - refactoring needs to be completed
- Testinfra tests could be sped up using GOSS