Skip to content

Triage the open issue backlog #4876

Open
Open
Triage the open issue backlog#4876
Assignees
cliffhall
Labels
choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changev2
Milestone
v2.1.0

Description

@cliffhall
cliffhall
opened on Sep 27, 2026

Part of the triage tracker #4875. Blocked by #4857 (2026-07-28 Spec Refactor) and #4858 (agentic software factory). The shared conventions (close labels, close notes, throttling) are in #4875.

Goal

Triage every open issue: about 258 as of 2026-09-26. Each one ends up either kept (labelled, put on the board, milestoned) or closed with a labelled note. Modeled on inspector#1872.

Buckets

Classify every issue. Cheap heuristics first, then hand-check the rest.

  1. Server submissions, README listing requests and other spam: close as out of scope and point to the MCP Registry.
  2. Archived servers (github, gitlab, gdrive, puppeteer, slack, sqlite, brave-search, …): close and point to servers-archived.
  3. Fixed or made obsolete by the refactor (Tracker: 2026-07-28 Spec Refactor #4857): for example SDK v1 import errors, initialize/session behavior, Roots-dependent access, or SSE transport quirks. Close with the refactor close note, and invite a fresh issue if the problem still reproduces on the new release.
  4. Legitimate bugs that still reproduce after the refactor: keep. Label v2 and server-*, put on the board in Todo, and set a milestone.
  5. Reasonable feature requests in scope under the contribution guidelines (demonstrating MCP features, usability): keep and put on the board. Otherwise close as out of scope, and say why.
  6. Security reports: never close as declined. If a report was filed publicly and should be handled privately, move it to Security Advisories. Proposals that would weaken a control (e.g. widening filesystem or git path access, or turning off validation) may get the security-declined label, using the Inspector's three-condition test adapted to these servers.

Tasks

  • Take a full snapshot of open issues (gh issue list --state open --limit 1000 --json …) and record the counts per bucket in a comment here before closing anything.
  • Create the shared close labels, if the PR pass hasn't already.
  • Finalize the close notes, one per bucket, adapted from inspector#1872's notes A and B. Each one references Tracker: Triage the open issue and PR backlog #4875 in the original comment.
  • Hand-review everything that falls in buckets 4–6 before closing anything in bulk.
  • Run the scripted, throttled closes for buckets 1–3.
  • Put every kept issue on the Servers V2 board with a Status of Incoming, label v2, and no milestone.
  • Post a final summary here: counts closed per label, counts kept per server, and anything that became new work.

Acceptance criteria

Activity

  1. cliffhall
    added this to the v2.0.0 milestone on Sep 27, 2026
  2. cliffhall
    self-assigned this
    on Sep 27, 2026
  3. cliffhall
    added
    v2
    on Sep 27, 2026
  4. cliffhall
    added a parent issue on Sep 27, 2026
  5. cliffhall
    marked this as blocked by 2 issues on Sep 27, 2026
  6. cliffhall
    modified the milestones: v1.0.0, v2.0.0, v2.1.0 on Oct 8, 2026

  7. cliffhall commented on Oct 19, 2026

    @cliffhall
    cliffhall
    on Oct 19, 2026
    MemberAuthor

    Snapshot and bucket counts (2026-10-19)

    Snapshot taken at origin/v2/main f18beb7, the day v2.0.0 shipped: 215 open issues, of which 15 were already on the board (left as they are) and 200 unboarded, classified below. Each was read and checked against the current code by static analysis; nothing was run against any server an issue pointed at.

    Bucket Count Action
    1. Listings, submissions, issues not about these servers 12 Close, closed-out-of-scope
    2. Archived servers 2 Close, closed-archived-server
    3. Fixed or made obsolete by the refactor (incl. 15 already available in v2) 87 Close, closed-superseded-v2
    3a. Duplicates of open issues 4 Close as duplicate, duplicate
    3b. Belongs to an SDK or the spec/docs 3 Close, closed-out-of-scope
    4. Bugs that may still reproduce 22 Keep → board Incoming; static verification next
    5. In-scope feature requests 37 Keep → board Incoming
    5. Out-of-scope feature requests 23 Close, closed-out-of-scope (2 also closed-security-declined)
    6. Security reports 10 Keep, handed to maintainers; never closed by this pass

    Close labels created for both sub-issues: closed-superseded-v2, closed-archived-server, closed-out-of-scope, closed-security-declined (the last only alongside another).

    Kept issues go onto the board in Incoming with no milestone, with a Priority and a posted score; pass 2 (milestoning) stays with a maintainer.

    Issues per close class
  8. cliffhall
    added
    choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior change
    on Oct 19, 2026

  9. cliffhall commented on Oct 19, 2026

    @cliffhall
    cliffhall
    on Oct 19, 2026
    MemberAuthor

    Final summary

    All 200 unboarded open issues from the snapshot are now either closed with a close label and a note referencing #4875, or labelled v2 + one type + scope and on the Servers V2 board in Incoming with a Priority and a posted score comment, and no milestone (pass 2 is a maintainer's). The board audit prints 0 on every check.

    Closed: 134

    Label Count
    closed-archived-server 2
    closed-out-of-scope 38
    closed-superseded-v2 89
    duplicate 5

    closed-security-declined was added alongside closed-out-of-scope on 2 proposals that would have weakened a control (#508, #3457).

    Bucket 4 was verified before anything was kept or closed: each candidate bug was checked against v2/main by static reading, and by a local reproduction against local fixtures where that was cheap (#470, #3878, #4199, #4914, #5129, #5134). No server or URL named in any issue was contacted. Three turned out fixed and are among the closes: #692 and #2113 (superseded), #3508 (a duplicate of the fixed #3527).

    Kept: 67, all Incoming

    Scope Count
    repo-wide 12
    server-everything 9
    server-fetch 10
    server-filesystem 21
    server-git 5
    server-memory 4
    server-sequentialthinking 3
    server-time 3

    Priorities: 2 High, 16 Medium, 49 Low. Of these, 19 are verified or unconfirmed bugs, 37 are in-scope enhancements/docs/chores, 10 are security reports handed to the maintainers (their score comments carry bands only), and 1 is new work.

    New work

    The three trackers (#4875–#4877) also received the chore type label they were missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changev2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions