Skip to content

Groom backlog: close resolved and obsolete issues #956

Closed
11 of 11 issues completed
Closed

Description

@tdstein

Destination

Every open issue (excluding the Python EOL effort) has been checked for whether it is already resolved or obsolete. Those issues are closed with an evidence-backed comment. Everything else is untouched and waits for a later grooming pass.

Notes

  • Execution override: this map does its own closing. Each batch's review ticket ends with the approved issues closed. Closing is cheap and reversible.
  • Verdicts (one per issue):
    • Resolved: a later change fixed it. Cite a PR, commit, code reference, or CHANGELOG entry.
    • Obsolete: no longer applies. The feature was removed, a Python or Connect version is unsupported, the workflow was superseded, or it duplicates another issue.
    • Still valid: leave open, untouched. This includes "won't do" product calls (e.g. renaming commands), which a later prioritization pass decides.
    • Unclear: not enough evidence. Leave open.
  • Evidence: researchers read code and git history, and may run the CLI locally (uv run rsconnect …, write-manifest, --help) against temp dirs. They never call a live Connect, shinyapps.io, or Connect Cloud server. Anything that needs a live server is Unclear.
  • Duplicates: keep the issue with the clearer spec or more discussion and close the other with gh issue close --duplicate-of. The researcher proposes and the human decides.
  • Sign-off: nothing is closed on agent judgment alone. The human approves each batch's verdict table first.
  • Closing: comment prefixed with "🤖 ", citing the evidence and inviting a reopen if it still affects the reader. Resolved issues close as completed, obsolete ones as not planned. Close immediately, with no waiting period.
  • Ticket pattern per batch: a research ticket (AFK) writes a verdict table to a research/<name> branch, then a review-and-close task (HITL), blocked by it, applies the approved verdicts.
  • shinyapps.io is being decommissioned, so open issues specific to shinyapps.io are obsolete. Close them as not planned and link the migration guide. Connect Cloud deploys are still supported, so issues about them are not obsolete by default.

Decisions so far

Not yet specified

Out of scope

  • Verifying Unclear verdicts against a live server, Windows, or the reporter: even a confirmed repro only makes an issue "still valid". The evidence for the later triage pass is in the batch verdict tables. See Verify or defer the Unclear verdicts?.
  • Removing shinyapps.io support from the CLI (deploy target, help text, tests): a code change for a separate effort, not grooming.
  • Python EOL effort (Drop support for EOL Python #942–Modernize syntax for Python 3.11 (ruff UP) #951): freshly specified and actively planned, so it has nothing to groom.
  • Prioritization, wontfix, needs-info, and triage labelling of still-valid issues: these are product decisions for a later grooming pass, not "already resolved or no longer an issue".

Metadata

Metadata

Assignees

Labels

wayfinder:mapWayfinder map (index of a planning effort)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions