Reporting Bugs

[Brian Murray]

On Tue, Jul 02, 2013 at 11:28:39AM -0400, Joseph Salisbury wrote:
> Can someone further analyze this paragraph.
> 
> "For bugs in the Linux (Ubuntu)
> <https://launchpad.net/ubuntu/+source/linux> package,
> unless the upstream maintainer or kernel developer notes otherwise, if a
> new mainline kernel comes out, and you haven't tested with it, your report
> is considered Status Incomplete <https://wiki.ubuntu.com/Bugs/Status>
> whether
> or not someone toggled the Status of your report. "
> 
> Source: https://help.ubuntu.com/community/ReportingBugs
> 
> 
> Hi Istimsak,
> 
> When a new mainline kernel comes out, we usually ask to have it tested. 
> The primary purpose of this is to see if the bug has already been fixed
> upstream.  If it has been fixed upstream, we check to see if it was also
> sent for inclusion in the upstream stable trees.  If it wasn't sent to
> upstream stable, we then figure what exact commit fixed the bug, then
> cherry pick it into the Ubuntu stable kernels.
> 
> A bug is also set to Incomplete when the apport logs are not included in
> the report.
> 
> I'm not sure if this is the information you were looking for.  If not,
> just let me know and I can provide some additional details.

I also think part of the original statement "your report is considered
Status Incomplete ... whether or not someone toggled the status of your
report", is trying to address the fact that Launchpad automatically
confirms bugs if a bug is made a duplicate of another or if someone
clicks "affects me too".  Is that right Joe?

--
Brian Murray