...
- Discussion of new features (if any) on component-specific slack channels
- tier-shib
- tier-grouper
- tier-comanage
- tier-midpoint
- Images are built from the pipeline and made available for testing
- Announcement of new container images on the appropriate slack channel
- The same channels listed in Section 1 above are used.
- The same channels listed in Section 1 above are used.
- Discussion of testing on slack channel
- Minor / no known changes normally require a 3 day minimum discussiodiscussion
- Releases with new features normally require a 7 day minimum discussion; perhaps longer for major version updates as needed.
- Critical security updates may be moved at a more rapid pace, as needed.
- Iteration, as needed, to fix bugs and agree on stability.
- Update the TIER Package Delivery (TPD) Web Site
- The TPD site is updated with a reference to the new production container image.
- A reference to the past version or two is maintained.
- An email message is sent to watchers of the TPD site (is this sufficient or do we need a separate or other existing list for this function?