Skip to content

docs(runbooks): clarify deprecation review signals #442

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ss-o merged 1 commit into from
Jun 12, 2026
Merged

docs(runbooks): clarify deprecation review signals #442

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions runbooks/deprecation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,16 +14,26 @@ Use this when an artifact is no longer maintained or has been superseded:
- a package no longer published
- a repo that should become read-only

Quiet repositories are not abandoned by default. Low issue volume, few commits,
or a stable done state are signals to review maintainer intent, consumer usage,
and replacement availability; they are not enough on their own to deprecate or
archive a project.

Do not use this for routine workflow-hygiene cleanup (removing a stale CI
workflow) — that is ordinary maintenance, kept separate from release semantics.

## Step 1 — Decide and record

1. Confirm the artifact's class (ADR-0007) and what consumes it.
2. File a tracker issue describing the deprecation, the replacement (if any), and
1. Confirm the artifact's class (ADR-0007), what consumes it, and whether it is
intentionally stable, actively replaced, or genuinely unmaintained. Use issue
activity as context, not as the decision.
2. Identify maintainer intent and replacement availability. If maintainers intend
the project to remain stable, record that state instead of starting the
sunset process.
3. File a tracker issue describing the deprecation, the replacement (if any), and
the migration path. If the decision is non-obvious or cross-repo, draft an ADR
(`runbooks/adr.md`).
3. Identify every install path: `zi` ice, meta-plugin labels
4. Identify every install path: `zi` ice, meta-plugin labels
(`z-a-meta-plugins`), wiki references, and the catalog `workspace/repos.yml`.

## Step 2 — Announce
Expand Down
Loading