Or "forecast"


Sprint 38 retrospective

  • what went well
    • Upcoming release is a good thing
    • Getting back into thoughts of continuous integration and e2e testing
    • Found bugs
    • Excitement around the release – we should do more releases. The promise of CD is if you do it often enough, it's less scary.
    • We have traction with MDF group
    • Doing better on review
  • what didn't go well
    • break, hard to get back
    • Charles tried to dial in, but we didn't dial him in
    • Constant maintenance – on Nebula, TACC, etc.
      • Jetstream down for 1 week
    • Release keeps getting pushed back, which is bad
    • Overcommitted or poorly predicted.
    • Cybertraining proposal distraction – we haven't learned how to factor in this noise
    • Losing Kandace – we need to absorb more distractions
  • what should we continue or not continue
    • Continue to improve release and testing processes
    • Think more about security
    • Plan to show what we've done
    • If we were better at sprint planning, we'd know how distractions impact velocity
      • How do we find our velocity?
      • We need to estimate every story and use JIRA
      • We should start doing estimates if we want to know velocity
    • We're not terribly serious about closing stories
    • Move to points, not hours


Release discussion

  • Meaningful release means installation on beta, ETK, or TERRA
  • Build rc, test
    • unit tests (some day)
    • postman (exercise API endpoints)
    • e2e UI tests
    • It's as good as 1.0, lets push it
  • With real CI, there's no RC

GlobusWorld:

  • MDF Forge logged in with Globus Auth no pasting token
  • Download data to personal endpoint running in Workbench
  • Workbench running near the storage condo with real Globus endpoint
  • Workbench link hidden in GP entry

NDS-1117 (use go client, use 5.0 go client)


Integration testing:

  • Process for building coverage binary/image
  • Server clean exit (handling interrupt signal) with shutdown endpoint
  • 100% endpoint coverage
  • Postman json for specific test cases
    • Register
    • Login
    • ...
  • Run via Postman UI
  • Documenting test process


Sprint 39 priorities:

  • Get e2e tests passing on refactored UI (1.1)
  • Get baseline integration tests with postman
  • Supercool stuff for GlobusWorld
    • Meeting with JD and maybe Kyle
  • Deploy on beta
  • No labels