[Ubuntu-phone] Policy: filing bugs against Ubuntu packages instead of upstream projects

Luke Faraone lfaraone at ubuntu.com
Tue Nov 26 23:01:03 UTC 2013


On 26 November 2013 08:58, Sergio Schvezov <sergio.schvezov at canonical.com>wrote:

> On Tue, Nov 26, 2013 at 5:56 AM, Thomi Richards <
>> thomi.richards at canonical.com> wrote:
>>> On Tue, Nov 26, 2013 at 2:44 PM, Ursula Junque <ursinha at ursinha.net>wrote:
>>>> If upstreams don't oppose to that, bugs should only be filed against
>>>> Ubuntu packages, discouraging the direct upstream reporting.
>>> I think the distinction between upstream and distro is a useful one, and
>>> I'd be sad if we started treating them as one and the same (or created a
>>> blanket rule about where bugs should be reported, which is effectively the
>>> same thing, in my mind).
>>> I also believe that the correct place for almost all bugs to be filed is
>>> against the upstream projects itself (at least, for the core
>>> Canonical/Ubuntu projects - I assume we're having this conversation in the
>>> context of canonical-sponsored Ubuntu Touch projects).
>> I understand your point, but I'm talking about the policy while
>> dogfooding Ubuntu Touch, and as this is testing the distro it would make
>> more sense to file bugs against the distro packages and use the distro
>> tools, as ogra pointed. As I said, if upstreams see value in having an
>> upstream bugtask that can be discussed, but in this case we need to have at
>> least one bugtask for the source package, always.
>> Sebastian (seb128) pointed that having one list of bugs (the distro ones)
>> helped a lot for the Settings project, they even "closed" the bugs section
>> on the upstream project to ensure bugs would be in a single place (also
>> easier to maintain more accurate bug status/progress). We only need to
>> agree on a policy so it's clear to everyone how it works.
> I'm all for this, although there are places where this isn't really going
> to reflect reality; two components come to my mind here; phablet-tools and
> the sdk itself, which are being offered all the way back to precise on a
> PPA (and the emulator as well soon too);
> This is a problem since ubuntu-bug won't find the package and fail. Any
> solution to this is welcome.

For me at least, it seems like there is a simple mechanism to determine
where to file a bug:

   1. If a bug is found using a package in the Ubuntu repository, be it
   daily images or anything else, it should be reported against that package
   in Ubuntu.
   2. If the bug is found using a package in a PPA, it should be reported
   against the upstream software.

That said, most bugs found and reported via №1 are probably in fact also
bugs of note to upstream. I assume since the projects in question are
Canonical-sponsored they also use Launchpad, in which case marking the bug
as affecting the upstream project is two clicks assuming the project is
associated with the package in Launchpad.

This also lets you mark a bug as fixed in the upstream repo before it is
packaged, and lets you see what the delta is between the two.

Does this make sense?



Luke Faraone;; Debian & Ubuntu Developer; Sugar Labs; MIT SIPB
lfaraone on irc.[freenode,oftc].net -- https://luke.wf/ohhello
PGP fprint: 5189 2A7D 16D0 49BB 046B  DC77 9732 5DD8 F9FD D506
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-quality/attachments/20131126/37b4a0fd/attachment.html>

More information about the Ubuntu-quality mailing list