Skip to content

Standup Notes 2019 09 05

Jump to bottom
Erik Moeller edited this page Sep 6, 2019 · 1 revision

Participants (alphabetical): Allie, Conor, Erik, Jen, John, Kevin, Kushal, Mickael, Nina

Topics and Call-outs

1.0.0 updates:

  • We have backports into RC2 #4745 (tailsconfig changes), #4747 (update_version changes), the tag has been pushed and deb packages also got pushed into LFS and merged.

  • No one yet marked to pick up the tests on Mac mini (based on QA matrix)

    • Kev will take Mac Minis after other testing tasks are completed

  • Build log management discussion

    • Goal: What is this protecting against and what is it not protecting against?

      • Does not protect against a malicious insider

      • Does not protect against compromised pip dependencies, that is done via hashes in the rquirementes file

      • Does not protect against compromised build machine

      • The goal here is to have a clear record of what happened, which can help us in retro if mistakes are made during the prod build (since some of this is manual) and for incident response

    • Proposal: We basically save the terminal session starting with:

      • Checking out the prod tag and verifying it
      • Make build-debs - verbose enough?
      • sha256 the debs at this point
      • sign and stop here for rc build
      • Ending with cat-ing the release file since they contain the hashes of the debs, Release, Release.gpg
      • entire thing signed

Action: We'll adopt this process for RC3 and, likely, subsequent RCs and releases

Allie

Yesterday:

  • Worked on running export tests from the client, was able to see many of the different types of errors
  • Finished a happy-path end-to-end export from the client

Today:

  • Now write the code to create the real export archive
  • Add logic in the UI to respond to the different error scenarios appropriately
  • Work on tests for export

Blockers or Asks:

  • None

Conor

Yesterday:

Today:

  • Moving forward with HTTPS v2 cert request for long-standing canary instance (CSR)

Blockers or Asks:

  • None

Erik

Yesterday:

  • Docs & support work
  • Completed nyworld test site buildout and ran first Source UI user test (just 1 participant for now for early testing)

Today:

  • Redmine 4 testing
  • Address comments on transfer/export docs PR

Blockers or Asks:

None

Jen

Yesterday:

  • 1.0.0 support

Today:

  • Big block of meetings, but otherwise am doing some testing of rc2 on Tails 4 in prod VMs
  • I'm on PTO tomorrow

Blockers or Asks:

  • None

John

Yesterday:

  • 1.0.0 support (I like that!)

Today:

  • More of the same; running through QA now that debs are right

Blockers or Asks:

  • None

Kev

Yesterday:

  • PR for tailsconfig bugfix
  • Discovered RC1 build issue (changes didn't make it in)

Today:

  • docs review on Ro's PR
  • v3 Onion docs
  • QA

Blockers or Asks:

-None?

Kushal

Today:

  • RC2 related steps
  • Had to kick a few random failed tests
  • debugging his hardware installation, no network it seems.

Tomorrow:

  • If hardware fails, then continue QA on VM

Blockers or Asks:

  • Difficulty reaching mon or app from Tails, may need some help w/ debugging

Mickael

Yesterday:

  • RM tasks
  • Non-sd tasks

Today:

  • rc2 QA
  • Review export device recommendations PR

Blockers or Asks:

  • None

Nina

Yesterday:

  • Getting UserFeel (remote testing tool) setup for our first test, WOOO!!!

Today:

  • Epic UX meeting; notes, forthcoming!
  • Debrief w/ Erik (que?) wrt updates & next-steps w/ UserFeel
  • Draft updated questions/tasks/scenario for UF next steps

Blockers or Asks:

  • Usual from Erik :D
  • ¡COMPLIMENTS! <— ...intentionally cryptic leaving-it-there, nothing to "read into" and everything to giggle at
  • Planning to be OOTO tomorrow (Friday) and Monday PM, wrt limited hours allocation

Ro

0.5 day PTO

Clone this wiki locally