...
Section 2: Important Upgrade Considerations > Changes and Required Actions
- This section outlines all changes that require special consideration for customers in production. Configuration changes may be needed to prevent operational interruptions. See checklist for guidelines on how to fill this out.
- PO and/or Dev lead must complete this section and should include any critical changes and or required migration/upgrade actions for hosting providers.
Section 3: Important Upgrade Considerations > New apps
...
- Post details regarding new/deprecated permissions
Section 6: Known issue
- Add any known issue that will not be addressed for the release
- You can add to table OR apply a JIRA label for the issue to show in JIRA list.
- JIRA label > known-issue-<<release name>>
Section 7: Notes on functionality tbaletable
- A table that describes functionality that might not be included in ppt (see Section 1)?
Section 8: Post-Release Hotfixes
- JIRA filters of CSP issues. Handled by Oleksii.
Section 9: New Features
- JIRA filters of New features. Handled by Oleksii.
Section 10: New Features by Epic (Sub-Project)
- JIRA filter created by Oleksii
Section 11: Closed Bugs
- JIRA filter created by Oleksii
Section 12: All Closed Bugs and Stories
- JIRA filter created by Oleksii
Section 13: Remaining Open Bugs at Time of Release
- JIRA filter created by Oleksii
POs should
- Update release notes once a feature and/or issue is set to PO Review.
- Ask SM to coordinate time for devs to add release notes throughout the release
- If no SM, PO should remind devs to add release notes throughout the release
- Add a label to track known issues for a release
- Add a label for features/issues that require a release note
- Beware of any updates/migrations that may result in significant service disruption or results in significant changes to data (i.e. MARC - FOLIO mapping rules changes)
- Please remember to update release notes if required for a Critical service patch (CSP)
...