On Thu, Nov 20, 2014 at 9:14 PM, Alberto Salvia Novella
es204904...@gmail.com wrote:
C de-Avillez:
I will try to stress the above a bit more: users in general will always
assume their bug is high/critical (it is, by definition, affecting their
work!).
We did have it, sort of, on for a while
On Mon, Nov 10, 2014 at 05:11:52PM +0100, Alberto Salvia Novella wrote:
Thomas Ward:
How would a user know what a critical bug is?
Instead of asking to report critical bugs, you can ask if the bug
causes data corruption or renders the system temporally or
permanently unusable, please warn
On Thu, 20 Nov 2014 19:47:00 +0100
Alberto Salvia Novella es204904...@gmail.com wrote:
Brian Murray:
I think this is a false assumption, in that the people setting the bug's
importance to critical know the definition of critical and are able to
independently judge the bug's importance.
On 20/11/14 09:00, Brian Murray wrote:
I think this is a false assumption, in that the people setting the bug's
importance to critical know the definition of critical and are able to
independently judge the bug's importance. Some Launchpad user reporting
or experiencing the bug report is much
C de-Avillez:
I will try to stress the above a bit more: users in general will always
assume their bug is high/critical (it is, by definition, affecting their
work!).
We did have it, sort of, on for a while -- and we found that importance
would have to be controlled. We used to spend a nice
Alberto Salvia Novella:
Perhaps asking users in documentation to mail the Ubuntu Bug Control
team when they find a critical bug would be a good idea.
Added as
https://help.ubuntu.com/community/ReportingBugs#Warn_about_a_critical_bug.
--
Ubuntu-quality mailing list
It is an interesting idea if I am interpreting things correctly.
What I think is being said is:
* If someone writing documentation finds a bug they report it to
bug control
The idea sounds like it could be a positive one, but I too question how
they would know a bug is critical.
Thomas Ward:
How would a user know what a critical bug is?
Instead of asking to report critical bugs, you can ask if the bug
causes data corruption or renders the system temporally or permanently
unusable, please warn about it to the Bug Control team.
Thomas Ward:
why would they need to
On Mon, 10 Nov 2014 09:15:53 -0500
cprofitt cprof...@ubuntu.com wrote:
It is an interesting idea if I am interpreting things correctly.
What I think is being said is:
* If someone writing documentation finds a bug they report it to
bug control
The idea sounds like it
I think we need to really tread carefully here...
On Mon, Nov 10, 2014 at 11:31 AM, Nio Wiklund nio.wikl...@gmail.com wrote:
Den 2014-11-10 17:11, Alberto Salvia Novella skrev:
Thomas Ward:
How would a user know what a critical bug is?
Instead of asking to report critical bugs, you can ask
On Mon, Nov 10, 2014 at 12:44 PM, Alberto Salvia Novella
es204904...@gmail.com wrote:
Brendan Perrine:
If this gets to all users how can we make sure there are not people
that think this bug affects me therefore it is critical which could
make lots of mistakes. Or a user that is like I want
Thomas Ward:
The only way this can work is if people familiar with the package /
issue actively are alerted about the criticality issue. In those
cases, though, they're likely already watching the bugs in the
specific packages. So how does this expedite processing of the bugs?
By making
Perhaps asking users in documentation to mail the Ubuntu Bug Control
team when they find a critical bug would be a good idea. What do you think?
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at:
I... don't see your logic here.
When I read your statement I have a thousand questions show up in my head: How
would a user know what a critical bug is? Better question, why would they need
to email bug control? And where in the documentation would you put this?
Further, while bugs may be
14 matches
Mail list logo
