Ubuntu system image has two unsynced bug lists
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu system image |
Won't Fix
|
Undecided
|
Unassigned | ||
| system-image (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
system-image has two unsynced bug lists.
<https:/
<https:/
This needlessly risks quality: some bugs are only in one list, some people will know about only the other list, and even when a bug is in both lists they can have different importance levels, making it harder to tell what to work on next.
For these reasons, since 2013 Ubuntu Touch policy has been to track bugs on packages, not projects.
<https:/
To fix this:
1. Go through each bug reported on the project, and move it to the package.
2. At <https:/
| Barry Warsaw (barry) wrote | #1 |
| Changed in system-image (Ubuntu): | |
| status: | New → Won't Fix |
| tags: | added: client |
| Changed in ubuntu-system-image: | |
| status: | New → Won't Fix |
It's more complicated than that. For historical reasons, the project also tracks bugs in the server and other related pieces. There is a tag on the project 'client' that tracks bugs specifically in the client. The client *is* a separate project; it has a separate upstream release and a separate packaging branch.
The guidelines I've been using are:
* Report bugs on the project. If they are in the client component, tag them with 'client'
* Problems specifically related to the way system-image client is packaged in Ubuntu are reported on the package
I do not mind if the bugs are initially reported on the package. Whenever I get time or have the need to work on the project, I regularly cull the packaging bugs and transfer/tag them over to the project.