Re: What if users warned about critical bugs?
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. Certainly, having bug-control alerted could be helpful. It does raise another question though. What would make this any different than a normal bug report? Charles On Mon, 2014-11-10 at 00:59 -0500, Thomas Ward wrote: 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 'critical' and need attention, does everyone on bug control really need to be notified of every critical bug? I'm curious what your reasoning for asking this question is. Mind explaining how you came up with this suggestion/idea? -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: What if users warned about critical bugs?
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 email bug control? So the team can set importance early, instead these bugs remain unnoticed in a pool of reports. Thomas Ward: And where in the documentation would you put this? On https://help.ubuntu.com/community/ReportingBugs. Thomas Ward: Further, while bugs may be 'critical' and need attention, does everyone on bug control really need to be notified of every critical bug? There are only 47 known critical bugs for all the supported releases, and only 14 affecting Utopic. Probably the Bug Control team would be receiving less than 10 emails for every circle of 6 months. Thomas Ward: Mind explaining how you came up with this suggestion/idea? Because I noticed many critical bugs only get marked as such after a long time has passed. Charles Profit: What would make this any different than a normal bug report? Nearly no critical bug would go unnoticed into releases, and broken systems would be unusable for the shortest period of time. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: What if users warned about critical bugs?
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 could be a positive one, but I too question how they would know a bug is critical. Certainly, having bug-control alerted could be helpful. It does raise another question though. What would make this any different than a normal bug report? Charles On Mon, 2014-11-10 at 00:59 -0500, Thomas Ward wrote: 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 'critical' and need attention, does everyone on bug control really need to be notified of every critical bug? I'm curious what your reasoning for asking this question is. Mind explaining how you came up with this suggestion/idea? -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality How would this be any different than a bug that ends up in red on the bug tracker that makes an install fail. I am not sure about things in packages on in the installer though that is a harder question to answer. Notifying bug control of things like that may be nice but I don't know of any systems already in place. 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 this fixed badly therefore it is critical. I think we need to not only know when users correctly identify critical bugs but what happens with mistakes and what makes ubuntu have better quailty overall. A bug tag on launchpad like iso-testing-critical for bugs that caused a failed testcase could be something to make triaging easier and would encourage people to use the tracker and would work on top of the already existing infrastructre. Or maybe iso-testing-fail could be another name for the tag. -- Brendan Perrine walteror...@gmail.com -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: What if users warned about critical bugs?
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 if the bug causes data corruption or renders the system temporally or permanently unusable, please warn about it to the Bug Control team. I think this is a good idea, definitely worth trying :-) We need to be really careful with how we define 'data corruption'. There are cases, such as in the nginx package, where data is overwritten by the package because it ships defaults. If the configuration files, and/or included default file directories, get overwritten, this can cause 'data corruption via overwriting', but that's not a Critical bug, that's a case where the user used the default location controlled by the package manager, not necessarily a bug in the package itself. If we define 'data corruption' to be, say, a partition-wide corruption, that's different than a few configs being deleted or corrupted but. being repairable or replaceable. Therefore, we need to explicitly define 'data corruption' in context of how we want something to be determined as 'critical'. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: What if users warned about critical bugs?
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 this fixed badly therefore it is critical. In the last term the Bug Control team is who sets the importance, not the reported. 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? As well, we're going to have a lot of users who aren't familiar with the importance criterion, emailing in and saying Oh, this is critical, because they don't read the importance requirements, and we're probably going to get higher amounts of incorrectly-reported items in the bug control inbox. Brendan Perrine: How would this be any different than a bug that ends up in red on the bug tracker that makes an install fail. Nothing, as the bug would be tracked in Launchpad equally. If this makes it no different than any other bug, how does notifying Bug Control about potentially critical bugs make any real difference? Just because we set the importance does not mean it gets fixed faster. Brendan Perrine: A bug tag on launchpad like iso-testing-critical for bugs that caused a failed testcase could be something to make triaging easier and would encourage people to use the tracker and would work on top of the already existing infrastructre. Why putting critical to a tag when there's already a field for priorities? How can adding a new tag to the list of 123 we have encourage people to use the tracker? This. There's no need for a 'critical' tag. If we had a 'critical' tag we'd need the additional tags for every other importance and that's not necessarily needed. -- Thomas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Displayport Testing Request
If you have an Intel VGA with DisplayPort 1.2 and either * 2 DisplayPort 1.2 MST-enabled displays in a daisy-chain configuration, or * a DisplayPort 1.2 MST-enabled hub connected to 2 regular DisplayPort monitors. there's a sticky bug the kernel team would like to see more testing on. Check out https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1104230 and do give the ppa from Dariusz with the proposed fix a whirl. If you test and get positive or negative results, please simply leave feedback in the bug itself so Dariusz and the kernel folks see it. Thanks everyone and happy testing! Nicholas -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Fwd: Typo in Vagrant Cloud box description
Jared Beck: I think I found a typo in a Vagrant Cloud Ubuntu box description (see http://tinyurl.com/p848ya2). I reported it to the Ubuntu Documentation team, but they were unaware of Vagrant Cloud. Seth Vargo: Thank you for finding that typo! Unfortunately HashiCorp does not control third-party boxes; it is the responsibility of the box maintainer(s) to keep box information up-to-date and fix these types of issues. Regarding ownership, I have confirmed that the |ubuntu| organization is owned by a user with an |@ubuntu.com| email address. Due to the way our registration system works (confirmation by email is required), it is highly unlikely that individual is /not/ a member of the Ubuntu organization. Due to our privacy policy, I cannot give you the name or email address of that individual who owns the Ubuntu organization on Vagrant Cloud. Do you know where this needs to be reported? -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: What if users warned about critical bugs?
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 Launchpad to short those first when visiting a project bug section, even for a package maintainer or somebody willing to report bugs upstream while triaging. Thomas Ward: As well, we're going to have a lot of users who aren't familiar with the importance criterion, emailing in and saying Oh, this is critical, because they don't read the importance requirements, and we're probably going to get higher amounts of incorrectly-reported items in the bug control inbox. So better to change saying it is critical for telling it renders the system temporally or permanently unusable. Thomas Ward: Just because we set the importance does not mean it gets fixed faster. Because critical flaws are discovered sooner, it also allows to work on them sooner. To stop watering weeds for watering trees. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
