Closes #5255: Update release notes structure

[danahertzberg]

Description

Updates release formatting to use a table.

Changes to Release Types section include:

• LTS patch release note moved to Patch releases section
• Minor releases has a description
• Major releases has a description
• New "What's Included in each Type of Release?" section with table format
  • * and ** notes below the table
• "Bugfix" changed to "Bug-fix"

Release notes

Related issues

Closes #5255

How to test

View file: https://github.com/az-digital/az_quickstart/blob/9d5f61fb6fe30a5e0672833b3445f5ae14800e82/RELEASES.md#release-types

1. Verify new formatting on RELEASES.md is accurate and legible

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Patch release changes
  • Security update
  • Patch level release (non-security bug-fix release)
  • Patch removal that's no longer necessary
• Minor release changes
  • Major or minor level update
• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My change requires release notes.