When to report upstream?

[Alberto Salvia Novella]

So what will you do, lets say for example, in this bug 
<https://bugs.launchpad.net/compiz/+bug/1182742>?


El 26/10/13 16:58, Dr. David Alan Gilbert escribió:
> * Alberto Salvia Novella (es20490446e at gmail.com) wrote:
>> How can you know a bug has to be reported upstream too? since I feel
>> like missing some cases.
> To report upstream you'd generally have to make sure it happens on
> the upstream version of the code rather than the Ubuntu packaged version.
>
> So it's not necessarily easy; for kernel's there is an ubuntu
> upstream nightly kernel build that makes it easy to try the upstream.
>
> For KDE generally I normally go the other way, i.e. report to KDEs bug
> tracker unless the problem feels like an ubuntu packaging issue.
>
> For everything else it's normally a case of having to download the code
> and try.
>
> Then there is the question of what you mean by 'upstream' - so debian
> or the original package source; i.e. did the problem occur in debian
> or ubuntu's patches; are either of those just way old and the upstream
> version is much newer? Upstream will generally get annoyed
> if you complain about ancient versions of their code, however if they
> keep an old version in a maintanence mode they might still want to know.
>
> Dave
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20131026/91d9c4c9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2260 bytes
Desc: Firma criptogr??fica S/MIME
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20131026/91d9c4c9/attachment.bin>