New tool for opening upstream tasks

[Chuck Frain]

Out of curiosity (I've not found an answer yet), what is the best way to
tell if a bug is an upstream issue vs an Ubuntu specific issue? If there is
a page out there that explains it please feel free to point me in the
appropriate direction.

Thanks!

Chuck

On Wed, Feb 18, 2009 at 3:51 PM, Jorge O. Castro <jorge at ubuntu.com> wrote:

> At UDS I went over the upstream report[1] and pointed out how we do a
> good job of linking Ubuntu bugs to upstream bugs when we know it's an
> upstream bug but we generally don't do a decent job of marking bugs as
> affecting upstream in the first place. After the session I asked
> around and asked why people weren't linking bugs. The overwhelming
> response was that it was an extra step in the process and that it took
> so long, so unless it was a serious bug they didn't bother. So now
> that LP has an API for manipulating bugs I asked Graham Binns to make
> a script that will make "bulk opening of upstream tasks" possible. The
> script is called upstream-packagebugs[2]. Here's an example:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20090219/26ac463b/attachment.htm