Changing status to "New" after providing information

Timothy Mayoh timothy.mayoh at gmail.com
Thu Oct 27 10:12:00 UTC 2011


Brad Figg's script usually requests that the user changes the status to
"Confirmed" for kernel bugs; I believe that would be a better approach for
the majority of bugs than requesting it be changed to "New", as it shows the
bug likely already has the required logs, whereas many "New" bugs don't have
them.

For example:

>This bug is missing log files that will aid in diagnosing the problem. From
a terminal window please run:

>apport-collect BUGNUMBER

>and then change the status of the bug to 'Confirmed'.

>If, due to the nature of the issue you have encountered, you are unable to
run this command, please add a comment stating that fact and change the bug
status to 'Confirmed'.

>This change has been made by an automated script, maintained by the Ubuntu
Kernel Team.


On 27 October 2011 04:51, Walter Garcia-Fontes <walter.garcia at upf.edu>wrote:

> I think it could be a good idea to ask bug reporters to change the
> status to "new" again if they provide the information requested by a
> triager. For instance something like:
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please execute the following command, as it will
> automatically gather debugging information, in a terminal:
> apport-collect BUGNUMBER
> Please change the status of the bug to "New" when you finish doing
> this. When reporting bugs in the future please use apport by using
> 'ubuntu-bug' and the name of the package affected. You can learn more
> about this functionality at https://wiki.ubuntu.com/ReportingBugs.
>
> Same thing for other standard responses asking for more information.
>
> --
> Walter Garcia-Fontes
>
>
>
> --
> Ubuntu-bugsquad mailing list
> Ubuntu-bugsquad at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20111027/e7a86e6a/attachment.html>


More information about the Ubuntu-bugsquad mailing list