Re: Restoring the status of automatically expired bugs
On Tue, 2007-10-09 at 15:57 -0700, Jordan Mantha wrote: > Just to be clear as I'm not quite sure, are *all* Janitor-closed bugs > going to be reverted or just the ones that were closed in error? > > -Jordan Mantha All that are still Invalid, regardless of if error will be reverted. About 100 of the 2,862 bugs have been updated by users since the expiration. They will be unchanged. > On 10/9/07, Matthew Revell <[EMAIL PROTECTED]> wrote: > > Shortly after we released Launchpad 1.1.9 (on 21 September), > > Launchpad's housekeeping system - the Launchpad Janitor - expired > > 2,862 Incomplete bugs. We estimate that around 900 of these bugs > > should not have been expired. > > > > We're sorry for the confusion and inconvenience that this caused. We > > will restore the "Incomplete" status of all bugs that the Launchpad > > Janitor expired. This process will begin at 12.00 UTC on 10th October. > > > > > > What went wrong > > === > > > > The feedback that you've given us has highlighted three flaws in the > > bug expiration process we used: > > > > 1. We expired duplicate bugs: this went against our policy that > > duplicate bugs should not be modified, nor should they generate email. > > > > 2. We expired bugs that were still being triaged: recent comment > > activity showed that these bugs had not been abandoned but our process > > didn't take account of that. > > > > 3. We expired bugs that were confirmed or fixed in another location: > > once a bug is confirmed in one location, it should not be incomplete > > in another. Bug contacts are responsible for managing a bug's many > > statuses once it is confirmed in one location. > > > > > > Understanding Launchpad's bug statuses > > == > > > > While we were reviewing these issues, we discovered that many people > > are using the Incomplete status to mean something other than "this > > report cannot be confirmed to be a bug, additional information is > > needed". The comments and activity of roughly 20% of the Incomplete > > reports suggest that Confirmed or Wont Fix would have been a more > > appropriate status. > > > > In light of this, we've written a blog post looking at how and when to > > use the various bug statuses that Launchpad offers: > > > > http://news.launchpad.net/general/of-bugs-and-statuses > > > > > > How we're going to fix this > > === > > > > Now that we know that many people have used the Incomplete status to > > mean a number of different things, we are going to restore the > > Incomplete status of all bugs that the Launchpad Janitor changed. > > > > During this process: > > > > * Comments left by the Janitor will be removed from those bugs that > >have their status restored. > > * The updates will not generate email. > > * We won't alter the status of any bug if its status has been > >manually altered since the expiration. > > > > We still believe that our original intention -- to remove abandoned > > bugs from bug queues -- will be a useful enhancement to Launchpad. > > We're going to fix the three flaws in the expiration process and then > > email selected projects' bug contacts with a list of the bugs that we > > have identified as abandoned. With your feedback, we will refine this > > process. We will only resume the expiry process when the Launchpad > > user community is happy with the way we identify abandoned bugs. > > > > We will also update the Launchpad documentation to ensure it explains > > the bug statuses more thoroughly and we will make that documentation > > easier to find. > > > > Thank you for your ongoing feedback and for helping us to refine this > > process. > > > > -- > > Matthew Revell > > launchpad.net > > > > mrevell in #launchpad on Freenode > > > > -- > > Ubuntu-motu mailing list > > Ubuntu-motu@lists.ubuntu.com > > Modify settings or unsubscribe at: > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu > > > > > > > -- > "That's all very well in practice, but will it ever work in theory?" -- G. > Hill > "A tidy laboratory means a lazy chemist." -- Jöns Jacob Berzelius -- __Curtis C. Hovey_ http://launchpad.net/ signature.asc Description: This is a digitally signed message part -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Mozilla ligature bug with Dejavu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Denis Jacquerye wrote: > Hi, > > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/37828/comments/57 > is a patch to "fix" the ligature bug in Mozilla, as this is only fixed > in the next version this patch actually removes the ligatures from the > Dejavu fonts. > > There's also a serious bug with FreeType on Gutsy the breaks U+00E5 å > at some sizes. Do you want a patch so DejaVu Sans doesn't trigger the > bug? Yes, if we can still get it into gutsy, that should be better. Thanks Arne -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHDE6Wbp/QbmhdHowRAmKwAKDxCTJeazJ/blom6Krs3UZFkKUrtwCffo4C lIyoKsgR43s7kTsZJalC6Yw= =IHF0 -END PGP SIGNATURE- -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Restoring the status of automatically expired bugs
On Tuesday 09 October 2007 18:24, Matthew Revell wrote: > Shortly after we released Launchpad 1.1.9 (on 21 September), > Launchpad's housekeeping system - the Launchpad Janitor - expired > 2,862 Incomplete bugs. We estimate that around 900 of these bugs > should not have been expired. > > We're sorry for the confusion and inconvenience that this caused. We > will restore the "Incomplete" status of all bugs that the Launchpad > Janitor expired. This process will begin at 12.00 UTC on 10th October. > > > What went wrong > === > > The feedback that you've given us has highlighted three flaws in the > bug expiration process we used: > ... Since these were mostly things that were different than your design intended (as I understand it) I think it'd be useful to do an autopsy on the pre-release test process and see what went wrong there too. > > > Understanding Launchpad's bug statuses > == > > While we were reviewing these issues, we discovered that many people > are using the Incomplete status to mean something other than "this > report cannot be confirmed to be a bug, additional information is > needed". The comments and activity of roughly 20% of the Incomplete > reports suggest that Confirmed or Wont Fix would have been a more > appropriate status. > > In light of this, we've written a blog post looking at how and when to > use the various bug statuses that Launchpad offers: > > http://news.launchpad.net/general/of-bugs-and-statuses > > > How we're going to fix this > === > > Now that we know that many people have used the Incomplete status to > mean a number of different things, we are going to restore the > Incomplete status of all bugs that the Launchpad Janitor changed. > > During this process: > > * Comments left by the Janitor will be removed from those bugs that >have their status restored. > * The updates will not generate email. > * We won't alter the status of any bug if its status has been >manually altered since the expiration. > > We still believe that our original intention -- to remove abandoned > bugs from bug queues -- will be a useful enhancement to Launchpad. > We're going to fix the three flaws in the expiration process and then > email selected projects' bug contacts with a list of the bugs that we > have identified as abandoned. With your feedback, we will refine this > process. We will only resume the expiry process when the Launchpad > user community is happy with the way we identify abandoned bugs. How about instead of an automatic process, make a link off the main bug page for a project/package called "Abandonded Bugs" or something similar that's a link to a canned query for all these bugs. Then give project/distro developers a "Mark all invalid" link. That way projects that wanted to clean house could easily do so and those that wanted to work through the old bugs one by one could. I think this would be inifinitely superior to trying to create a one size fits all process that will always leave some projects dissatisfied. > We will also update the Launchpad documentation to ensure it explains > the bug statuses more thoroughly and we will make that documentation > easier to find. But that presumes that projects using status in a way that's useful to them, but not what the LP developers intended is an actual problem that needs solving. Scott K -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Restoring the status of automatically expired bugs
Just to be clear as I'm not quite sure, are *all* Janitor-closed bugs going to be reverted or just the ones that were closed in error? -Jordan Mantha On 10/9/07, Matthew Revell <[EMAIL PROTECTED]> wrote: > Shortly after we released Launchpad 1.1.9 (on 21 September), > Launchpad's housekeeping system - the Launchpad Janitor - expired > 2,862 Incomplete bugs. We estimate that around 900 of these bugs > should not have been expired. > > We're sorry for the confusion and inconvenience that this caused. We > will restore the "Incomplete" status of all bugs that the Launchpad > Janitor expired. This process will begin at 12.00 UTC on 10th October. > > > What went wrong > === > > The feedback that you've given us has highlighted three flaws in the > bug expiration process we used: > > 1. We expired duplicate bugs: this went against our policy that > duplicate bugs should not be modified, nor should they generate email. > > 2. We expired bugs that were still being triaged: recent comment > activity showed that these bugs had not been abandoned but our process > didn't take account of that. > > 3. We expired bugs that were confirmed or fixed in another location: > once a bug is confirmed in one location, it should not be incomplete > in another. Bug contacts are responsible for managing a bug's many > statuses once it is confirmed in one location. > > > Understanding Launchpad's bug statuses > == > > While we were reviewing these issues, we discovered that many people > are using the Incomplete status to mean something other than "this > report cannot be confirmed to be a bug, additional information is > needed". The comments and activity of roughly 20% of the Incomplete > reports suggest that Confirmed or Wont Fix would have been a more > appropriate status. > > In light of this, we've written a blog post looking at how and when to > use the various bug statuses that Launchpad offers: > > http://news.launchpad.net/general/of-bugs-and-statuses > > > How we're going to fix this > === > > Now that we know that many people have used the Incomplete status to > mean a number of different things, we are going to restore the > Incomplete status of all bugs that the Launchpad Janitor changed. > > During this process: > > * Comments left by the Janitor will be removed from those bugs that >have their status restored. > * The updates will not generate email. > * We won't alter the status of any bug if its status has been >manually altered since the expiration. > > We still believe that our original intention -- to remove abandoned > bugs from bug queues -- will be a useful enhancement to Launchpad. > We're going to fix the three flaws in the expiration process and then > email selected projects' bug contacts with a list of the bugs that we > have identified as abandoned. With your feedback, we will refine this > process. We will only resume the expiry process when the Launchpad > user community is happy with the way we identify abandoned bugs. > > We will also update the Launchpad documentation to ensure it explains > the bug statuses more thoroughly and we will make that documentation > easier to find. > > Thank you for your ongoing feedback and for helping us to refine this > process. > > -- > Matthew Revell > launchpad.net > > mrevell in #launchpad on Freenode > > -- > Ubuntu-motu mailing list > Ubuntu-motu@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu > > -- "That's all very well in practice, but will it ever work in theory?" -- G. Hill "A tidy laboratory means a lazy chemist." -- Jöns Jacob Berzelius -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Restoring the status of automatically expired bugs
Shortly after we released Launchpad 1.1.9 (on 21 September), Launchpad's housekeeping system - the Launchpad Janitor - expired 2,862 Incomplete bugs. We estimate that around 900 of these bugs should not have been expired. We're sorry for the confusion and inconvenience that this caused. We will restore the "Incomplete" status of all bugs that the Launchpad Janitor expired. This process will begin at 12.00 UTC on 10th October. What went wrong === The feedback that you've given us has highlighted three flaws in the bug expiration process we used: 1. We expired duplicate bugs: this went against our policy that duplicate bugs should not be modified, nor should they generate email. 2. We expired bugs that were still being triaged: recent comment activity showed that these bugs had not been abandoned but our process didn't take account of that. 3. We expired bugs that were confirmed or fixed in another location: once a bug is confirmed in one location, it should not be incomplete in another. Bug contacts are responsible for managing a bug's many statuses once it is confirmed in one location. Understanding Launchpad's bug statuses == While we were reviewing these issues, we discovered that many people are using the Incomplete status to mean something other than "this report cannot be confirmed to be a bug, additional information is needed". The comments and activity of roughly 20% of the Incomplete reports suggest that Confirmed or Wont Fix would have been a more appropriate status. In light of this, we've written a blog post looking at how and when to use the various bug statuses that Launchpad offers: http://news.launchpad.net/general/of-bugs-and-statuses How we're going to fix this === Now that we know that many people have used the Incomplete status to mean a number of different things, we are going to restore the Incomplete status of all bugs that the Launchpad Janitor changed. During this process: * Comments left by the Janitor will be removed from those bugs that have their status restored. * The updates will not generate email. * We won't alter the status of any bug if its status has been manually altered since the expiration. We still believe that our original intention -- to remove abandoned bugs from bug queues -- will be a useful enhancement to Launchpad. We're going to fix the three flaws in the expiration process and then email selected projects' bug contacts with a list of the bugs that we have identified as abandoned. With your feedback, we will refine this process. We will only resume the expiry process when the Launchpad user community is happy with the way we identify abandoned bugs. We will also update the Launchpad documentation to ensure it explains the bug statuses more thoroughly and we will make that documentation easier to find. Thank you for your ongoing feedback and for helping us to refine this process. -- Matthew Revell launchpad.net mrevell in #launchpad on Freenode -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Re: Unable to upload new ia32-libs package to REVU
Hi Scott, Am Montag 08 Oktober 2007 08:52:08 schrieb Scott Ritchie: > Scott Ritchie wrote: > > The current ia32-libs package needs a refresh, and its missing the > > libssl0.9.8 package. > > > > I tried fixing these issues myself, however I've been unable to upload > > the package to REVU - it's 300 megabytes, and the connection will just > > fail after a while. It's likely my ISP. > > > > Wine depends on the existence of a 32 bit libssl0.9.8 in order to work > > fully - many of the libs in the package are also over a month out of > > date before release. > > > > How can I get the package up and committed? > > In the mean time, I have put the two packages here: > http://wine.budgetdedicated.com/experimental/ > > Perhaps someone with more reliable internet > connection can upload them for me. I've imported ia32-libs right on sparky, REVUs current home: [1]. Cheers, Stefan. -- [1]: http://revu.tauware.de/details.py?upid=371 signature.asc Description: This is a digitally signed message part. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
MOTU Q&A session on Friday, 12th Oct
Hello everybody, we're keeping the MOTU Q&A sessions rolling. The next one will be on Friday, October 12th, at 14:30 UTC in #ubuntu-classroom on irc.freenode.net If you always wanted to get involved, here's the best way to prepare: * check out http://wiki.ubuntu.com/MOTU and http://wiki.ubuntu.com/UbuntuDevelopment * play with http://wiki.ubuntu.com/MOTU/Recipes * note down all the questions you have * come to the session I look forward to seeing you all (and your questions) there! Have a nice day, Daniel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Mozilla ligature bug with Dejavu
Hi, https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/37828/comments/57 is a patch to "fix" the ligature bug in Mozilla, as this is only fixed in the next version this patch actually removes the ligatures from the Dejavu fonts. There's also a serious bug with FreeType on Gutsy the breaks U+00E5 å at some sizes. Do you want a patch so DejaVu Sans doesn't trigger the bug? Cheers, Denis Moyogo Jacquerye -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
MOTU Mentoring Meeting
Dear all, as announced at the last MOTU meeting, the MOTU Mentoring Reception would like to have a dedicated meeting on the Mentoring Program. We have set-up a provisional agenda as follows: 1. Current status of the Mentoring program - Feedback from Mentors - Drop rate - Open requests status - Available slots vs. requests 2. Future of the Mentoring program - How to increase the number of Mentors - How to improve feedback and effectiveness of Mentors - Is it possible to select contributors and if yes, how? - Should we set-up a trial period? 3. AOB Date, place and time is to be decided, but we think it could be a good idea to link it to the next MOTU meeting to permit attendance to the highest possible number of people: October 19th, at 13:00 UTC, #ubuntu-meeting We would appreciate it very much if you can participate and contribute to the meeting. Please let us know if you have any comment or additional topic which could be of interest. Let us also know what you think of the proposed date and time. Cheers, MOTU Mentoring Reception -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
Unsubscribing doesn't work ?
Hi, I have tried to unsubscribe, but i don't seem to get the confirmation mail. Please unsubscribe me from these ML's Thanks, -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
