From nicholas.skaggs at canonical.com Mon Jul 7 20:06:32 2014 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Mon, 07 Jul 2014 16:06:32 -0400 Subject: Utopic Bug Hug (and testing!) Days In-Reply-To: <53AC6CE8.50300@canonical.com> References: <53AC6CE8.50300@canonical.com> Message-ID: <53BAFDC8.3000501@canonical.com> On 06/26/2014 02:56 PM, Nicholas Skaggs wrote: > I'd like to create a combination of the testing days and bug hug days > we've done in the past. Let's have them on the same day as part of a > collaborated effort. We'll work on bug triaging, while executing > testcases and attempting to find new bugs or confirm existing ones. > Curious about what a bug hug day is/was? Checkout > https://wiki.ubuntu.com/UbuntuBugDay for more information. > > Any volunteers for demoing bug triaging? I think this would be > something helpful to demo each time we do one of these. > Still looking for someone to volunteer to show off triaging. You need to be available this Thursday July 10th at 1900 UTC, and be able to join a hangout on air. The demo can be really quick, just triaging a few bugs 'live' and fielding questions. I know there's several good bugmasters who can help out. Volunteers? Nicholas From nicholas.skaggs at canonical.com Tue Jul 8 18:40:15 2014 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Tue, 08 Jul 2014 14:40:15 -0400 Subject: Utopic Bug Hug and Testing Day, June 10th 1900 UTC Message-ID: <53BC3B0F.9040606@canonical.com> The first testing day of the cycle is coming this week on Thursday, June 10th. Elfy and myself will be giving demos and talking about running and testing the development release of ubuntu. You can catch the action live on ubuntuonair.com at 1900 UTC. After the hangout, we'll transition to IRC and keep running tests, reporting results, filing bugs and doing triage work. I'll be around until 2200 UTC, so feel free to swing by late if you can't make it on time. The video will be on youtube following the transmission and you can watch it later at your convenience if needed. This is your chance to ask questions and report some test results. Hope to see everyone there! Nicholas P.S. We have a team calendar that can help you keep track of the release schedule along with this and other events. Check it out https://wiki.ubuntu.com/QATeam/Calendar. From nicholas.skaggs at canonical.com Tue Jul 8 19:39:57 2014 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Tue, 08 Jul 2014 15:39:57 -0400 Subject: Utopic Bug Hug and Testing Day, July 10th 1900 UTC In-Reply-To: <53BC3B0F.9040606@canonical.com> References: <53BC3B0F.9040606@canonical.com> Message-ID: <53BC490D.9090103@canonical.com> On 07/08/2014 02:40 PM, Nicholas Skaggs wrote: > The first testing day of the cycle is coming this week on Thursday, > June 10th. Elfy and myself will be giving demos and talking about > running and testing the development release of ubuntu. > > You can catch the action live on ubuntuonair.com at 1900 UTC. After > the hangout, we'll transition to IRC and keep running tests, reporting > results, filing bugs and doing triage work. I'll be around until 2200 > UTC, so feel free to swing by late if you can't make it on time. The > video will be on youtube following the transmission and you can watch > it later at your convenience if needed. > > This is your chance to ask questions and report some test results. > Hope to see everyone there! > > Nicholas > > P.S. We have a team calendar that can help you keep track of the > release schedule along with this and other events. Check it out > https://wiki.ubuntu.com/QATeam/Calendar. That would be July 10th.. Someone remind me it's 2014 again too, ok? Nicholas From nicholas.skaggs at canonical.com Wed Jul 9 19:51:39 2014 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Wed, 09 Jul 2014 15:51:39 -0400 Subject: Utopic Bug Hug and Testing Day, July 10th 1900 UTC In-Reply-To: <53BC490D.9090103@canonical.com> References: <53BC3B0F.9040606@canonical.com> <53BC490D.9090103@canonical.com> Message-ID: <53BD9D4B.9040202@canonical.com> On 07/08/2014 03:39 PM, Nicholas Skaggs wrote: > On 07/08/2014 02:40 PM, Nicholas Skaggs wrote: >> The first testing day of the cycle is coming this week on Thursday, >> June 10th. Elfy and myself will be giving demos and talking about >> running and testing the development release of ubuntu. >> >> You can catch the action live on ubuntuonair.com at 1900 UTC. > That would be July 10th.. Someone remind me it's 2014 again too, ok? The bughug page is also now live, https://wiki.ubuntu.com/UbuntuBugDay/20140710. You can see we have a list of installer bugs to go after! Bug hug veterans, feel free to point out any errors I may have made in prepping the page ;-) Remember, 23 hours from this mailing the event begins. See you all tomorrow! Nicholas From nicholas.skaggs at canonical.com Thu Jul 10 20:59:08 2014 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Thu, 10 Jul 2014 16:59:08 -0400 Subject: Utopic Bug Hug and Testing Day, July 10th 1900 UTC In-Reply-To: <53BD9D4B.9040202@canonical.com> References: <53BC3B0F.9040606@canonical.com> <53BC490D.9090103@canonical.com> <53BD9D4B.9040202@canonical.com> Message-ID: <53BEFE9C.6040206@canonical.com> On 07/09/2014 03:51 PM, Nicholas Skaggs wrote: > On 07/08/2014 03:39 PM, Nicholas Skaggs wrote: >> On 07/08/2014 02:40 PM, Nicholas Skaggs wrote: >>> The first testing day of the cycle is coming this week on Thursday, >>> June 10th. Elfy and myself will be giving demos and talking about >>> running and testing the development release of ubuntu. >>> >>> You can catch the action live on ubuntuonair.com at 1900 UTC. >> That would be July 10th.. Someone remind me it's 2014 again too, ok? > > The bughug page is also now live, > https://wiki.ubuntu.com/UbuntuBugDay/20140710. > > You can see we have a list of installer bugs to go after! Bug hug > veterans, feel free to point out any errors I may have made in > prepping the page ;-) > > Remember, 23 hours from this mailing the event begins. See you all > tomorrow! > > Nicholas > Thanks to everyone who attended. If you missed it, checkout the recording at https://www.youtube.com/watch?v=3-70xaJsxEM. Happy Testing! Nicholas From noreply at ubuntu.com Wed Jul 9 19:17:08 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 09 Jul 2014 19:17:08 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_nskaggs?= Message-ID: <20140709191708.30837.48243@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Events" page has been changed by nskaggs: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=267&rev2=268 || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20140710| ubiquity]]|| hugday-20140710 || || [[UbuntuBugDay/20130328| update-manager]]|| hugday-20130328 || || [[UbuntuBugDay/Ubuntu-release-upgrader-20130321| ubuntu-release-upgrader]]|| hugday-20130321|| || [[UbuntuBugDay/20130214| Totem]]|| hugday-20130214 || From noreply at ubuntu.com Thu Jul 10 19:12:50 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 10 Jul 2014 19:12:50 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/BugsHeader=22_by_j-matopos?= Message-ID: <20140710191250.30990.94560@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/BugsHeader" page has been changed by j-matopos: http://wiki.ubuntu.com/Bugs/BugsHeader?action=diff&rev1=21&rev2=22 Comment: The link on "Triage a bug" was broken. It now links to Bugs/Triage - ||{{attachment:reportabug.png||height=45}}||'''[[Bugs/ReportingBugs|Report a bug]]'''||||{{attachment:bugsquad.png||height=45}}||'''[[Bugs/Bug triage|Triage a bug]]'''||||{{attachment:fixabug.png||height=45}}||'''[[Bugs/HowToFix|Fix a bug]]'''||||{{attachment:events.png||height=45}}||'''[[Bugs/Events|Events]]'''<
>|| + ||{{attachment:reportabug.png||height=45}}||'''[[Bugs/ReportingBugs|Report a bug]]'''||||{{attachment:bugsquad.png||height=45}}||'''[[Bugs/Triage|Triage a bug]]'''||||{{attachment:fixabug.png||height=45}}||'''[[Bugs/HowToFix|Fix a bug]]'''||||{{attachment:events.png||height=45}}||'''[[Bugs/Events|Events]]'''<
>|| From nicholas.skaggs at canonical.com Mon Jul 14 17:55:40 2014 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Mon, 14 Jul 2014 13:55:40 -0400 Subject: Utopic test writing hackfest In-Reply-To: <53AC79C0.3050800@canonical.com> References: <53AC79C0.3050800@canonical.com> Message-ID: <53C4199C.3070809@canonical.com> On 06/26/2014 03:51 PM, Nicholas Skaggs wrote: > In addition to the bug hug + testing days, I'd like to also schedule > some hackfests to get our tests in shape. What's a hackfest? > > https://wiki.ubuntu.com/QATeam/Hackfest > > We have some outstanding needs on both the automated and manual test > writing efforts. Elfy has already stepped forward to help out on the > manual test front (thank you much!), while perhaps still unbeknownst > to the QA folks, they'll be helping me on the automated test front :-) > Thanks Leo et la! > > So what are we going to be hacking on? If you know python and have > some autopilot knowledge (or willing to learn), we are going to be > hacking on the toolkit helper for autopilot for the ubuntu sdk. That's > a mouthful! Specifically it's the helpers that we use for writing > autopilot tests against ubuntu-sdk applications. All app developers > make use of these helpers, and we need more of them to ensure we have > good coverage for all components developers use. > > If you don't know python, we still need help writing manual testcases! > All you need is some basic tester knowledge and the ability to write > in English. Don't worry, we'll be around to help, and there's guides > to well, guide you! Specifically we'll be looking at writing and > finishing some testcases for ubuntu studio and some other flavors. > > The first is scheduled for July 15th from 1900-2200 UTC. Complete > details, guides, work items, etc are all being collected on the event > page: > > https://wiki.ubuntu.com/QATeam/Hackfest/20140715 > > Questions? Ask away! hope to see everyone there! > > Nicholas Just a reminder this hackfest will be tomorrow. We'll be doing demos again on ubuntuonair.com, so be sure to join us there! https://wiki.ubuntu.com/QATeam/Hackfest/20140715 Nicholas From nicholas.skaggs at canonical.com Wed Jul 16 20:44:27 2014 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Wed, 16 Jul 2014 16:44:27 -0400 Subject: Utopic test writing hackfest In-Reply-To: <53C4199C.3070809@canonical.com> References: <53AC79C0.3050800@canonical.com> <53C4199C.3070809@canonical.com> Message-ID: <53C6E42B.1@canonical.com> On 07/14/2014 01:55 PM, Nicholas Skaggs wrote: > On 06/26/2014 03:51 PM, Nicholas Skaggs wrote: >> In addition to the bug hug + testing days, I'd like to also schedule >> some hackfests to get our tests in shape. What's a hackfest? >> >> https://wiki.ubuntu.com/QATeam/Hackfest >> >> We have some outstanding needs on both the automated and manual test >> writing efforts. Elfy has already stepped forward to help out on the >> manual test front (thank you much!), while perhaps still unbeknownst >> to the QA folks, they'll be helping me on the automated test front >> :-) Thanks Leo et la! >> >> So what are we going to be hacking on? If you know python and have >> some autopilot knowledge (or willing to learn), we are going to be >> hacking on the toolkit helper for autopilot for the ubuntu sdk. >> That's a mouthful! Specifically it's the helpers that we use for >> writing autopilot tests against ubuntu-sdk applications. All app >> developers make use of these helpers, and we need more of them to >> ensure we have good coverage for all components developers use. >> >> If you don't know python, we still need help writing manual >> testcases! All you need is some basic tester knowledge and the >> ability to write in English. Don't worry, we'll be around to help, >> and there's guides to well, guide you! Specifically we'll be looking >> at writing and finishing some testcases for ubuntu studio and some >> other flavors. >> >> The first is scheduled for July 15th from 1900-2200 UTC. Complete >> details, guides, work items, etc are all being collected on the event >> page: >> >> https://wiki.ubuntu.com/QATeam/Hackfest/20140715 >> >> Questions? Ask away! hope to see everyone there! >> >> Nicholas > Just a reminder this hackfest will be tomorrow. We'll be doing demos > again on ubuntuonair.com, so be sure to join us there! > > https://wiki.ubuntu.com/QATeam/Hackfest/20140715 > > Nicholas For those who missed it, it's not too late to both watch the video and try your hand at some of the tasks listed on the hackfest. Bugs are still open and we still need your help! https://wiki.ubuntu.com/QATeam/Hackfest/20140715 https://www.youtube.com/watch?v=2lAmjBr-Khw Feel free to ping myself, elopio, or elfy if you get stuck or need help getting started. Thanks everyone! Nicholas From leo.arias at canonical.com Thu Jul 17 07:37:14 2014 From: leo.arias at canonical.com (Leo Arias) Date: Thu, 17 Jul 2014 01:37:14 -0600 Subject: Utopic test writing hackfest In-Reply-To: <53C6E42B.1@canonical.com> References: <53AC79C0.3050800@canonical.com> <53C4199C.3070809@canonical.com> <53C6E42B.1@canonical.com> Message-ID: Here is my quick and incomplete guide to contribute helpers to the toolkit: http://pad.ubuntu.com/contributing-toolkit-helpers After cleaning it up a little, it might be good to put it in a wiki page or a file in the branch. Please give it a try if you want to start writing helpers, and let me know if you find something wrong or just fix it on the pad. Thanks balloons. pura vida. -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Sat Jul 19 16:17:58 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sat, 19 Jul 2014 18:17:58 +0200 Subject: We could automatically clean End Of Life bugs Message-ID: <53CA9A36.5050509@gmail.com> Looking at the list of confirmed bugs affecting Ubuntu and the same list tagged with the current supported releases, we can see that around the 70% of bugs in Launchpad are not tagged with those; what suggests that a big amount of bugs are simply End Of Life. I believe we can just jump on reading these reports and save a huge amount of time by just writing a bot that checks for tags in the report, and if the report doesn't have any with a current supported release name do the following: 1. Set the bug status to "Incomplete". 2. Print the following message: "If you are still experiencing this issue in any currently supported release (https://wiki.ubuntu.com/Releases), please set the status back to its previous setting". What do you think? From teward at trekweb.org Sat Jul 19 16:27:51 2014 From: teward at trekweb.org (Thomas Ward) Date: Sat, 19 Jul 2014 12:27:51 -0400 Subject: We could automatically clean End Of Life bugs In-Reply-To: <53CA9A36.5050509@gmail.com> References: <53CA9A36.5050509@gmail.com> Message-ID: <10D435CE-192D-460D-A882-4BF0104DA4ED@trekweb.org> Actually a good portion of "End of Life" bugs are typically cleaned up on an automated process, last I checked. I believe there's an automatic script that runs for some of the packages by people on the Security team and other teams, but I do not know the extent of those that get covered. From observations, EOL release targeted bugs go to "Won't Fix", if they've targeted it to the specific EOL release, and "Incomplete" if you're waiting on confirmation of the bug existing in a later release than the EOL one. There are a few special case bugs I watch in nginx, for example, where that second criterion is matched. (I may be wrong, as this is just built from my observations on EOL-release bugs.) ------ Thomas *Sent from my iPhone. Please excuse any typos, as they are likely to happen by accident.* > On Jul 19, 2014, at 12:17, Alberto Salvia Novella wrote: > > Looking at the list of confirmed bugs affecting Ubuntu and the same list tagged with the current supported releases, we can see that around the 70% of bugs in Launchpad are not tagged with those; what suggests that a big amount of bugs are simply End Of Life. > > I believe we can just jump on reading these reports and save a huge amount of time by just writing a bot that checks for tags in the report, and if the report doesn't have any with a current supported release name do the following: > > 1. Set the bug status to "Incomplete". > > 2. Print the following message: "If you are still experiencing this issue in any currently supported release (https://wiki.ubuntu.com/Releases), please set the status back to its previous setting". > > What do you think? > > > -- > Ubuntu-quality mailing list > Ubuntu-quality at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality From es20490446e at gmail.com Sat Jul 19 16:29:45 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sat, 19 Jul 2014 18:29:45 +0200 Subject: We could automatically clean End Of Life bugs In-Reply-To: <53CA9A36.5050509@gmail.com> References: <53CA9A36.5050509@gmail.com> Message-ID: <53CA9CF9.7020708@gmail.com> Alberto Salvia Novella: > 2. Print the following message: "If you are still experiencing this > issue in any currently supported release > (https://wiki.ubuntu.com/Releases), please set the status back to its > previous setting". Sorry, and ask for proper tagging too: "If you are still experiencing this issue in any currently supported release (https://wiki.ubuntu.com/Releases), please: 1. Add its name to the tag list under the bug description. 2. Set the bug status back to its previous setting." From maarten.bezemer at gmail.com Sat Jul 19 16:54:48 2014 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Sat, 19 Jul 2014 18:54:48 +0200 Subject: We could automatically clean End Of Life bugs In-Reply-To: <53CA9A36.5050509@gmail.com> References: <53CA9A36.5050509@gmail.com> Message-ID: <5080944.KH2YpXfucL@i7> On Saturday 19 July 2014 18:17:58 Alberto Salvia Novella wrote: > What do you think? EOL bugs can still be present in active releases... So just closing these bugs without checking if it is still present, is wasting the efforts of the reporters (just to have a low open bug count.) and does not show much respect toward these reporters (in my opinion). Regards, Maarten From brian at ubuntu.com Sat Jul 19 18:25:54 2014 From: brian at ubuntu.com (Brian Murray) Date: Sat, 19 Jul 2014 11:25:54 -0700 Subject: We could automatically clean End Of Life bugs In-Reply-To: <10D435CE-192D-460D-A882-4BF0104DA4ED@trekweb.org> References: <53CA9A36.5050509@gmail.com> <10D435CE-192D-460D-A882-4BF0104DA4ED@trekweb.org> Message-ID: <20140719182554.GX6659@murraytwins.com> On Sat, Jul 19, 2014 at 12:27:51PM -0400, Thomas Ward wrote: > Actually a good portion of "End of Life" bugs are typically cleaned up > on an automated process, last I checked. I believe there's an > automatic script that runs for some of the packages by people on the > Security team and other teams, but I do not know the extent of those > that get covered. > > From observations, EOL release targeted bugs go to "Won't Fix", if > they've targeted it to the specific EOL release, and "Incomplete" if > you're waiting on confirmation of the bug existing in a later release > than the EOL one. There are a few special case bugs I watch in nginx, > for example, where that second criterion is matched. > > (I may be wrong, as this is just built from my observations on EOL-release bugs.) I believe you are confusing bug tasks targeted to an End of Life release and the generic bug task for the package which by default applies to the current release. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From brian at ubuntu.com Sat Jul 19 18:28:37 2014 From: brian at ubuntu.com (Brian Murray) Date: Sat, 19 Jul 2014 11:28:37 -0700 Subject: We could automatically clean End Of Life bugs In-Reply-To: <5080944.KH2YpXfucL@i7> References: <53CA9A36.5050509@gmail.com> <5080944.KH2YpXfucL@i7> Message-ID: <20140719182837.GY6659@murraytwins.com> On Sat, Jul 19, 2014 at 06:54:48PM +0200, Maarten Bezemer wrote: > On Saturday 19 July 2014 18:17:58 Alberto Salvia Novella wrote: > > What do you think? > > EOL bugs can still be present in active releases... So just closing these bugs > without checking if it is still present, is wasting the efforts of the > reporters (just to have a low open bug count.) and does not show much respect > toward these reporters (in my opinion). I agree with this opinion, its entirely possible the person is no longer using Ubuntu or Launchpad or any other of a multitude of things, and consequently will not reply to the bug report and then it will just auto-expire. This does not mean that the bug is invalid though, we should do some investigate work to determine whether or not the bug still exists or if there is enough information to make such a determination. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From teward at trekweb.org Sat Jul 19 18:38:57 2014 From: teward at trekweb.org (Thomas Ward) Date: Sat, 19 Jul 2014 14:38:57 -0400 Subject: We could automatically clean End Of Life bugs In-Reply-To: <20140719182554.GX6659@murraytwins.com> References: <53CA9A36.5050509@gmail.com> <10D435CE-192D-460D-A882-4BF0104DA4ED@trekweb.org> <20140719182554.GX6659@murraytwins.com> Message-ID: Ahh, yeah, you're right. I tend to make it a habit of adding the task for that release and marking the bug otherwise for the latest release and leave the task for monitoring it for the affected release, which is why I observe things as such. Otherwise, bugs don't get touched if they don't have the task, you're right. (My fault on the miscommunication) *Sent from my iPhone. Please excuse any typos, as they are likely to happen by accident.* > On Jul 19, 2014, at 14:25, Brian Murray wrote: > >> On Sat, Jul 19, 2014 at 12:27:51PM -0400, Thomas Ward wrote: >> Actually a good portion of "End of Life" bugs are typically cleaned up >> on an automated process, last I checked. I believe there's an >> automatic script that runs for some of the packages by people on the >> Security team and other teams, but I do not know the extent of those >> that get covered. >> >> From observations, EOL release targeted bugs go to "Won't Fix", if >> they've targeted it to the specific EOL release, and "Incomplete" if >> you're waiting on confirmation of the bug existing in a later release >> than the EOL one. There are a few special case bugs I watch in nginx, >> for example, where that second criterion is matched. >> >> (I may be wrong, as this is just built from my observations on EOL-release bugs.) > > I believe you are confusing bug tasks targeted to an End of Life release > and the generic bug task for the package which by default applies to the > current release. > > -- > Brian Murray > Ubuntu Bug Master From dtl131 at gmail.com Sat Jul 19 19:11:10 2014 From: dtl131 at gmail.com (Daniel Letzeisen) Date: Sat, 19 Jul 2014 15:11:10 -0400 Subject: We could automatically clean End Of Life bugs In-Reply-To: <5080944.KH2YpXfucL@i7> References: <53CA9A36.5050509@gmail.com> <5080944.KH2YpXfucL@i7> Message-ID: <53CAC2CE.6020204@gmail.com> On 07/19/2014 12:54 PM, Maarten Bezemer wrote: > EOL bugs can still be present in active releases... So just closing these bugs > without checking if it is still present, is wasting the efforts of the > reporters ... and does not show much respect > toward these reporters (in my opinion). > Yes, they can still be present, but unless the reporter confirms that it is still present in a supported release, the bug should automatically go to Incomplete if it is tagged with EOL release(s). I do not agree that it is disrespectful, since marking it Incomplete gives the user two months to confirm that they still experience it with a supported version. In fact, I think users find it more disrespectful when their report stays open for years without response and basically goes into a state of limbo. Oh, and I also find it odd that apport allows users to file bugs with EOL releases.. > (just to have a low open bug count.) Bug count is not a terribly useful metric itself, but lower bug count makes searching easier/quicker. From brian at ubuntu.com Sat Jul 19 19:31:24 2014 From: brian at ubuntu.com (Brian Murray) Date: Sat, 19 Jul 2014 12:31:24 -0700 Subject: We could automatically clean End Of Life bugs In-Reply-To: <53CAC2CE.6020204@gmail.com> References: <53CA9A36.5050509@gmail.com> <5080944.KH2YpXfucL@i7> <53CAC2CE.6020204@gmail.com> Message-ID: <20140719193124.GZ6659@murraytwins.com> On Sat, Jul 19, 2014 at 03:11:10PM -0400, Daniel Letzeisen wrote: > On 07/19/2014 12:54 PM, Maarten Bezemer wrote: > > >EOL bugs can still be present in active releases... So just closing these bugs > >without checking if it is still present, is wasting the efforts of the > >reporters ... and does not show much respect > >toward these reporters (in my opinion). > > > > Yes, they can still be present, but unless the reporter confirms > that it is still present in a supported release, the bug should > automatically go to Incomplete if it is tagged with EOL release(s). > I do not agree that it is disrespectful, since marking it Incomplete > gives the user two months to confirm that they still experience it > with a supported version. In fact, I think users find it more > disrespectful when their report stays open for years without > response and basically goes into a state of limbo. > > Oh, and I also find it odd that apport allows users to file bugs > with EOL releases.. That's bug 834895 and should be relatively easy to fix, although we can't SRU it to Saucy because it is already End of Life! However, it would be a good target for fixing in Utopic and I'm happy to help someone work on this. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From dtl131 at gmail.com Sat Jul 19 19:41:58 2014 From: dtl131 at gmail.com (Daniel Letzeisen) Date: Sat, 19 Jul 2014 15:41:58 -0400 Subject: We could automatically clean End Of Life bugs In-Reply-To: <20140719182837.GY6659@murraytwins.com> References: <53CA9A36.5050509@gmail.com> <5080944.KH2YpXfucL@i7> <20140719182837.GY6659@murraytwins.com> Message-ID: <53CACA06.9070307@gmail.com> On 07/19/2014 02:28 PM, Brian Murray wrote: > This does not mean that the bug is invalid though, we > should do some investigate work to determine whether or not the bug > still exists or if there is enough information to make such a > determination. > With the amount of new bug reports coming in vs. the limited manpower of bug team, I don't think that's practical. I think Fedora/RH has a much better approach in this regard (though I don't care for bugzilla in general). From walter.garcia at upf.edu Sun Jul 20 12:10:37 2014 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Sun, 20 Jul 2014 14:10:37 +0200 Subject: We could automatically clean End Of Life bugs In-Reply-To: <5080944.KH2YpXfucL@i7> References: <53CA9A36.5050509@gmail.com> <5080944.KH2YpXfucL@i7> Message-ID: <20140720121037.GC20668@upf.edu> * Maarten Bezemer, maarten.bezemer at gmail.com [19/07/14 18:55]: > On Saturday 19 July 2014 18:17:58 Alberto Salvia Novella wrote: > > What do you think? > > EOL bugs can still be present in active releases... So just closing these bugs > without checking if it is still present, is wasting the efforts of the > reporters (just to have a low open bug count.) and does not show much respect > toward these reporters (in my opinion). This is exactly what I was thinking, usually reporters are quite pissed off about unattended bugs, if they get a bot response closing their report they can get even more pissed off. -- Walter Garcia-Fontes From es20490446e at gmail.com Sun Jul 20 13:32:47 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sun, 20 Jul 2014 15:32:47 +0200 Subject: We could automatically clean End Of Life bugs In-Reply-To: <53CAC2CE.6020204@gmail.com> References: <53CA9A36.5050509@gmail.com> <5080944.KH2YpXfucL@i7> <53CAC2CE.6020204@gmail.com> Message-ID: <53CBC4FF.2050608@gmail.com> Daniel Letzeisen: > Yes, they can still be present, but unless the reporter confirms that it > is still present in a supported release, the bug should automatically go > to Incomplete if it is tagged with EOL release(s). This is exactly what a human will do, and there will be no difference if it is done by a bot. The probability of discarding a good bug automatically by setting it to "incomplete" and asking the user for confirming the bug is the same for a human than for a bot. The only difference will be that you will save bug squad members from looking at the 70% of bugs in Launchpad. Walter Garcia-Fontes: > This is exactly what I was thinking, usually reporters are quite > pissed off about unattended bugs, if they get a bot response closing > their report they can get even more pissed off. The bot shall not close the bug, but ask the user for information by setting the status to "incomplete"; exactly as it would be done by a human. In fact what really pisses the user is to have their reports managed slow, and the root cause of this is looking at tons of reports that doesn't matter or could be managed automatically. Then, years later, answering using bottled friendliness language; while what these users are really expecting for is simply to know you are addressing the REAL issue. Regards. From noreply at ubuntu.com Thu Jul 17 10:52:12 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 17 Jul 2014 10:52:12 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Triage=22_by_lifeboy?= Message-ID: <20140717105212.20653.85936@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Triage" page has been changed by lifeboy: http://wiki.ubuntu.com/Bugs/Triage?action=diff&rev1=162&rev2=163 Comment: Fix the link to Bugs/Triage/Charts Bug triage is a lot like that because we assess bugs to determine whether or not they have enough information to be worked on and assign a priority to them as soon as possible. Without any risk of death. This page explains the different aspects of triaging. - Ubuntu receives an incredibly large number of bug reports every day through our [[https://bugs.launchpad.net/ | bug tracking system]]. Each one of these needs to be read, assessed, and sorted so it can be fixed. This is where we could use your assistance with HelpingWithBugs. For a visual representation of the bug triage process, see these nice [[Bugs/HowToTriage/Charts|Flow Charts]]. + Ubuntu receives an incredibly large number of bug reports every day through our [[https://bugs.launchpad.net/ | bug tracking system]]. Each one of these needs to be read, assessed, and sorted so it can be fixed. This is where we could use your assistance with HelpingWithBugs. For a visual representation of the bug triage process, see these nice [[Bugs/Triage/Charts|Flow Charts]]. Every bug report is a conversation with the reporter. The first contact any reporter usually has with the Ubuntu community is through a bug triager, who tries to put together a complete bug report. It's very important that we give a good impression, so please be polite and try to use your best English. From dwh96913 at yahoo.com Wed Jul 23 10:22:01 2014 From: dwh96913 at yahoo.com (Dave Hastings) Date: Wed, 23 Jul 2014 03:22:01 -0700 Subject: HACKED Message-ID: <1406110921.48522.YahooMailBasic@web160201.mail.bf1.yahoo.com> Hello, I am sending this email on a old desktop with XP, because my ubuntu 14.04 has been so hacked, I am actually having hem interfer with logging into yahoo: they make the typed words on log-in disappear. I sent this already to the website with a log, got a replyu to check my settings. The report was that my seetings will not open, none of them. Someone has placed "Me" as admin: I can't control machine at all. What the heck is going on, this is a serious hack. What should I provide top you? Thank you, Dave From martincigorraga at gmail.com Fri Jul 25 16:09:55 2014 From: martincigorraga at gmail.com (=?UTF-8?Q?Mart=C3=ADn_Cigorraga?=) Date: Fri, 25 Jul 2014 13:09:55 -0300 Subject: HACKED In-Reply-To: <1406110921.48522.YahooMailBasic@web160201.mail.bf1.yahoo.com> References: <1406110921.48522.YahooMailBasic@web160201.mail.bf1.yahoo.com> Message-ID: On Wed, Jul 23, 2014 at 7:22 AM, Dave Hastings wrote: > Hello, > > I am sending this email on a old desktop with XP, because my ubuntu 14.04 > has been so hacked, I am actually having hem interfer with logging into > yahoo: they make the typed words on log-in disappear. > > I sent this already to the website with a log, got a replyu to check my > settings. > > The report was that my seetings will not open, none of them. Someone has > placed "Me" as admin: I can't control machine at all. > > What the heck is going on, this is a serious hack. > > What should I provide top you? > > Thank you, > Dave > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > WOOT!? What do you *exactly* mean by 'hacked'!? In which way you are using the word, as the yellow-press & the Average Joe or as a computer knowledgeable person!? Is this email even real or just a spam!? -Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: