Package Lifecycle: Offboarding

Use this checklist for package deprecation and downward/high-impact track changes (for example, Integrated to Maintained or Maintained to Community).

If a package is re-promoted later, use the Package Lifecycle Integration Checklist.

1. Open or update BBTOC issue: include current track, requested track, direction, impact summary, proposed timeline, and release-notes notice.
2. Set BBTOC status to in process and keep status updates limited to in process, accepted, or rejected.
3. Route through governance path: complete Value Stream review and Jedi review; escalate to Big Rocks when criteria in the BBTOC process are met.
4. Create communication plan: include audiences, channels, timing, owners, and release-note language before execution.
5. Complete Cyber checkpoint: record outcome and any required follow-up actions in linked artifacts.
6. Update ADR and BBTOC links: record communication plan and Cyber outcome in amendment/update records.
7. Execute offboarding implementation: update package track badges, chart references, repository location/CODEOWNERS, and package docs.
8. Publish notifications: send required track-change notifications on schedule until the transition is complete.
9. Finalize BBTOC status: set accepted once required approvals are complete and execution is cleared; set rejected with explicit next steps if the request is not approved.

Required References