-
Notifications
You must be signed in to change notification settings - Fork 684
Standup Notes 2018 04 26
Participants (alphabetical): Conor, Emmanuel, Erik, Freddy, Harris, Jen, Kushal, Mike, Mickael, Loic Async updates: Erik
- New website! https://securedrop.org
- Open issues
Yesterday: New securedrop.org website, it's beauts. No code open source YET but we're working on it. If you notice problems get loud.
Today: Working on granting Mickael access to our apt-test.freedom.press infrastructure since he is RM.
Blockers: None
Yesterday: Lots of client support, including website cleanup
Today: Lots of client support
Blockers: None
Yesterday: [async update] Post-deployment QA on SDO, observing SD training.
Today: Catching up on release issues, hiring; more SD training.
Blockers: None
Yesterday: Mostly spent time debugging hardware.
Today: What's QA strategy? (We'll discuss during long-form SD Eng in several minutes)
Blockers: Need clarity on QA strat
Yesterday: New website! Hurray!
Today: Follow-up on many requested improvements to new website
Blockers: None
Yesterday: Reviewed release process taking shape. Resolved GUI branch issues with Kushal.
Today: Starting QA as soon as test debs are up. Also some HTTPS sdconfig bug (will toss to Freddy for QA)
Blockers: None
Yesterday: Qubes journalist UI discussion. Also Tails updater GUI fixes.
Today: Jumping onto QA train!
Blockers: None.
Yesterday:
Today: [absent]
Blockers:
Yesterday: SDO launch
Today: Cleaning up some backend logging
Blockers: None
Yesterday: Branched for 0.7 release. Suggesting rebranch—let's discuss during long-form SD eng.
Today: Maybe rebranch prior to pushing tags.
Blockers: None
- 0.7: Jen proposal: We rebranch release/0.7 with #3300 since we didn't actually push any tags due to an outstanding issue on the new SD.org website
Long-form meeting:
- Let's re-branch to accommodate GUI inclusion
- 3309 should be merged as well to include in branch
- We're modestly violating our release practices, but well intentioned, so let's do it
- Let's consider testing backups as regular QA process as well
- HTTPS should be tested as well, with self-signed certs (since we don't have EV certs to test with)
- Test plan is here: https://github.com/freedomofpress/securedrop/issues/3307
- Suggested for inclusion here: https://github.com/freedomofpress/securedrop/issues/3305