From bryce at canonical.com Wed Apr 1 01:55:45 2009 From: bryce at canonical.com (Bryce Harrington) Date: Tue, 31 Mar 2009 18:55:45 -0700 Subject: X.org glossary (Was Re: Announcing the Next Ubuntu Hug Day! - April 02 2009) In-Reply-To: <1238442865.6824.9.camel@thylacine> References: <1238442865.6824.9.camel@thylacine> Message-ID: <20090401015545.GB7966@bryceharrington.org> Ever wondered why your pipe-A underruns and your EQ overflows? These and other cryptic X.org error terms now have a handy glossary available from the Ubuntu-X wiki, put together with Jesse Barnes' help for all you bug triagers: https://wiki.ubuntu.com/X/Glossary See you for Hug Day Thursday! Bryce On Mon, Mar 30, 2009 at 03:54:25PM -0400, Pedro Villavicencio Garrido wrote: > Fellow Ubuntu Triagers! > > This week's HugDay target is *drum roll please* xorg-server and xserver-xorg-video-intel! > * 49 New bugs need a hug. > * 103 Incomplete bugs need a status check. > * 81 Confirmed bugs need a review. > * 16 Bugs with patches that need to be reviewed. > > Bookmark it, add it to your calendars, turn over those egg-timers! > * April 02 2009 > * https://wiki.ubuntu.com/UbuntuBugDay/20090402 > > Can't stress it enough: everyone can help! > > Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) > Have a blog? Blog about Hugday! > Have some screen space? Open #ubuntu-bugs and keep an eye out for > newcomers in need. > Have minions? Teach THEM to triage for you! :) > > Wanna be famous? Is easy! remember to use 5-A-day so if you do a good > work your name could be listed at the top 5-A-Day Contributors in the > Ubuntu Hall of Fame page! > > Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and > night, and will be ready to answer your questions about how to help. > > If you're new to all this, head to > http://wiki.ubuntu.com/Bugs > > Have a nice day, > > pedro. > > > -- > ubuntu-devel-announce mailing list > ubuntu-devel-announce at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce From martinmai-ubuntu at web.de Tue Apr 7 09:21:59 2009 From: martinmai-ubuntu at web.de (Martin Mai) Date: Tue, 07 Apr 2009 11:21:59 +0200 Subject: Announcing the Next Ubuntu Hug Day! - 9th of April, 2009 Message-ID: <1239096119.6205.3.camel@martin-laptop> Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* bugs with patches! * #486 New bugs with patches need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 9th of April, 2009 * http://wiki.ubuntu.com/UbuntuBugDay/20090409 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, Martin Mai [From the BugSquad] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From dqaz101 at yahoo.com Wed Apr 8 18:02:45 2009 From: dqaz101 at yahoo.com (Tyler Johnson) Date: Wed, 8 Apr 2009 11:02:45 -0700 (PDT) Subject: No subject Message-ID: <610454.41419.qm@web59313.mail.re1.yahoo.com> Check out these fonts that we could put on Ubuntu. They are so cool. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Newest_Font.zip Type: application/x-zip-compressed Size: 601 bytes Desc: not available URL: From macoafi at gmail.com Wed Apr 8 18:32:13 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Wed, 8 Apr 2009 14:32:13 -0400 Subject: No subject In-Reply-To: <610454.41419.qm@web59313.mail.re1.yahoo.com> References: <610454.41419.qm@web59313.mail.re1.yahoo.com> Message-ID: <200904081432.17266.macoafi@gmail.com> On Wednesday 08 April 2009 2:02:45 pm Tyler Johnson wrote: > Check out these fonts that we could put on Ubuntu. They are so cool. SPAM -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From sense at qense.nl Wed Apr 8 18:55:43 2009 From: sense at qense.nl (Sense Hofstede) Date: Wed, 8 Apr 2009 20:55:43 +0200 Subject: No subject In-Reply-To: <200904081432.17266.macoafi@gmail.com> References: <610454.41419.qm@web59313.mail.re1.yahoo.com> <200904081432.17266.macoafi@gmail.com> Message-ID: 2009/4/8 Mackenzie Morgan : > On Wednesday 08 April 2009 2:02:45 pm Tyler Johnson wrote: >> Check out these fonts that we could put on Ubuntu. They are so cool. > > SPAM > > -- > Mackenzie Morgan > http://ubuntulinuxtipstricks.blogspot.com > apt-get moo > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > Even GMail marked it as spam! -- Sense Hofstede From macoafi at gmail.com Wed Apr 8 19:21:50 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Wed, 8 Apr 2009 15:21:50 -0400 Subject: No subject In-Reply-To: References: <610454.41419.qm@web59313.mail.re1.yahoo.com> <200904081432.17266.macoafi@gmail.com> Message-ID: <200904081521.53785.macoafi@gmail.com> On Wednesday 08 April 2009 2:55:43 pm Sense Hofstede wrote: > 2009/4/8 Mackenzie Morgan : > > On Wednesday 08 April 2009 2:02:45 pm Tyler Johnson wrote: > >> Check out these fonts that we could put on Ubuntu. They are so cool. > > > > SPAM GMail didn't catch it. I read it went "looks like spam" and asked Ark what was in the archive. A .lnk file...which is a link file for Windows...now, does *that* sound likely to have anything to do with TTFs? -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From dqaz101 at yahoo.com Wed Apr 8 20:29:11 2009 From: dqaz101 at yahoo.com (Tyler Johnson) Date: Wed, 8 Apr 2009 13:29:11 -0700 (PDT) Subject: No subject Message-ID: <471479.1553.qm@web59311.mail.re1.yahoo.com> sorry. i didn't send that. someone hacked my e-mail and sent it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From macoafi at gmail.com Wed Apr 8 20:41:04 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Wed, 8 Apr 2009 16:41:04 -0400 Subject: No subject In-Reply-To: <471479.1553.qm@web59311.mail.re1.yahoo.com> References: <471479.1553.qm@web59311.mail.re1.yahoo.com> Message-ID: <200904081641.09137.macoafi@gmail.com> On Wednesday 08 April 2009 4:29:11 pm Tyler Johnson wrote: > sorry. i didn't send that. someone hacked my e-mail and sent it. Any chance you've got that account setup in a mail client on Windows somewhere? Maybe it got a virus. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From andreas.moog at warperbbs.de Tue Apr 14 22:21:07 2009 From: andreas.moog at warperbbs.de (Andreas Moog) Date: Wed, 15 Apr 2009 00:21:07 +0200 Subject: Status "FixCommited" for ubuntu-tasks Message-ID: <49E50C53.9060606@warperbbs.de> Hello Bugsquad, i had a short discussion today in #ubuntu-bugs about when to set the status of an ubuntu-task to "FixCommited". I used this status to indicate that a patch was commited in upstream's svn/cvs/git/$whatever so that one could easily find what reports could be closed by a package-update. Another opinion on "FixCommited" was that it should only be used when a package with this patch is in -proposed OR uploaded and waiting to be accepted. If the latter is the majority opinion here, we should discuss having a new status in malone, e.g. called "FixedUpstream" to easily spot already fixed bugs. Thanks for your opinion. -- Andreas Moog Berliner Str. 29 36205 Sontra Germany Tel.:+49(0)56 53 91 24 3 PGP-Encrypted mail preferred, please use Key-ID 0xF67089C4 Fingerprint: 7C60 6E85 F8A1 E26C 96B4 CC8D D3A1 6090 F670 89C4 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From cjk at teamcharliesangels.com Tue Apr 14 22:45:22 2009 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Tue, 14 Apr 2009 16:45:22 -0600 Subject: Status "FixCommited" for ubuntu-tasks In-Reply-To: <49E50C53.9060606@warperbbs.de> References: <49E50C53.9060606@warperbbs.de> Message-ID: <20090414164522.72406c8e@teamcharliesangels.com> On Wed, 15 Apr 2009 00:21:07 +0200 Andreas Moog wrote: > Hello Bugsquad, > > i had a short discussion today in #ubuntu-bugs about when to set the > status of an ubuntu-task to "FixCommited". I used this status to > indicate that a patch was commited in upstream's svn/cvs/git/$whatever > so that one could easily find what reports could be closed by a > package-update. > > Another opinion on "FixCommited" was that it should only be used when > a package with this patch is in -proposed OR uploaded and waiting to > be accepted. > > If the latter is the majority opinion here, we should discuss having a > new status in malone, e.g. called "FixedUpstream" to easily spot > already fixed bugs. > > Thanks for your opinion. > I have used "Fixcommitted"when the fix in is in any -proposed or svn. I thought that was correct status per previous discussions about this. If this is incorrect, then I feel strongly a status needs to be added for those bugs which are simply sitting waiting for the upstream fix to get to Ubuntu. It seems a bit out of place to have these sitting in confirmed/incomplete status when the fix is out there. Any of these bugs forwarded upstream may or may not have the upstream status updated, depending on whether or not the upstream updates are working at the time. Many of the bugs that are forwarded are left in unknown status against the project because the automatic updates do not work. That leaves the bugsquad members to do a lot of manual tracking for themselves so as to not have to keep looking up status on bugs that should be "FixCommitted". Obviously, if the fix is upstream, it is going to make it into Ubuntu, even if it is in the next version. Not using "FixCommitted" for Ubuntu makes it much harder to triage the bugs. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From hggdh2 at gmail.com Tue Apr 14 23:28:37 2009 From: hggdh2 at gmail.com (C de-Avillez) Date: Tue, 14 Apr 2009 18:28:37 -0500 Subject: Status "FixCommited" for ubuntu-tasks In-Reply-To: <20090414164522.72406c8e@teamcharliesangels.com> References: <49E50C53.9060606@warperbbs.de> <20090414164522.72406c8e@teamcharliesangels.com> Message-ID: <20090414182837.6863e72e@xango2> On Tue, 14 Apr 2009 16:45:22 -0600 Charlie Kravetz wrote: > Not using "FixCommitted" for Ubuntu makes it much > harder to triage the bugs. > I think both Charlie and Andreas are correct. +1 from me. It makes no sense to restrict "fix committed" to upstream tasks, or when the Ubuntu fix has been placed on -proposed. Or, as said in the previous emails, add a new status for the Ubuntu tasks. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From maxb at f2s.com Tue Apr 14 23:33:00 2009 From: maxb at f2s.com (Max Bowsher) Date: Wed, 15 Apr 2009 00:33:00 +0100 Subject: Status "FixCommited" for ubuntu-tasks In-Reply-To: <49E50C53.9060606@warperbbs.de> References: <49E50C53.9060606@warperbbs.de> Message-ID: <49E51D2C.6060804@f2s.com> Andreas Moog wrote: > Hello Bugsquad, > > i had a short discussion today in #ubuntu-bugs about when to set the > status of an ubuntu-task to "FixCommited". I used this status to > indicate that a patch was commited in upstream's svn/cvs/git/$whatever > so that one could easily find what reports could be closed by a > package-update. > > Another opinion on "FixCommited" was that it should only be used when a > package with this patch is in -proposed OR uploaded and waiting to be > accepted. My understanding, based on https://wiki.ubuntu.com/Bugs/Status, is that the current policy is somewhere between the two: The status of a ubuntu-task should not have anything to do with upstream (upstream is, after all, not Ubuntu), but on the other hand it is not required for the package to be in -proposed or the queue - having the fix in the package's version control system, or if it doesn't have one, commitment from some ubuntu-dev person that they have a fix and intend it to be in the next upload is good enough for "Fix Committed". I don't think a fix upstream should qualify an ubuntu-task for "Fix Committed", because it's an indication of the amount of work remaining - "Fix Committed" implies that the fix will arrive with no further development work, just releasing/uploading. Whereas, integrating a new upstream version may require lots of packaging work, or be impossible during a freeze. > If the latter is the majority opinion here, we should discuss having a > new status in malone, e.g. called "FixedUpstream" to easily spot already > fixed bugs. Surely the canonical way to describe that in Malone is with an upstream bugtask? Duplicating the ways in which you can represent that information seems like it could get messy. Max. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature URL: From mgunes at ubuntu.com Wed Apr 15 12:25:06 2009 From: mgunes at ubuntu.com (Murat Gunes) Date: Wed, 15 Apr 2009 15:25:06 +0300 Subject: Status "FixCommited" for ubuntu-tasks In-Reply-To: <49E51D2C.6060804@f2s.com> References: <49E50C53.9060606@warperbbs.de> <49E51D2C.6060804@f2s.com> Message-ID: <1239798306.6943.1310601467@webmail.messagingengine.com> On Wed, 15 Apr 2009 00:33 +0100, "Max Bowsher" wrote: > I don't think a fix upstream should qualify an ubuntu-task for "Fix > Committed", because it's an indication of the amount of work remaining > - "Fix Committed" implies that the fix will arrive with no further > development work, just releasing/uploading. Whereas, integrating a > new upstream version may require lots of packaging work, or be > impossible during a freeze. Agreed; it's best to keep the status as "Triaged". That means the the report has been evaluated and there's nothing more to be done by the reporter or triager, but there's still work to be done by a developer. Another point is that the presence of a fix somewhere in the upstream VCS does not necessarily mean that it will be included in the upstream release, which will in turn end up in Ubuntu. Further changes may occur that can revert or modify the fix, or there may be independent patches (such as in Debian) that interfere with it or revert it. The logic of using "Fix Committed" in accordance with its literal meaning can also be extended to mean that a fix has been committed anywhere in the VCS (such as an independent branch), which again will complicate things. > > If the latter is the majority opinion here, we should discuss having > > a new status in malone, e.g. called "FixedUpstream" to easily spot > > already fixed bugs. > > Surely the canonical way to describe that in Malone is with an > upstream bugtask? > > Duplicating the ways in which you can represent that information seems > like it could get messy. The combination of "Fix Released" upstream and "Triaged" in Ubuntu should be enough to indicate that the fix is set to land in Ubuntu. m. From cjk at teamcharliesangels.com Wed Apr 15 12:31:18 2009 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Wed, 15 Apr 2009 06:31:18 -0600 Subject: Status "FixCommited" for ubuntu-tasks In-Reply-To: <1239798306.6943.1310601467@webmail.messagingengine.com> References: <49E50C53.9060606@warperbbs.de> <49E51D2C.6060804@f2s.com> <1239798306.6943.1310601467@webmail.messagingengine.com> Message-ID: <20090415063118.4228a0f4@teamcharliesangels.com> On Wed, 15 Apr 2009 15:25:06 +0300 "Murat Gunes" wrote: > On Wed, 15 Apr 2009 00:33 +0100, "Max Bowsher" wrote: > > > I don't think a fix upstream should qualify an ubuntu-task for "Fix > > Committed", because it's an indication of the amount of work > > remaining > > - "Fix Committed" implies that the fix will arrive with no further > > development work, just releasing/uploading. Whereas, integrating a > > new upstream version may require lots of packaging work, or be > > impossible during a freeze. > > Agreed; it's best to keep the status as "Triaged". That means the the > report has been evaluated and there's nothing more to be done by the > reporter or triager, but there's still work to be done by a developer. > > Another point is that the presence of a fix somewhere in the upstream > VCS does not necessarily mean that it will be included in the upstream > release, which will in turn end up in Ubuntu. Further changes may > occur that can revert or modify the fix, or there may be independent > patches (such as in Debian) that interfere with it or revert it. The > logic of using "Fix Committed" in accordance with its literal meaning > can also be extended to mean that a fix has been committed anywhere > in the VCS (such as an independent branch), which again will > complicate things. > > > > If the latter is the majority opinion here, we should discuss > > > having a new status in malone, e.g. called "FixedUpstream" to > > > easily spot already fixed bugs. > > > > Surely the canonical way to describe that in Malone is with an > > upstream bugtask? > > > > Duplicating the ways in which you can represent that information > > seems like it could get messy. > > The combination of "Fix Released" upstream and "Triaged" in Ubuntu > should be enough to indicate that the fix is set to land in Ubuntu. > > m. > While I can agree with this logic, what do you do when the upstream report does not update in launchpad? There are many bugs with upstream projects attached, that become fixed upstream but never get a launchpad update. They also become fix-released in launchpad without the upstream bug having been updated beyond "unknown". I, personnally, find I must maintain some type of personal list to know which bugs have actually been worked upstream because of this issue. Not being able to move the Ubuntu bug to fix-committed does double the work I must do to find out if the upstream bug has indeed been fixed. It also increases the workload for the developers if they must go and look upstream for status. Doesn't that defeat the purpose of even having the upstream project? -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From maxb at f2s.com Wed Apr 15 13:01:09 2009 From: maxb at f2s.com (Max Bowsher) Date: Wed, 15 Apr 2009 14:01:09 +0100 Subject: Status "FixCommited" for ubuntu-tasks In-Reply-To: <20090415063118.4228a0f4@teamcharliesangels.com> References: <49E50C53.9060606@warperbbs.de> <49E51D2C.6060804@f2s.com> <1239798306.6943.1310601467@webmail.messagingengine.com> <20090415063118.4228a0f4@teamcharliesangels.com> Message-ID: <49E5DA95.2040606@f2s.com> Charlie Kravetz wrote: > While I can agree with this logic, what do you do when the upstream > report does not update in launchpad? There are many bugs with upstream > projects attached, that become fixed upstream but never get a launchpad > update. They also become fix-released in launchpad without the upstream > bug having been updated beyond "unknown". OK, do we know the reason for that? If the bug watch is configured but not working, we should file bugs on launchpad itself about that. If the bugs don't have upstream bug watches because launchpad doesn't support the relevant upstream tracker type, we should file wishlist bugs on launchpad itself. > I, personnally, find I must > maintain some type of personal list to know which bugs have actually > been worked upstream because of this issue. Not being able to move the > Ubuntu bug to fix-committed does double the work I must do to find out > if the upstream bug has indeed been fixed. It also increases the > workload for the developers if they must go and look upstream for > status. > > Doesn't that defeat the purpose of even having the upstream project? So maybe there needs to be a better way to see at a glance in bug listings whether there is an upstream task with a "Fix Committed" or "Fix Released" status? Max. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature URL: From hggdh2 at gmail.com Wed Apr 15 14:17:44 2009 From: hggdh2 at gmail.com (C de-Avillez) Date: Wed, 15 Apr 2009 09:17:44 -0500 Subject: Status "FixCommited" for ubuntu-tasks In-Reply-To: <49E5DA95.2040606@f2s.com> References: <49E50C53.9060606@warperbbs.de> <49E51D2C.6060804@f2s.com> <1239798306.6943.1310601467@webmail.messagingengine.com> <20090415063118.4228a0f4@teamcharliesangels.com> <49E5DA95.2040606@f2s.com> Message-ID: <20090415091744.063dc48a@xango2> On Wed, 15 Apr 2009 14:01:09 +0100 Max Bowsher wrote: > So maybe there needs to be a better way to see at a glance in bug > listings whether there is an upstream task with a "Fix Committed" or > "Fix Released" status? And we almost go full circle to the starting emails on this thread. This could be bypassed (or solved) easily with a new tag FIXED_UPSTREAM, or something in the same vein. For the argument that a bug fixed upstream can be changed before making it to a distribution point: yes, it can. It can also be changed after the distribution point, so this argument does not give any points either way. Do do cherry-pick upstream fixes, after all. Cheers, -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: not available URL: From cjk at teamcharliesangels.com Wed Apr 15 16:34:09 2009 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Wed, 15 Apr 2009 10:34:09 -0600 Subject: Fw: Status "FixCommited" for ubuntu-tasks Message-ID: <20090415103409.28e4772a@teamcharliesangels.com> Begin forwarded message: Date: Wed, 15 Apr 2009 07:19:46 -0600 From: Charlie Kravetz To: Max Bowsher Subject: Re: Status "FixCommited" for ubuntu-tasks On Wed, 15 Apr 2009 14:01:09 +0100 Max Bowsher wrote: > Charlie Kravetz wrote: > > While I can agree with this logic, what do you do when the upstream > > report does not update in launchpad? There are many bugs with > > upstream projects attached, that become fixed upstream but never > > get a launchpad update. They also become fix-released in launchpad > > without the upstream bug having been updated beyond "unknown". > > OK, do we know the reason for that? If the bug watch is configured but > not working, we should file bugs on launchpad itself about that. If > the bugs don't have upstream bug watches because launchpad doesn't > support the relevant upstream tracker type, we should file wishlist > bugs on launchpad itself. > Yes, we know the reason for that. It is a bug in launchpad, that is known and being worked. That doesn't make if fixed, though. > > I, personnally, find I must > > maintain some type of personal list to know which bugs have actually > > been worked upstream because of this issue. Not being able to move > > the Ubuntu bug to fix-committed does double the work I must do to > > find out if the upstream bug has indeed been fixed. It also > > increases the workload for the developers if they must go and look > > upstream for status. > > > > Doesn't that defeat the purpose of even having the upstream project? > > So maybe there needs to be a better way to see at a glance in bug > listings whether there is an upstream task with a "Fix Committed" or > "Fix Released" status? > > Max. > Gee, what was the reason for this discussion? Oh, yeah, an easier way to determine if the bug might have a "Fix-committed" status. I apologize, Max, I did not intend to send this only to you. Normally I try to reply to the list instead of individuals. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From mgunes at ubuntu.com Wed Apr 15 18:23:20 2009 From: mgunes at ubuntu.com (Murat Gunes) Date: Wed, 15 Apr 2009 21:23:20 +0300 Subject: Status "FixCommited" for ubuntu-tasks In-Reply-To: <20090415063118.4228a0f4@teamcharliesangels.com> References: <49E50C53.9060606@warperbbs.de> <49E51D2C.6060804@f2s.com><1239798306.6943.1310601467@webmail.messagingengine.com> <20090415063118.4228a0f4@teamcharliesangels.com> Message-ID: <1239819800.12944.1310638411@webmail.messagingengine.com> On Wed, 15 Apr 2009 06:31 -0600, "Charlie Kravetz" wrote: > While I can agree with this logic, what do you do when the upstream > report does not update in launchpad? There are many bugs with upstream > projects attached, that become fixed upstream but never get a > launchpad update. They also become fix-released in launchpad without > the upstream bug having been updated beyond "unknown". If the upstream status isn't updating, that should mean one of the following: that Launchpad does not support communicating with that bug tracker, that the location of the upstream bug tracker is not registered in Launchpad, or that there is a bug in Launchpad's remote bug tracker integration. It would be useful to know if there are exceptions to the above, which you can outline with a concrete bug workflow example. > I, personnally, find I must maintain some type of personal list to > know which bugs have actually been worked upstream because of this > issue. Not being able to move the Ubuntu bug to fix-committed does > double the work I must do to find out if the upstream bug has indeed > been fixed. It also increases the workload for the developers if they > must go and look upstream for status. You can perform an advanced search for bugs related to you that are fixed upstream but not in Ubuntu [1]. It's also possible to list such bugs via bughelper / python-launchpad-bugs and the Launchpad API. If/when the request in bug #49752 in Launchpad [2] is implemented, we will have the ability subscribe to an Atom feed of such bugs too. > Doesn't that defeat the purpose of even having the upstream project? I don't think so, but this discussion does echo some points previously raised against the distinction between "Fix Released" and "Fix Committed" [3] in a different context. On Wed, 15 Apr 2009 09:17 -0500, "C de-Avillez" wrote: > For the argument that a bug fixed upstream can be changed before > making it to a distribution point: yes, it can. It can also be changed > after the distribution point, so this argument does not give any > points either way. Do do cherry-pick upstream fixes, after all. I may be misunderstanding you, but for the Ubuntu task, we are mainly interested in the status of the bug before the distribution point(s). If the upstream code changes after a distribution point to cause the bug again, and this actually manifests itself in the current Ubuntu development branch, the Ubuntu task can be reopened. [1] http://tinyurl.com/dz6fr6 [2] https://bugs.launchpad.net/malone/+bug/49752 [3] https://bugs.launchpad.net/malone/+bug/163694 From daradib at gmail.com Wed Apr 15 19:21:24 2009 From: daradib at gmail.com (Dara Adib) Date: Wed, 15 Apr 2009 15:21:24 -0400 Subject: Status "FixCommited" for ubuntu-tasks In-Reply-To: <1239819800.12944.1310638411@webmail.messagingengine.com> References: <49E50C53.9060606@warperbbs.de> <49E51D2C.6060804@f2s.com> <1239798306.6943.1310601467@webmail.messagingengine.com> <20090415063118.4228a0f4@teamcharliesangels.com> <1239819800.12944.1310638411@webmail.messagingengine.com> Message-ID: <9f2cfa420904151221g23127cdbk4e9d9e170ea41fb2@mail.gmail.com> On Wed, Apr 15, 2009 at 2:23 PM, Murat Gunes wrote: > If the upstream status isn't updating, that should mean one of the > following: that Launchpad does not support communicating with that bug > tracker, that the location of the upstream bug tracker is not > registered in Launchpad, or that there is a bug in Launchpad's remote > bug tracker integration. Yes, and there are bug reports open against Launchpad specifically about this. For instance. Bug 258596 refers to a bug report's status in the gna.org (GNU Savannah) bugtracker. For an example of this bug, see Bug 256345. What I don't understand is why it isn't at least possible to manually update the status of an upstream task while still keeping the reference to the upstream bug number/URL. Currently, the only options are to refer to the upstream bug number/URL (bug watch) and keep the status of the bug as "Unknown", or to remove the bug watch and manually update the upstream bug's status. From dinesh372 at gmail.com Sat Apr 25 19:30:21 2009 From: dinesh372 at gmail.com (Dinesh Solanki) Date: Sun, 26 Apr 2009 01:00:21 +0530 Subject: email id Message-ID: dinesh372 at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ara at ubuntu.com Mon Apr 27 15:15:52 2009 From: ara at ubuntu.com (Ara Pulido) Date: Mon, 27 Apr 2009 17:15:52 +0200 Subject: [Ubuntu-bugcontrol] Kernel Bug Day - 20090428 In-Reply-To: <1240615133.32475.31.camel@emiko> References: <1240615133.32475.31.camel@emiko> Message-ID: <1240845352.5509.56.camel@sushirider> Forwarding the announcement to the Ubuntu Bugsquad. Cheers, Ara. On Fri, 2009-04-24 at 16:18 -0700, Leann Ogasawara wrote: > Hi All, > > At a recent Ubuntu kernel team sprint it was decided that the Canonical > Kernel Team would hold kernel bug days twice a month. Each kernel team > member will be responsible for a specific subset of bugs but community > involvement is also highly appreciated. The next scheduled kernel bug > day will be held Tues. April 28, 2009. Please refer to the following > wiki for more information: > > https://wiki.ubuntu.com/KernelTeam/BugDay/20090428 > > Thanks, > Leann > > > _______________________________________________ > Mailing list: https://launchpad.net/~ubuntu-bugcontrol > Post to : ubuntu-bugcontrol at lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol > More help : https://help.launchpad.net/ListHelp From martinmai-ubuntu at web.de Mon Apr 27 19:46:42 2009 From: martinmai-ubuntu at web.de (Martin Mai) Date: Mon, 27 Apr 2009 21:46:42 +0200 Subject: Announcing the Next Ubuntu Hug Day! - 30th April, 2009 Message-ID: <1240861602.3421.8.camel@martin-laptop> Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* new bugs for SRUs and Karmic! Bookmark it, add it to your calendars, turn over those egg-timers! * 30th April, 2009 * http://wiki.ubuntu.com/UbuntuBugDay/20090430 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, Martin Mai [From the BugSquad] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From martinmai-ubuntu at web.de Mon Apr 27 22:37:15 2009 From: martinmai-ubuntu at web.de (Martin Mai) Date: Mon, 27 Apr 2009 22:37:15 -0000 Subject: No subject Message-ID: <1239096119.6205.3.camel@martin-laptop> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-7kR0kgP6EMghGo/mY9V9" --=-7kR0kgP6EMghGo/mY9V9 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* bugs with patches! * #486 New bugs with patches need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 9th of April, 2009 * http://wiki.ubuntu.com/UbuntuBugDay/20090409 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, Martin Mai [From the BugSquad] --=-7kR0kgP6EMghGo/mY9V9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAknbGzQACgkQbi1ABKGxxJiJCgCePJ16HaX/WeRHA3HBxGzW4WDm 28UAn0xXRjy+zO9COVNh/MJFLfzp+fJh =+/pI -----END PGP SIGNATURE----- --=-7kR0kgP6EMghGo/mY9V9-- -------------- next part -------------- Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- ubuntu-devel-announce mailing list ubuntu-devel-announce at lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce From pedro at ubuntu.com Mon Apr 27 22:37:17 2009 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Mon, 27 Apr 2009 22:37:17 -0000 Subject: No subject Message-ID: <1238442865.6824.9.camel@thylacine> Fellow Ubuntu Triagers! This week's HugDay target is *drum roll please* xorg-server and xserver-xorg-video-intel! * 49 New bugs need a hug. * 103 Incomplete bugs need a status check. * 81 Confirmed bugs need a review. * 16 Bugs with patches that need to be reviewed. Bookmark it, add it to your calendars, turn over those egg-timers! * April 02 2009 * https://wiki.ubuntu.com/UbuntuBugDay/20090402 Can't stress it enough: everyone can help! Have some time? Triage boogz! I won't be upset if you get a headstart~ ;) Have a blog? Blog about Hugday! Have some screen space? Open #ubuntu-bugs and keep an eye out for newcomers in need. Have minions? Teach THEM to triage for you! :) Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! Make a difference; we will be in #ubuntu-bugs (FreeNode) all day and night, and will be ready to answer your questions about how to help. If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, pedro. -- ubuntu-devel-announce mailing list ubuntu-devel-announce at lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce From andres.mujica at ubuntu.com Mon Apr 27 23:54:53 2009 From: andres.mujica at ubuntu.com (Andres Mauricio Mujica Zalamea) Date: Mon, 27 Apr 2009 18:54:53 -0500 Subject: bugsquad meetings? Message-ID: <1240876494.17096.36.camel@akita.seaq.intranet> Hi!! i wonder why we don't have formal meetings like all the other teams? shouldn't we have at least a monthly meeting? what do you think? as far as i know the last meeting was held about 3 years ago and Brian proposed one around 2007.... https://wiki.ubuntu.com/BugSquad/Meeting any thoughts? Regards, Andrés Mujica Ubuntu Bugsquad/Bugcontrol -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Tue Apr 28 00:07:42 2009 From: brian at ubuntu.com (Brian Murray) Date: Mon, 27 Apr 2009 17:07:42 -0700 Subject: bugsquad meetings? In-Reply-To: <1240876494.17096.36.camel@akita.seaq.intranet> References: <1240876494.17096.36.camel@akita.seaq.intranet> Message-ID: <20090428000742.GD5902@murraytwins.com> On Mon, Apr 27, 2009 at 06:54:53PM -0500, Andres Mauricio Mujica Zalamea wrote: > Hi!! > > i wonder why we don't have formal meetings like all the other teams? > > shouldn't we have at least a monthly meeting? > > what do you think? > > as far as i know the last meeting was held about 3 years ago and Brian > proposed one around 2007.... > > https://wiki.ubuntu.com/BugSquad/Meeting > > any thoughts? One thing to consider is that the Ubuntu Quality Assurance team, which includes testing and bug teams, holds weekly meetings and these meetings may overlap (in terms of content) a lot with one specific to the Bug Squad. However, if there is sufficient interest I'd be happy to organize one. What kind of topics would you like you to see on the agenda? Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From andres.mujica at ubuntu.com Tue Apr 28 01:51:16 2009 From: andres.mujica at ubuntu.com (Andres Mauricio Mujica Zalamea) Date: Mon, 27 Apr 2009 20:51:16 -0500 Subject: bugsquad meetings? In-Reply-To: <20090428000742.GD5902@murraytwins.com> References: <1240876494.17096.36.camel@akita.seaq.intranet> <20090428000742.GD5902@murraytwins.com> Message-ID: <1240883476.17096.54.camel@akita.seaq.intranet> > One thing to consider is that the Ubuntu Quality Assurance team, which > includes testing and bug teams, holds weekly meetings and these meetings > may overlap (in terms of content) a lot with one specific to the Bug > Squad. > right. > However, if there is sufficient interest I'd be happy to organize one. > What kind of topics would you like you to see on the agenda? > - Newly bug trends identified by triagers - Bugs that need attention/help/mentoring - Upstream relationships (what happened with the bugtracker plugins developed by LP?/Relationship with different distros affected by same upstream bugs/What do the devs need from us?) - Tasks to do for the team - UDS participation? - probably some more... > Thanks, Andrés Mujica Ubuntu Bugsquad/Bugcontrol -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Tue Apr 28 16:28:14 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 28 Apr 2009 09:28:14 -0700 Subject: Bugs since release Message-ID: <20090428162814.GE5902@murraytwins.com> I've made a report[1] that lists New and Confirmed bug tasks opened since 2009-04-23, the day Jaunty came out. My thought was that the report would be helpful for finding bugs regarding the final version of Jaunty and identifying SRU worthy bug reports. [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From wolfger at gmail.com Tue Apr 28 16:58:21 2009 From: wolfger at gmail.com (Wolfger) Date: Tue, 28 Apr 2009 12:58:21 -0400 Subject: Bugs since release In-Reply-To: <20090428162814.GE5902@murraytwins.com> References: <20090428162814.GE5902@murraytwins.com> Message-ID: <3b00b3330904280958g54cc9edeqb4917c215cde57f2@mail.gmail.com> What's "Gravity"? Sorry if I'm just out of the loop... On Tue, Apr 28, 2009 at 12:28 PM, Brian Murray wrote: > I've made a report[1] that lists New and Confirmed bug tasks opened > since 2009-04-23, the day Jaunty came out.  My thought was that the > report would be helpful for finding bugs regarding the final version of > Jaunty and identifying SRU worthy bug reports. > > [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html > > -- > Brian Murray                                                 @ubuntu.com > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkn3Lp4ACgkQDTAwc5ER+zWKHQCgj5xVxiKDYI218B7teBpJPymr > ZPIAn1qQdoaPwhdKar6cS5G3Xg5zEIi/ > =a9n6 > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -- Wolfger http://wolfger.wordpress.com/ http://twitter.com/wolfger http://identi.ca/wolfger The world is a mess, and I just... need to rule it. From macoafi at gmail.com Tue Apr 28 17:09:34 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Tue, 28 Apr 2009 13:09:34 -0400 Subject: Bugs since release In-Reply-To: <3b00b3330904280958g54cc9edeqb4917c215cde57f2@mail.gmail.com> References: <20090428162814.GE5902@murraytwins.com> <3b00b3330904280958g54cc9edeqb4917c215cde57f2@mail.gmail.com> Message-ID: <200904281309.38966.macoafi@gmail.com> On Martes 28 Abril 2009 12:58:21 PM Wolfger wrote: > What's "Gravity"? Sorry if I'm just out of the loop... It's a measure of how "grave" it is (I guess? sounds rather morbid put that way) based on things like # of subscribers, # of dups, and # of "me too!" marks. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From brian at ubuntu.com Tue Apr 28 17:11:48 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 28 Apr 2009 10:11:48 -0700 Subject: Bugs since release In-Reply-To: <3b00b3330904280958g54cc9edeqb4917c215cde57f2@mail.gmail.com> References: <20090428162814.GE5902@murraytwins.com> <3b00b3330904280958g54cc9edeqb4917c215cde57f2@mail.gmail.com> Message-ID: <20090428171148.GG5902@murraytwins.com> On Tue, Apr 28, 2009 at 12:58:21PM -0400, Wolfger wrote: > What's "Gravity"? Sorry if I'm just out of the loop... The bug gravity is a calculation of the bug's weight based on whom it was reported by, the tags that a bug has, the quantity of duplicates, subscribers and users affected. There is actually a legend at the bottom of the report that indicates how many points each item is worth. In theory the bugs with a higher gravity may be worth looking at first. If you have any other ideas about how the gravity could be calculated please let me know. Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From macoafi at gmail.com Tue Apr 28 17:13:02 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Tue, 28 Apr 2009 13:13:02 -0400 Subject: Bugs since release In-Reply-To: <20090428162814.GE5902@murraytwins.com> References: <20090428162814.GE5902@murraytwins.com> Message-ID: <200904281313.03279.macoafi@gmail.com> On Martes 28 Abril 2009 12:28:14 PM Brian Murray wrote: > I've made a report[1] that lists New and Confirmed bug tasks opened > since 2009-04-23, the day Jaunty came out. My thought was that the > report would be helpful for finding bugs regarding the final version of > Jaunty and identifying SRU worthy bug reports. > > [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html Something's wrong. It's showing Bug 217504 in there, but the only change to that bug since Jaunty released was the addition of a subscriber (see: https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/217504/+activity ) -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From brian at ubuntu.com Tue Apr 28 17:20:17 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 28 Apr 2009 10:20:17 -0700 Subject: Bugs since release In-Reply-To: <200904281313.03279.macoafi@gmail.com> References: <20090428162814.GE5902@murraytwins.com> <200904281313.03279.macoafi@gmail.com> Message-ID: <20090428172017.GH5902@murraytwins.com> On Tue, Apr 28, 2009 at 01:13:02PM -0400, Mackenzie Morgan wrote: > On Martes 28 Abril 2009 12:28:14 PM Brian Murray wrote: > > I've made a report[1] that lists New and Confirmed bug tasks opened > > since 2009-04-23, the day Jaunty came out. My thought was that the > > report would be helpful for finding bugs regarding the final version of > > Jaunty and identifying SRU worthy bug reports. > > > > [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html > > Something's wrong. It's showing Bug 217504 in there, but the only change to > that bug since Jaunty released was the addition of a subscriber (see: > https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/217504/+activity ) Actually the 'linux' task was opened for this bug report on the 27th of April which is after the 23rd and makes it appear in the report. I found this by expanding each bug task to determine which one was created post release. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From macoafi at gmail.com Tue Apr 28 17:38:50 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Tue, 28 Apr 2009 13:38:50 -0400 Subject: Bugs since release In-Reply-To: <20090428172017.GH5902@murraytwins.com> References: <20090428162814.GE5902@murraytwins.com> <200904281313.03279.macoafi@gmail.com> <20090428172017.GH5902@murraytwins.com> Message-ID: <200904281338.55408.macoafi@gmail.com> On Martes 28 Abril 2009 1:20:17 PM Brian Murray wrote: > On Tue, Apr 28, 2009 at 01:13:02PM -0400, Mackenzie Morgan wrote: > > On Martes 28 Abril 2009 12:28:14 PM Brian Murray wrote: > > > I've made a report[1] that lists New and Confirmed bug tasks opened > > > since 2009-04-23, the day Jaunty came out. My thought was that the > > > report would be helpful for finding bugs regarding the final version of > > > Jaunty and identifying SRU worthy bug reports. > > > > > > [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html > > > > Something's wrong. It's showing Bug 217504 in there, but the only change to > > that bug since Jaunty released was the addition of a subscriber (see: > > https://bugs.launchpad.net/ubuntu/+source/acpi- support/+bug/217504/+activity ) > > Actually the 'linux' task was opened for this bug report on the 27th of > April which is after the 23rd and makes it appear in the report. I > found this by expanding each bug task to determine which one was created > post release. According to the Activity Log, the linux task existed since April of 2008. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From wolfger at gmail.com Tue Apr 28 17:41:56 2009 From: wolfger at gmail.com (Wolfger) Date: Tue, 28 Apr 2009 13:41:56 -0400 Subject: Bugs since release In-Reply-To: <20090428162814.GE5902@murraytwins.com> References: <20090428162814.GE5902@murraytwins.com> Message-ID: <3b00b3330904281041n5bc791b4r6ea7a69d532e61ed@mail.gmail.com> Would be nice for this purpose if bugs with [intrepid], [karmic], etc were not displayed. On Tue, Apr 28, 2009 at 12:28 PM, Brian Murray wrote: > I've made a report[1] that lists New and Confirmed bug tasks opened > since 2009-04-23, the day Jaunty came out.  My thought was that the > report would be helpful for finding bugs regarding the final version of > Jaunty and identifying SRU worthy bug reports. > > [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html > > -- > Brian Murray                                                 @ubuntu.com > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAkn3Lp4ACgkQDTAwc5ER+zWKHQCgj5xVxiKDYI218B7teBpJPymr > ZPIAn1qQdoaPwhdKar6cS5G3Xg5zEIi/ > =a9n6 > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -- Wolfger http://wolfger.wordpress.com/ http://twitter.com/wolfger http://identi.ca/wolfger The world is a mess, and I just... need to rule it. From brian at ubuntu.com Tue Apr 28 17:47:56 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 28 Apr 2009 10:47:56 -0700 Subject: Bugs since release In-Reply-To: <200904281338.55408.macoafi@gmail.com> References: <20090428162814.GE5902@murraytwins.com> <200904281313.03279.macoafi@gmail.com> <20090428172017.GH5902@murraytwins.com> <200904281338.55408.macoafi@gmail.com> Message-ID: <20090428174756.GI5902@murraytwins.com> On Tue, Apr 28, 2009 at 01:38:50PM -0400, Mackenzie Morgan wrote: > On Martes 28 Abril 2009 1:20:17 PM Brian Murray wrote: > > On Tue, Apr 28, 2009 at 01:13:02PM -0400, Mackenzie Morgan wrote: > > > On Martes 28 Abril 2009 12:28:14 PM Brian Murray wrote: > > > > I've made a report[1] that lists New and Confirmed bug tasks opened > > > > since 2009-04-23, the day Jaunty came out. My thought was that the > > > > report would be helpful for finding bugs regarding the final version of > > > > Jaunty and identifying SRU worthy bug reports. > > > > > > > > [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html > > > > > > Something's wrong. It's showing Bug 217504 in there, but the only change > to > > > that bug since Jaunty released was the addition of a subscriber (see: > > > https://bugs.launchpad.net/ubuntu/+source/acpi- > support/+bug/217504/+activity ) > > > > Actually the 'linux' task was opened for this bug report on the 27th of > > April which is after the 23rd and makes it appear in the report. I > > found this by expanding each bug task to determine which one was created > > post release. > > According to the Activity Log, the linux task existed since April of 2008. I don't believe the Activity Log is authoritative. You could look at the text representation of the bug report[1] to get a definitive answer. The important bit is: task: linux (Ubuntu) status: New date-created: Mon, 27 Apr 2009 11:02:55 -0000 [1] https://bugs.edge.launchpad.net/ubuntu/+source/acpi-support/+bug/217504/+text -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From a.starr.b at gmail.com Tue Apr 28 18:15:16 2009 From: a.starr.b at gmail.com (Andrew) Date: Tue, 28 Apr 2009 14:15:16 -0400 Subject: Bugs since release In-Reply-To: <20090428171148.GG5902@murraytwins.com> References: <20090428162814.GE5902@murraytwins.com> <3b00b3330904280958g54cc9edeqb4917c215cde57f2@mail.gmail.com> <20090428171148.GG5902@murraytwins.com> Message-ID: On Tue, Apr 28, 2009 at 1:11 PM, Brian Murray wrote: > On Tue, Apr 28, 2009 at 12:58:21PM -0400, Wolfger wrote: >> What's "Gravity"? Sorry if I'm just out of the loop... > > The bug gravity is a calculation of the bug's weight based on whom it > was reported by, the tags that a bug has, the quantity of duplicates, > subscribers and users affected.  There is actually a legend at the > bottom of the report that indicates how many points each item is worth. > > In theory the bugs with a higher gravity may be worth looking at first. > If you have any other ideas about how the gravity could be calculated > please let me know. You might want to consider filtering out bugs with sync or merge in the title. As bugs reported by developers (by way of bug-control membership) have a higher gravity, syncs are being shown as some of the "gravest" bugs in the report. Yet, they are not very interesting from a triaging/bugsquad stand point. - Andrew Starr-Bochicchio Ubuntu Contributing Developer From brian at ubuntu.com Tue Apr 28 18:20:03 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 28 Apr 2009 11:20:03 -0700 Subject: Bugs since release In-Reply-To: References: <20090428162814.GE5902@murraytwins.com> <3b00b3330904280958g54cc9edeqb4917c215cde57f2@mail.gmail.com> <20090428171148.GG5902@murraytwins.com> Message-ID: <20090428182003.GJ5902@murraytwins.com> On Tue, Apr 28, 2009 at 02:15:16PM -0400, Andrew wrote: > On Tue, Apr 28, 2009 at 1:11 PM, Brian Murray wrote: > > On Tue, Apr 28, 2009 at 12:58:21PM -0400, Wolfger wrote: > >> What's "Gravity"? Sorry if I'm just out of the loop... > > > > The bug gravity is a calculation of the bug's weight based on whom it > > was reported by, the tags that a bug has, the quantity of duplicates, > > subscribers and users affected.  There is actually a legend at the > > bottom of the report that indicates how many points each item is worth. > > > > In theory the bugs with a higher gravity may be worth looking at first. > > If you have any other ideas about how the gravity could be calculated > > please let me know. > > You might want to consider filtering out bugs with sync or merge in > the title. As bugs reported by developers (by way of bug-control > membership) have a higher gravity, syncs are being shown as some of > the "gravest" bugs in the report. Yet, they are not very interesting > from a triaging/bugsquad stand point. Is there a particular reason they are in the New or Confirmed status? -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From pochu at ubuntu.com Tue Apr 28 18:37:56 2009 From: pochu at ubuntu.com (Emilio Pozuelo Monfort) Date: Tue, 28 Apr 2009 20:37:56 +0200 Subject: Bugs since release In-Reply-To: <20090428182003.GJ5902@murraytwins.com> References: <20090428162814.GE5902@murraytwins.com> <3b00b3330904280958g54cc9edeqb4917c215cde57f2@mail.gmail.com> <20090428171148.GG5902@murraytwins.com> <20090428182003.GJ5902@murraytwins.com> Message-ID: <49F74D04.8030700@ubuntu.com> Brian Murray wrote: > Is there a particular reason they are in the New or Confirmed status? Non-developers report them with New status, and developers change them to Confirmed. It would make sense to use Triaged rather than Confirmed, but that should be discussed in ubuntu-devel@ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature URL: From macoafi at gmail.com Tue Apr 28 18:48:44 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Tue, 28 Apr 2009 14:48:44 -0400 Subject: Bugs since release In-Reply-To: <20090428182003.GJ5902@murraytwins.com> References: <20090428162814.GE5902@murraytwins.com> <20090428182003.GJ5902@murraytwins.com> Message-ID: <200904281448.48819.macoafi@gmail.com> On Martes 28 Abril 2009 2:20:03 PM Brian Murray wrote: > On Tue, Apr 28, 2009 at 02:15:16PM -0400, Andrew wrote: > > You might want to consider filtering out bugs with sync or merge in > > the title. As bugs reported by developers (by way of bug-control > > membership) have a higher gravity, syncs are being shown as some of > > the "gravest" bugs in the report. Yet, they are not very interesting > > from a triaging/bugsquad stand point. > > Is there a particular reason they are in the New or Confirmed status? Laziness...or people having better things to do than twiddle status to and fro. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From brunogirin at gmail.com Tue Apr 28 22:15:47 2009 From: brunogirin at gmail.com (Bruno Girin) Date: Tue, 28 Apr 2009 23:15:47 +0100 Subject: Bugs since release In-Reply-To: <20090428162814.GE5902@murraytwins.com> References: <20090428162814.GE5902@murraytwins.com> Message-ID: <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> 2009/4/28 Brian Murray : > I've made a report[1] that lists New and Confirmed bug tasks opened > since 2009-04-23, the day Jaunty came out.  My thought was that the > report would be helpful for finding bugs regarding the final version of > Jaunty and identifying SRU worthy bug reports. > > [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html Brian, Sorry to sound like a n00b but what does SRU stand for? For some reason, the definitions given by Google (Scottish Rugby Union or Sulphur Recovery Unit) don't seem appropriate. Other than that, thanks for the list, it shows we have quite a bit of triaging to do so I'll try to do my bit. Bruno Girin From briancurtis.wx at gmail.com Tue Apr 28 22:19:33 2009 From: briancurtis.wx at gmail.com (Brian Curtis) Date: Tue, 28 Apr 2009 18:19:33 -0400 Subject: Bugs since release In-Reply-To: <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> References: <20090428162814.GE5902@murraytwins.com> <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> Message-ID: SRU = Stable Release Updates/Upgrades (i believe) ~Brian Research is what I'm doing when I don't know what I'm doing. --Wernher Von Braun "The second law of thermodynamics: If you think things are in a mess now, JUST WAIT!!" On Tue, Apr 28, 2009 at 6:15 PM, Bruno Girin wrote: > 2009/4/28 Brian Murray : >> I've made a report[1] that lists New and Confirmed bug tasks opened >> since 2009-04-23, the day Jaunty came out.  My thought was that the >> report would be helpful for finding bugs regarding the final version of >> Jaunty and identifying SRU worthy bug reports. >> >> [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html > > Brian, > > Sorry to sound like a n00b but what does SRU stand for? For some > reason, the definitions given by Google (Scottish Rugby Union or > Sulphur Recovery Unit) don't seem appropriate. > > Other than that, thanks for the list, it shows we have quite a bit of > triaging to do so I'll try to do my bit. > > Bruno Girin > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > From robert.l.toscano at gmail.com Tue Apr 28 22:19:25 2009 From: robert.l.toscano at gmail.com (Robert Toscano) Date: Wed, 29 Apr 2009 00:19:25 +0200 Subject: Bugs since release In-Reply-To: <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> References: <20090428162814.GE5902@murraytwins.com> <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> Message-ID: <3bd381ba0904281519s55d97264m2f062dda1b6381b0@mail.gmail.com> Stable Release Update On Wed, Apr 29, 2009 at 12:15 AM, Bruno Girin wrote: > 2009/4/28 Brian Murray : > > I've made a report[1] that lists New and Confirmed bug tasks opened > > since 2009-04-23, the day Jaunty came out. My thought was that the > > report would be helpful for finding bugs regarding the final version of > > Jaunty and identifying SRU worthy bug reports. > > > > [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html > > Brian, > > Sorry to sound like a n00b but what does SRU stand for? For some > reason, the definitions given by Google (Scottish Rugby Union or > Sulphur Recovery Unit) don't seem appropriate. > > Other than that, thanks for the list, it shows we have quite a bit of > triaging to do so I'll try to do my bit. > > Bruno Girin > > -- > 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: From pochu at ubuntu.com Tue Apr 28 22:20:52 2009 From: pochu at ubuntu.com (Emilio Pozuelo Monfort) Date: Wed, 29 Apr 2009 00:20:52 +0200 Subject: Bugs since release In-Reply-To: <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> References: <20090428162814.GE5902@murraytwins.com> <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> Message-ID: <49F78144.7010505@ubuntu.com> Bruno Girin wrote: > Sorry to sound like a n00b but what does SRU stand for? For some > reason, the definitions given by Google (Scottish Rugby Union or > Sulphur Recovery Unit) don't seem appropriate. It means Stable Release Update. https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/glossary may be helpful to you. Best regards, Emilio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature URL: From briancurtis.wx at gmail.com Tue Apr 28 22:26:55 2009 From: briancurtis.wx at gmail.com (Brian Curtis) Date: Tue, 28 Apr 2009 18:26:55 -0400 Subject: bugsquad meetings? In-Reply-To: <1240883476.17096.54.camel@akita.seaq.intranet> References: <1240876494.17096.36.camel@akita.seaq.intranet> <20090428000742.GD5902@murraytwins.com> <1240883476.17096.54.camel@akita.seaq.intranet> Message-ID: On Mon, Apr 27, 2009 at 9:51 PM, Andres Mauricio Mujica Zalamea wrote: > > One thing to consider is that the Ubuntu Quality Assurance team, which > includes testing and bug teams, holds weekly meetings and these meetings > may overlap (in terms of content) a lot with one specific to the Bug > Squad. > > > right. > > However, if there is sufficient interest I'd be happy to organize one. > What kind of topics would you like you to see on the agenda? > > > - Newly bug trends identified by triagers > - Bugs that need attention/help/mentoring > - Upstream relationships (what happened with the bugtracker plugins > developed by LP?/Relationship with different distros affected by same > upstream bugs/What do the devs need from us?) > - Tasks to do for the team > - UDS participation? > - probably some more... -Open Discussions -LP Improvements for triagers -LoCo Bug Jams -New bug-stuff to look forward to > > > Thanks, > > Andrés Mujica > Ubuntu Bugsquad/Bugcontrol > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > From macoafi at gmail.com Wed Apr 29 00:07:42 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Tue, 28 Apr 2009 20:07:42 -0400 Subject: Bugs since release In-Reply-To: <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> References: <20090428162814.GE5902@murraytwins.com> <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> Message-ID: <200904282007.47801.macoafi@gmail.com> On Martes 28 Abril 2009 6:15:47 PM Bruno Girin wrote: > Brian, > > Sorry to sound like a n00b but what does SRU stand for? For some > reason, the definitions given by Google (Scottish Rugby Union or > Sulphur Recovery Unit) don't seem appropriate. Stable Release Update. Fill out forms explaining why a certain update should happen in a stable release and how unlikely it is that it'll cause more breakage, then release team (I think?) reads it and decides what to do. -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From cjsmo at cableone.net Wed Apr 29 00:16:05 2009 From: cjsmo at cableone.net (Charlie Smotherman) Date: Tue, 28 Apr 2009 19:16:05 -0500 Subject: Bugs since release In-Reply-To: <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> References: <20090428162814.GE5902@murraytwins.com> <6cad31400904281515m41809de1v3cd55b5d9080f0fb@mail.gmail.com> Message-ID: <1240964165.3913.6.camel@charliej-desktop> On Tue, 2009-04-28 at 23:15 +0100, Bruno Girin wrote: > 2009/4/28 Brian Murray : > > I've made a report[1] that lists New and Confirmed bug tasks opened > > since 2009-04-23, the day Jaunty came out. My thought was that the > > report would be helpful for finding bugs regarding the final version of > > Jaunty and identifying SRU worthy bug reports. > > > > [1] http://qa.ubuntu.com/reports/bugnumbers/bugs-since-jaunty.html > > Brian, > > Sorry to sound like a n00b but what does SRU stand for? For some > reason, the definitions given by Google (Scottish Rugby Union or > Sulphur Recovery Unit) don't seem appropriate. > > Other than that, thanks for the list, it shows we have quite a bit of > triaging to do so I'll try to do my bit. > SRU == Stable Release Updates https://wiki.ubuntu.com/StableReleaseUpdates -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From brian at ubuntu.com Wed Apr 29 03:12:07 2009 From: brian at ubuntu.com (Brian Murray) Date: Tue, 28 Apr 2009 20:12:07 -0700 Subject: Bugs since release In-Reply-To: <200904281448.48819.macoafi@gmail.com> References: <20090428162814.GE5902@murraytwins.com> <20090428182003.GJ5902@murraytwins.com> <200904281448.48819.macoafi@gmail.com> Message-ID: <20090429031207.GQ5902@murraytwins.com> On Tue, Apr 28, 2009 at 02:48:44PM -0400, Mackenzie Morgan wrote: > On Martes 28 Abril 2009 2:20:03 PM Brian Murray wrote: > > On Tue, Apr 28, 2009 at 02:15:16PM -0400, Andrew wrote: > > > You might want to consider filtering out bugs with sync or merge in > > > the title. As bugs reported by developers (by way of bug-control > > > membership) have a higher gravity, syncs are being shown as some of > > > the "gravest" bugs in the report. Yet, they are not very interesting > > > from a triaging/bugsquad stand point. > > > > Is there a particular reason they are in the New or Confirmed status? > > Laziness...or people having better things to do than twiddle status to and > fro. Considering that Ubuntu is a large project with a lot of bugs and volunteers triaging those bugs, its important that a bug task's status get twiddled to one that accurately reflects the state of the bug. This ensures that the bug will show up on appropriate lists and multiple people won't misspend time on it. -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From macoafi at gmail.com Wed Apr 29 04:56:27 2009 From: macoafi at gmail.com (Mackenzie Morgan) Date: Wed, 29 Apr 2009 00:56:27 -0400 Subject: Bugs since release In-Reply-To: <20090429031207.GQ5902@murraytwins.com> References: <20090428162814.GE5902@murraytwins.com> <200904281448.48819.macoafi@gmail.com> <20090429031207.GQ5902@murraytwins.com> Message-ID: <200904290056.31325.macoafi@gmail.com> On Martes 28 Abril 2009 11:12:07 PM Brian Murray wrote: > On Tue, Apr 28, 2009 at 02:48:44PM -0400, Mackenzie Morgan wrote: > > On Martes 28 Abril 2009 2:20:03 PM Brian Murray wrote: > > > On Tue, Apr 28, 2009 at 02:15:16PM -0400, Andrew wrote: > > > > You might want to consider filtering out bugs with sync or merge in > > > > the title. As bugs reported by developers (by way of bug-control > > > > membership) have a higher gravity, syncs are being shown as some of > > > > the "gravest" bugs in the report. Yet, they are not very interesting > > > > from a triaging/bugsquad stand point. > > > > > > Is there a particular reason they are in the New or Confirmed status? > > > > Laziness...or people having better things to do than twiddle status to and > > fro. > > Considering that Ubuntu is a large project with a lot of bugs and > volunteers triaging those bugs, its important that a bug task's status > get twiddled to one that accurately reflects the state of the bug. This > ensures that the bug will show up on appropriate lists and multiple > people won't misspend time on it. Does it matter as much if the person is also self-assigning at the same time? -- Mackenzie Morgan http://ubuntulinuxtipstricks.blogspot.com apt-get moo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From steven at too1337.com Wed Apr 29 05:50:21 2009 From: steven at too1337.com (Steven Susbauer) Date: Wed, 29 Apr 2009 00:50:21 -0500 Subject: Triage "Updated Version" bugs? Message-ID: <49F7EA9D.70800@too1337.com> Good evening/morning, I would ask in IRC but it seems everyone AFK at the moment. :) I am new to the BugSquad and still learning the triage process. I am curious how bugs asking for an updated package are handled, as they are not referenced in any of the guides I have found. An example I would currently be working on is at https://bugs.launchpad.net/ubuntu/+source/opencascade/+bug/369045 - Obviously something the description could be brightened up, but how would it be marked farther and commented? Thanks for the help, -Steve From paul at climbing.nl Wed Apr 29 07:49:11 2009 From: paul at climbing.nl (Paul Gevers) Date: Wed, 29 Apr 2009 09:49:11 +0200 Subject: Triage "Updated Version" bugs? In-Reply-To: <49F7EA9D.70800@too1337.com> References: <49F7EA9D.70800@too1337.com> Message-ID: <49F80677.2020701@climbing.nl> > I would ask in IRC but it seems everyone AFK at the moment. :) I am new > to the BugSquad and still learning the triage process. I am curious how > bugs asking for an updated package are handled, as they are not > referenced in any of the guides I have found. An example I would > currently be working on is at > https://bugs.launchpad.net/ubuntu/+source/opencascade/+bug/369045 - > Obviously something the description could be brightened up, but how > would it be marked farther and commented? One of the things to do is look where Debian stands in such a case. Here Debian has a newer version, so you could look into the differences between the Ubuntu and Debian version and convert this bug into a merge request of sync request depending on what you find. You could in this case consult [1]. Paul [1] https://wiki.ubuntu.com/UbuntuDevelopment/Merging -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature URL: From jw+debian at jameswestby.net Wed Apr 29 09:37:03 2009 From: jw+debian at jameswestby.net (James Westby) Date: Wed, 29 Apr 2009 10:37:03 +0100 Subject: Triage "Updated Version" bugs? In-Reply-To: <49F7EA9D.70800@too1337.com> References: <49F7EA9D.70800@too1337.com> Message-ID: <1240997823.4768.34.camel@flash> On Wed, 2009-04-29 at 00:50 -0500, Steven Susbauer wrote: > Good evening/morning, > > I would ask in IRC but it seems everyone AFK at the moment. :) I am new > to the BugSquad and still learning the triage process. I am curious how > bugs asking for an updated package are handled, as they are not > referenced in any of the guides I have found. An example I would > currently be working on is at > https://bugs.launchpad.net/ubuntu/+source/opencascade/+bug/369045 - > Obviously something the description could be brightened up, but how > would it be marked farther and commented? Generally these are "Wishlist" bugs, with a "Confirmed" status if the version being requested is not in any Ubuntu release, and actually exists. As Paul said looking at Debian as well can be useful. If you do that but aren't comfortable taking that forward to a sync request then you can just mention your findings in the bug report. If there is a Debian bug requesting the upgrade then you can add a bug task for that as well. Thanks, James From brian at ubuntu.com Wed Apr 29 16:18:47 2009 From: brian at ubuntu.com (Brian Murray) Date: Wed, 29 Apr 2009 09:18:47 -0700 Subject: bugsquad meetings? In-Reply-To: References: <1240876494.17096.36.camel@akita.seaq.intranet> <20090428000742.GD5902@murraytwins.com> <1240883476.17096.54.camel@akita.seaq.intranet> Message-ID: <20090429161847.GS5902@murraytwins.com> On Tue, Apr 28, 2009 at 06:26:55PM -0400, Brian Curtis wrote: > On Mon, Apr 27, 2009 at 9:51 PM, Andres Mauricio Mujica Zalamea > wrote: > > > > One thing to consider is that the Ubuntu Quality Assurance team, which > > includes testing and bug teams, holds weekly meetings and these meetings > > may overlap (in terms of content) a lot with one specific to the Bug > > Squad. > > > > > > right. > > > > However, if there is sufficient interest I'd be happy to organize one. > > What kind of topics would you like you to see on the agenda? > > > > > > - Newly bug trends identified by triagers > > - Bugs that need attention/help/mentoring > > - Upstream relationships (what happened with the bugtracker plugins > > developed by LP?/Relationship with different distros affected by same > > upstream bugs/What do the devs need from us?) > > - Tasks to do for the team > > - UDS participation? > > - probably some more... > -Open Discussions > -LP Improvements for triagers > -LoCo Bug Jams > -New bug-stuff to look forward to Well, it certainly sounds like there is a fair bit of stuff to discuss then. I'm generally available from 1500 to 2359 UTC during weekdays but could be available other times too. When should we try and have the meeting then? Thanks, -- Brian Murray @ubuntu.com -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From mrooney at gmail.com Wed Apr 29 17:44:01 2009 From: mrooney at gmail.com (Mike Rooney) Date: Wed, 29 Apr 2009 10:44:01 -0700 Subject: Bugs since release In-Reply-To: <200904290056.31325.macoafi@gmail.com> References: <20090428162814.GE5902@murraytwins.com> <200904281448.48819.macoafi@gmail.com> <20090429031207.GQ5902@murraytwins.com> <200904290056.31325.macoafi@gmail.com> Message-ID: <4f4806ee0904291044p6c0787bdtb72484624a29bfd7@mail.gmail.com> On Tue, Apr 28, 2009 at 9:56 PM, Mackenzie Morgan wrote: > Does it matter as much if the person is also self-assigning at the same time? I would say so. If you are already manipulating the bug why not just do it properly? Like Brian said one person's laziness can cause much more work for a bunch of other people who can't find the right bug. -- Michael Rooney mrooney at gmail.com