Major release process:
Beta Release: All major features are complete. 2-3 weeks
Beta release on demo site
Beta release is announced
First draft of documentation is done
First round of testing is done
Institutions have a chance to report bugs or ask for a PR to be considered for inclusion in release
Release Candidate: Feature Freeze and bug fixes only. 2-3 weeks (may be unrealistic time frame?)
RC goes to demo site
RC is announced
Finalize feature documentation by end of phase
Finalize testing document by end of phase
Distributed Testing all features and report bugs (includes accessibility testing)
Confirm bugs (PO?) and determine priority and fix bugs (need to establish process for this)
Repeat above with additional versions of RCx until release is confirmed stable.
Final Release:
Once Final Release is ready, at least 1 in-production institutions should upgrade before wide release (This may not be doable, but would be good if there are institutions willing to do this, could rotate and plan ahead to help curb)
Final Release is announced widely
Minor release process:
Follows the Major release process on a much more compressed timeline.
Upgrade demo site, retaining data. In the occasion that data needs to be wiped for whatever reason, this is fine. Mostly we want to test that data and users migrate smoothly.
Hyrax Shared Testing Tools:
Demo site:
Hyrax feature guide and testing interactions:
- <URLs to be added>
Hyrax test tracking document:
- Chrome on Windows
- Chrome on Mac OS X
- Chrome on Android (for public interactions) (most popular android versions)
- Safari on iPhone (for public interactions)
- Firefox and Safari should be added (for public interactions?)
This page has moved to the Samvera github pages here.