$customHeader
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

When a new release is being cut, the BTR WG will notify the DEPR working group about the new release. We will then follow this process to ensure that release notes around deprecations are added to the release notes.

Release Notes Process

  1. When a new release has been cut, the BTR WG will notify the DEPR WG.

  2. An agenda item to go through this process will be added to the agenda for the next DEPR meeting.

  3. Review each ticket that is in the ‘Removed’ column on the DEPR board as a group.

  4. If we feel the ticket needs release notes OR the ticket has the needs release notes label attached to it, ensure that release notes are written for that ticket.

  5. Archive the ticket in preparation for the next release.

  • No labels
$customFooter