What does stable look like?

Feature Freeze Process:  

Code Freeze Process:

Release criteria

  1. Installs cleanly at IU/NU on pilot/production systems
  2. Generic version of code available on Github (not one customized for IU/NU)
  3. It doesn’t break a lot
  4. It doesn’t look broken
  5. Document our benchmarking numbers for transcoding - with the system stats we’ve used
  6. Essential use cases work well
  7. Final documentation is complete and organized on the wiki (Collection Managers Guide, Sys Admin, Install)
  8. Process for partner support in place

Code change plan - release branching
See:  Branching and Tagging Releases