<div dir="ltr">Hello,<div><div class="gmail_extra"><br><br><div class="gmail_quote">On 26 November 2013 08:58, Sergio Schvezov <span dir="ltr"><<a href="mailto:sergio.schvezov@canonical.com" target="_blank">sergio.schvezov@canonical.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>On Tue, Nov 26, 2013 at 5:56 AM, Thomi Richards <span dir="ltr"><<a href="mailto:thomi.richards@canonical.com" target="_blank">thomi.richards@canonical.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">On Tue, Nov 26, 2013 at 2:44 PM, Ursula Junque <span dir="ltr"><<a href="mailto:ursinha@ursinha.net" target="_blank">ursinha@ursinha.net</a>></span> wrote:<br>
</div><div class="gmail_extra"><div><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><br></div><div><div>If upstreams don't oppose to that, bugs should only be filed against Ubuntu packages, discouraging the direct upstream reporting. </div>
</div></div></blockquote></div><div><br></div></div><div>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). </div>
<div><br></div><div>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).</div>
</div></div></blockquote><div><br></div><div><br></div></div><div>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.</div>
<div><br></div><div>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.</div>
</div></div></div></blockquote><div><br></div></div><div>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);<br>
<br>This is a problem since ubuntu-bug won't find the package and fail. Any solution to this is welcome.</div></div></div></div></blockquote><div><br></div><div>For me at least, it seems like there is a simple mechanism to determine where to file a bug:</div>
<div><ol><li>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.<br></li><li>If the bug is found using a package in a PPA, it should be reported against the upstream software. <br>
</li></ol></div></div><div>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. </div>
<div><br></div><div>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. </div><div><br></div><div>Does this make sense? </div><div><br></div>
<div>Cheers,</div><div><br></div>-- <br><div dir="ltr"><pre cols="72">Luke Faraone;; Debian & Ubuntu Developer; Sugar Labs; MIT SIPB
lfaraone on irc.[freenode,oftc].net -- <a href="https://luke.wf/ohhello" target="_blank">https://luke.wf/ohhello</a>
PGP fprint: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506</pre></div>
</div></div></div>