What does stable look like?
- Media reliably transcodes
- Elements on the page don’t jump around and get out of place
- What was once working, stays working
- Builds succeed reliably
- System installs and continues to work on servers and individual machines
Feature Freeze Process:
- When the above criteria are met, a feature freeze will be in place to provide stable testing.
- Testing script will be provided with specific end-user tests
- Only prioritized and agreed on bugs (POs will approve fixes) will be fixed and related code pushed to the release branch.
- Any code changes that violate the feature freeze must be approved by Release Manager and POs and thoroughly tested.
Code Freeze Process:
- Release code to Master branch
- Master branch is frozen until next release
- Any code changes after this point must be approved by the Release Manager and thoroughly tested with the same script used during the feature freeze before being implemented. Process for merging code TBD by Release Manager.
- Installs cleanly at IU/NU on pilot/production systems
- Generic version of code available on Github (not one customized for IU/NU)
- It doesn’t break a lot
- It doesn’t look broken
- Document our benchmarking numbers for transcoding - with the system stats we’ve used
- Essential use cases work well
- Final documentation is complete and organized on the wiki (Collection Managers Guide, Sys Admin, Install)
- Process for partner support in place
Code change plan - release branching
See: Branching and Tagging Releases