ubuntu-bugcontrol team mailing list archive

[Brett Cornwall <brettcornwall@xxxxxxxxx>]

 1) https://bugs.launchpad.net/compiz/+bug/579688

I would set this as 'low' because of the trivial impact on users. It does
not affect the program's functionality or stability in any way.

 This bug right there, its not being tracked right because the only
remaining task in this bug report is of Compiz <launchpad.net/compiz>
since its a Ubunut bug the right thing would be to have the bug opened
for package in ubuntu. Also now we use <launchpad.net/compiz-core> as
upstream for compiz.


 My apologies, I had neglected to change the status of that.

I have changed to bug report to affect compiz (ubuntu)

 2) https://bugs.launchpad.net/banshee/+bug/738862

I would set this to 'low' -- same reasons as the above.

 Nice work there sending the bug upstream. Its better to use stock
responses <https://wiki.ubuntu.com/Bugs/Responses>
<https://wiki.ubuntu.com/Bugs/Responses> mostly when
replying to a bug report.

In this case "Thank you for your bug report. This bug has been
reported to the developers of the software. You can track it and make
comments at: https://bugzilla.gnome.org/show_bug.cgi?id=648951"; would
have been the right response.

 Again, apologies. I have only recently discovered the pool of stock
responses and have also recently discovered the LP enhancer PPA, a package
I will use the most out of.

Here's an old bug that I also linked upstream in which I recently used a
stock response.

And to counter the lack of stock responses, I present to you a slew of old
bugs that I have been pooling over for compiz. All are for incompleting
bugs because I've been having to ask for info on 98 percent of them:
(1<https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/731413>,
2 <https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/722449>,
3<https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/711679>,
4 <https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/694010>,
5<https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/684871>,
6 <https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/683039>,
7<https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/682364>,
8 <https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/682356>,
9<https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/617093>
)

  3) https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/923823

I would actually have set this to 'wishlist' as it's a feature enhancement
request. Since it was reported upstream and properly documented it was ready
for developer response.

 Agreed that's a whislist but again stock responses please.


Again, apologies. Could I do it again, I would have inserted:

 Thank you for your bug report. This bug has been reported to the
developers of the software. You can track it and make comments at:<insert
bug number>

  4) https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/297234

I would set this to 'medium' because of the non-frequency of such a setup
does not warrant a 'high' value. It warrants a 'medium' rather than a 'low'
because Compiz is a core Ubuntu application.

 Its a 3 years old untouched bug, much have changed since then in
compiz. you could have chose a better example bug :-)

 I had requested information and OP delivered updated logs with
confirmation that the bug still exists just yesterday. As per the Responses
Wiki I set the value to 'New' but I felt that it had enough information to
be triaged.

  5) https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/768800

This is 'wishlist' material because this is a non-trivial extension of
functionality not in the design scope. I confirmed the bug with my own
tablet.

 Not really sure whats this bug report is about.

 I have updated the report with more accurate details and a video
demonstrating the effect.


If these still are too weak of examples and replies then I will happily
wait a little bit more and return a brand-new application a little later
for you. Thanks!