Skip to content

Pre-0.17.0 backlog triage campaign #2717

Description

@chalin

We're running a triage pass over the full open backlog: ~300 issues and PRs, some dating back to 2019. This issue is the campaign's home: closes made as part of it link back here, so this issue's timeline indexes everything the campaign touches.

What we're doing. Each open item was reviewed with its full thread. Items are being closed as not planned when they are:

  • Already resolved by the current theme or docs (evidence in the close comment);
  • Stale support questions answered years ago with no follow-up;
  • Superseded by newer issues, PRs, or shipped work (credited in the close comment);
  • Feature additions with low community demand that the maintainer team has no capacity to adopt and maintain.

What a close here means. A close is a statement of maintainer capacity and current direction, not a verdict on the idea's merit. If a closed item matters to you:

  • 👍 the issue and say so: community demand is an explicit input to what we reconsider;
  • Comment with new information (for example, a repro on a current release), and we'll reassess.

Conflicting PRs. Most open PRs predate the 2026 monorepo restructure and no longer apply. Where the underlying proposal still has value, the close comment says so; a rebased resubmission against the current layout is welcome, and we'll reopen or link the successor.

Questions about the campaign itself? Comment here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions