-
Notifications
You must be signed in to change notification settings - Fork 695
[Initiative]: Release Notes Best Practices #2026
Copy link
Copy link
Open
Labels
kind/initiativeAn initiative or an item related to imitative processesAn initiative or an item related to imitative processesneeds-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)needs-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)
Description
Metadata
Metadata
Assignees
Labels
kind/initiativeAn initiative or an item related to imitative processesAn initiative or an item related to imitative processesneeds-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)Indicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)needs-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)Indicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)
Type
Projects
Status
New
Status
status/new
Status
No status
Status
No status
Status
No status
Name
Release Notes Best Practices
Short description
Release Notes Best Practices
Responsible group
TAG Operational Resilience
Does the initiative belong to a subproject?
Yes
Subproject name
No response
Primary contact
N/A
Additional contacts
n/a
Initiative description
What are the best practices for Release Notes?
Adopters review release notes in order to determine whether to move to a new release. If the release notes do not give thorough information, adopters are unable to make an informed decision to move to a new release.
Deliverable(s) or exit criteria
Document describing the best practices for a release document.
Tracking document for meeting and progress
n/a