release cycle notes

A  1. ticket review / sanity check
   2. identify lingering design needs
   3. check in on priorities

B  1. show and tell
   2. get clear on testing needs
   3. get clear on Ethan coding objectives
   4. plan for branches / checkpoints (= deploy to pinz?)

C  1. remaining tickets
   2. roll-out details
   3. talk through downtime: sysadmin/infrastructure/spikes/refactoring

D  1. loose ends (name and plan) (5)
   2. review cycle (10)
   3. next release planning (15)
   4. group gathering plans   chicago option july 25-aug1