Snapcraft has three unsynced bug lists
Metadata
Current evaluation
Snapcraft bug reports were split across Launchpad and GitHub, causing duplicates and unclear prioritization. No activity for ~9 years. The referenced #100 signpost is now closed and the repo uses GitHub issue templates, so tracking has consolidated on GitHub.
Suggested action: close stale
Reason: The issue is 3260 days old with 0 comments and no maintainer interaction, and its core problem is no longer applicable: the #100 'Issues are tracked on launchpad' signpost it cites is now closed, and the repo ships .github/ISSUE_TEMPLATE files, showing the project adopted the issue's proposed GitHub-exclusive upstream tracking. Closing as resolved-by-project-evolution rather than leaving a 9-year-old process debate open.
Impact:
20
Quick Win:
13.0
Staleness:
95
Complexity:
35
Confidence:
70
Support Request:
10
Issue body
Snapcraft has at least three unsynced bug lists:
<https://bugs.launchpad.net/snapcraft> (currently 425 open bugs)
<https://bugs.launchpad.net/ubuntu/+source/snapcraft> (currently 53)
<https://github.com/snapcore/snapcraft/issues> (currently 31).
This introduces all the usual problems of multiple to-do lists:
* It’s harder to tell whether an issue has been reported already, so duplicates are more likely.
* It’s harder to to tell which are the most important things to work on.
* Someone fixing one bug is less likely to notice when another bug would be best fixed at the same time.
Since Snapcraft is a cross-distro tool, it may be necessary to keep at least separate upstream and downstream bug lists. But it may be possible to avoid having two upstream bug lists.
Using GitHub for issue tracking is optional. "Issues are tracked on launchpad" <https://github.com/snapcore/snapcraft/issues/100> is a signpost that points people to Launchpad, but it doesn’t explain why GitHub Issues are open for Snapcraft at all. <https://github.com/snapcore/snapcraft/issues/1506#issuecomment-330279314> gives a little more explanation: “We only use github issues here in order to use Projects”. So, one solution would be to find an alternative to using GitHub Projects.
Another approach would be to use GitHub exclusively for upstream issue tracking.
Things that would lessen the problem:
* Mention Launchpad for bug reporting more prominently in the README
* Migrate and close all the GitHub issues except for the #100 signpost.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
13.0
Staleness:
95
Complexity:
35
Confidence:
70
Support Request:
10
|
close stale | Snapcraft bug reports were split across Launchpad and GitHub, causing duplicates and unclear prioritization. No activity for ~9 years. The referenced #100 signpost is now closed and the repo uses GitHub issue templates, so tracking has consolidated on GitHub. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
30
Confidence:
90
Support Request:
0
|
close stale | Highlights unsynced bug tracking across Launchpad and GitHub, suggesting consolidation. No maintainer response in over 8 years; project tracking has likely consolidated to GitHub. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
20
|
close stale | Issue proposes consolidating Snapcraft's fragmented bug tracking across Launchpad and GitHub to reduce duplicates and improve prioritization. No maintainer response or activity in over 8 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
10
Confidence:
90
Support Request:
0
|
close stale | Suggests consolidating Snapcraft's three unsynced bug trackers to GitHub or improving signposting. The report is over 8 years old, has zero comments, and shows no maintainer engagement. | |
| qwen3.6-35b-moe-q4 |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
10
|
close stale | Reports unsynced bug tracking across Launchpad and GitHub. Untriaged, zero comments, and dormant for over 8 years. Likely obsolete given project evolution. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#100
(confidence 75%)
The 'Issues are tracked on launchpad' signpost cited in this issue is now closed, indicating the project moved off the dual Launchpad/GitHub tracking arrangement described here.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2104274 Snapcraft has unclear behavior when providing same build-snap from different channels | snapcraft (launchpad) | open | Bug report: snapcraft resolves build-snap from wrong channel (stable vs candidate). Untriaged, no maintainer response in 527 days. | |
| #5086 snapcraft status lists several time the same information | snapcraft | open | snapcraft status prints the same track/arch/channel rows multiple times in its table output. Reported against snapcraft 8.4.1 on Ubuntu Oracular; no maintainer response, no labels, no activity since filing ~2 years ago. |