From robla at robla.net Fri Jul 1 03:37:36 2005 From: robla at robla.net (Rob Lanphier) Date: Thu, 30 Jun 2005 20:37:36 -0700 Subject: Status of OpenID Consumer in Bugzilla Message-ID: <1120189057.18801.122.camel@localhost.localdomain> Hi folks, I've made some pretty good progress on OpenID. Nothing ready to release, but the actual authentication part is done. It just doesn't bother to check the database yet. I'm trying to decide how many shortcuts I take to get this to work. In particular, here's the list of questions I have: * Where should the OpenID URI be stored? * Should user log in using email or by OpenID? * Should email verification process still occur? * Should a confirm hash style verification (ala Mailman or GForge) be created, as opposed to mailing a password to the user? * How should createaccount.cgi modification be done? Here's where I've listed my answers to the questions: http://wiki.mozilla.org/Bugzilla:OpenID_Auth_Plugin I'd like some other opinions on this, as well. Since I'm not personally going to be running this in production (I'm just doing this to learn how OpenID and BZ work), it'd be good to hear from someone who will be running in production. Thanks Rob From kiko at async.com.br Fri Jul 1 14:15:37 2005 From: kiko at async.com.br (Christian Robottom Reis) Date: Fri, 1 Jul 2005 11:15:37 -0300 Subject: Status of OpenID Consumer in Bugzilla In-Reply-To: <1120189057.18801.122.camel@localhost.localdomain> References: <1120189057.18801.122.camel@localhost.localdomain> Message-ID: <20050701141537.GS11640@www.async.com.br> On Thu, Jun 30, 2005 at 08:37:36PM -0700, Rob Lanphier wrote: > I'm trying to decide how many shortcuts I take to get this to work. In > particular, here's the list of questions I have: > * Where should the OpenID URI be stored? Good question -- I assume the only reasonable place is in the profiles table. > * Should user log in using email or by OpenID? Allowing either might be nice. > * Should email verification process still occur? Yes. We don't want a user in Bugzilla without a valid email. > * Should a confirm hash style verification (ala Mailman or GForge) be > created, as opposed to mailing a password to the user? Why not use the existing Token mechanism? > * How should createaccount.cgi modification be done? This is a rather open question :-) Take care, -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125 From robla at robla.net Fri Jul 1 20:40:03 2005 From: robla at robla.net (Rob Lanphier) Date: Fri, 01 Jul 2005 13:40:03 -0700 Subject: Status of OpenID Consumer in Bugzilla In-Reply-To: <20050701141537.GS11640@www.async.com.br> References: <1120189057.18801.122.camel@localhost.localdomain> <20050701141537.GS11640@www.async.com.br> Message-ID: <1120250404.8445.26.camel@localhost.localdomain> On Fri, 2005-07-01 at 11:15 -0300, Christian Robottom Reis wrote: > On Thu, Jun 30, 2005 at 08:37:36PM -0700, Rob Lanphier wrote: > > I'm trying to decide how many shortcuts I take to get this to work. In > > particular, here's the list of questions I have: > > * Where should the OpenID URI be stored? > > Good question -- I assume the only reasonable place is in the profiles > table. I'm currently using profiles.extern_id, which is only 64 characters long. Max replied in bug 294608 (the openid bug) that that should be the permahome for this, expanding the size if necessary. It would mean, however, that any two auth mechanisms that use extern_id couldn't be used together. > > * Should user log in using email or by OpenID? > > Allowing either might be nice. I'm heading in that direction now. My first iteration on this is going to require that both DB and OpenID verify are turned on. OpenID login support is going to be a superset of plain CGI login. So, basically, you'll create an account using the standard username/password mechanism. However, once you log in the first time, you can associate an OpenID with the account, and presumably never need the password again. > > * Should email verification process still occur? > > Yes. We don't want a user in Bugzilla without a valid email. Long-term, I can see this being site configurable. Some sites may want to insist on having valid email on record, other sites may not. Some users may prefer to be able to submit a bug without submitting their email, and don't mind missing out on email notification. However, with bug reports, I imagine the development teams will probably be forced to close out vague reports due to not being able to contact the reporter. OpenID-only logins aren't completely anonymous, but currently lack a standard push messaging mechanism. > > * Should a confirm hash style verification (ala Mailman or GForge) be > > created, as opposed to mailing a password to the user? > > Why not use the existing Token mechanism? /me looks. Hey, whaddya know! :) I saw that the standard new account creation mechanism just pushed out a password rather than a login token, so I just assumed that there wasn't a token mechanism. Any philosophical reason why Token isn't used for new account creation, or is it just a bit of cleanup that's always been below the cut line? > > * How should createaccount.cgi modification be done? > > This is a rather open question :-) Indeed. I decided to narrow the question quite a bit by punting on it :) The first version will just use standard account creation. For the long term, it's tempting to restructure this code, creating a new Bugzilla->create_account($cgi) method, and moving the bulk of the current code into Bugzilla/Auth/Login/WWW/CGI.pm, or perhaps create Bugzilla/Auth/Create/WWW/CGI.pm along with Bugzilla/Auth/Create/WWW/OpenID.pm. Rob From jake at bugzilla.org Fri Jul 1 22:39:02 2005 From: jake at bugzilla.org (Jake) Date: Fri, 1 Jul 2005 18:39:02 -0400 (EDT) Subject: Status of OpenID Consumer in Bugzilla In-Reply-To: <1120250404.8445.26.camel@localhost.localdomain> References: <1120189057.18801.122.camel@localhost.localdomain> <20050701141537.GS11640@www.async.com.br> <1120250404.8445.26.camel@localhost.localdomain> Message-ID: <50075.71.115.162.147.1120257542.squirrel@mail.steenhagen.us> On Fri, July 1, 2005 4:40 pm, Rob Lanphier wrote: > Hey, whaddya know! :) I saw that the standard new account creation > mechanism just pushed out a password rather than a login token, so I just > assumed that there wasn't a token mechanism. > > Any philosophical reason why Token isn't used for new account creation, > or is it just a bit of cleanup that's always been below the cut line? I remember asking that question once before myself, but I don't remember what, if anything, the answer was. But I agree that using the tokens would be better than email a password in almost every case I can think of. From robla at robla.net Fri Jul 1 23:03:26 2005 From: robla at robla.net (Rob Lanphier) Date: Fri, 01 Jul 2005 16:03:26 -0700 Subject: Status of OpenID Consumer in Bugzilla In-Reply-To: References: <1120189057.18801.122.camel@localhost.localdomain> Message-ID: <1120259007.8445.123.camel@localhost.localdomain> Hi Martin, Comments inline (multiple parts snipped out): On Fri, 2005-07-01 at 10:59 +0100, Martin Atkins wrote: > Rob Lanphier wrote: > > * Where should the OpenID URI be stored? > > LiveJournal does this by having a separate identity map table. Every new > OpenID user gets a userid magically allocated and an entry placed into > the map table which is essentially a (userid, identity) pair. This seems > reasonable since it doesn't inflate any other tables and add needless > indexes for sites which aren't using OpenID. I think you're probably right from a long-term perspective. I have some misgivings about using an existing field that may clash with other auth mechanisms. BZ folks, what are your thoughts on this input? > > * Should email verification process still occur? > > No. As above, ideally Bugzilla shouldn't need my email address unless I > want to be contacted through it, in which case I'll provide it when I've > logged in. The address I'm identified by on LiveJournal's bugzilla > installation doesn't actually work anymore, but I've done nothing about > it because I don't want email from Bugzilla anyway. I don't really see > why I should have to provide it if I'm not going to use it as a login > identifier, especially on LiveJournal's Bugzilla where email isn't used > as a primary means of contact. Well, I don't see any way around verifying email *when* its used. You bring up very good points on the question of "if", but once someone opts in, I don't think that BZ can trust an email provided by an OpenID user any more than it can trust an email provided by a normal new account. So, this is probably a two-stage process: 1. Make it possible to use BZ with OpenID 2. Make it possible to use BZ without email A third stage way down the road is to somehow optimize how email verification works (e.g. OpenID for mailto: URLs). > In the interests of getting a working version out quickly, though, I'd > accept as a short term solution just binding an OpenID identity to an > existing email-bound account. That way I won't have to remember my > password. :) Cool, I should be able to get something like this out soon. Rob From robla at robla.net Fri Jul 1 23:35:12 2005 From: robla at robla.net (Rob Lanphier) Date: Fri, 01 Jul 2005 16:35:12 -0700 Subject: Using Token for new accounts (Re: Status of OpenID Consumer in Bugzilla) In-Reply-To: <50075.71.115.162.147.1120257542.squirrel@mail.steenhagen.us> References: <1120189057.18801.122.camel@localhost.localdomain> <20050701141537.GS11640@www.async.com.br> <1120250404.8445.26.camel@localhost.localdomain> <50075.71.115.162.147.1120257542.squirrel@mail.steenhagen.us> Message-ID: <1120260912.8445.128.camel@localhost.localdomain> On Fri, 2005-07-01 at 18:39 -0400, Jake wrote: > On Fri, July 1, 2005 4:40 pm, Rob Lanphier wrote: > > Hey, whaddya know! :) I saw that the standard new account creation > > mechanism just pushed out a password rather than a login token, so I just > > assumed that there wasn't a token mechanism. > > > > Any philosophical reason why Token isn't used for new account creation, > > or is it just a bit of cleanup that's always been below the cut line? > > I remember asking that question once before myself, but I don't remember > what, if anything, the answer was. But I agree that using the tokens would > be better than email a password in almost every case I can think of. Looks like this bug is the answer: https://bugzilla.mozilla.org/show_bug.cgi?id=87795 Summary: it's just been below the cut line, and just fell below the cut line for 2.20, but is targeted for 2.22. Rob From timeless at myrealbox.com Sat Jul 2 00:02:20 2005 From: timeless at myrealbox.com (timeless) Date: Fri, 01 Jul 2005 17:02:20 -0700 Subject: Status of OpenID Consumer in Bugzilla In-Reply-To: <50075.71.115.162.147.1120257542.squirrel@mail.steenhagen.us> References: <1120189057.18801.122.camel@localhost.localdomain> <20050701141537.GS11640@www.async.com.br> <1120250404.8445.26.camel@localhost.localdomain> <50075.71.115.162.147.1120257542.squirrel@mail.steenhagen.us> Message-ID: <42C5D98C.5060009@myrealbox.com> On Fri, July 1, 2005 4:40 pm, Rob Lanphier wrote: > Any philosophical reason why Token isn't used for new account creation, > or is it just a bit of cleanup that's always been below the cut line? Jake wrote: > I remember asking that question once before myself, but I don't remember > what, if anything, the answer was. But I agree that using the tokens would > be better than email a password in almost every case I can think of. afaik tokens were introduced and no one ported new accounts to use them. note that we really do want to switch because it will stop bugzilla's user account list from being bloated by accounts that can't exist. From bugreport at peshkin.net Sat Jul 2 02:01:41 2005 From: bugreport at peshkin.net (Joel Peshkin) Date: Fri, 01 Jul 2005 19:01:41 -0700 Subject: Status of OpenID Consumer in Bugzilla In-Reply-To: <1120259007.8445.123.camel@localhost.localdomain> References: <1120189057.18801.122.camel@localhost.localdomain> <1120259007.8445.123.camel@localhost.localdomain> Message-ID: <42C5F585.7000401@peshkin.net> Rob Lanphier wrote: >Hi Martin, > >Comments inline (multiple parts snipped out): > >On Fri, 2005-07-01 at 10:59 +0100, Martin Atkins wrote: > > >>Rob Lanphier wrote: >> >> >>>* Where should the OpenID URI be stored? >>> >>> >>LiveJournal does this by having a separate identity map table. Every new >>OpenID user gets a userid magically allocated and an entry placed into >>the map table which is essentially a (userid, identity) pair. This seems >>reasonable since it doesn't inflate any other tables and add needless >>indexes for sites which aren't using OpenID. >> >> > >I think you're probably right from a long-term perspective. I have some >misgivings about using an existing field that may clash with other auth >mechanisms. > >BZ folks, what are your thoughts on this input? > > > extern_id was created so that, if an external authentication mechanism had an identifier for a user that persist even if the email address changes, the external identifier would be preserved. This was originally for SiteMinder which passes LDAP attributes via enviroment variables. One of those attributes is a numeric string that perists even if the user's name and email address change (like in the case of marriage or domain name renames). The environment variable authenication mechanism will rename an existing profile to re-learn the email address and real name of a user if the extern_id is the same. This sounds like it matches the purpose of the OpenID identifier. The biggest problem I see is that Bugzilla cannot get either Realname or Email address from OpenId. It would be very cool if OpenID were tied into an SMTP server so that sites to which I previously logged in could send me mail (unless I revoke the permission) by using a mail-delivery key provided by my OpenID provider. -Joel From mkanat at bugzilla.org Sat Jul 2 02:50:53 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Fri, 01 Jul 2005 19:50:53 -0700 Subject: Status of OpenID Consumer in Bugzilla In-Reply-To: <1120259007.8445.123.camel@localhost.localdomain> References: <1120189057.18801.122.camel@localhost.localdomain> <1120259007.8445.123.camel@localhost.localdomain> Message-ID: <1120272654.5468.9.camel@localhost.localdomain> On Fri, 2005-07-01 at 16:03 -0700, Rob Lanphier wrote: > I think you're probably right from a long-term perspective. I have some > misgivings about using an existing field that may clash with other auth > mechanisms. > > BZ folks, what are your thoughts on this input? Originally having just an extern_id in Bugzilla was fine, because you couldn't "stack" Auth modules. Since the introduction of "stacking" Auth modules in Bugzilla 2.19, external-ids-to-profiles is a many-to-one relationship. So yeah, external ids should have a table: user_id, extern_id, auth_method > > In the interests of getting a working version out quickly, though, I'd > > accept as a short term solution just binding an OpenID identity to an > > existing email-bound account. That way I won't have to remember my > > password. :) Yeah, that's also the solution that I would suggest currently. And to present somebody the option of making an email-bound account if they enter an unknown OpenID. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From robla at robla.net Sat Jul 2 05:46:34 2005 From: robla at robla.net (Rob Lanphier) Date: Fri, 01 Jul 2005 22:46:34 -0700 Subject: Bugzilla/OpenID support patch available (v0.1.0) Message-ID: <1120283194.8445.141.camel@localhost.localdomain> Hi folks, Initial version of Bugzilla/OpenID support is available. Patch download, open issues, and other details here: http://wiki.mozilla.org/Bugzilla:OpenID_Auth_Plugin Enjoy! Rob From mkanat at bugzilla.org Sat Jul 2 21:16:16 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 02 Jul 2005 14:16:16 -0700 Subject: Landfill downtime approaching Message-ID: <1120338976.5466.6.camel@localhost.localdomain> Hey there. landfill.bugzilla.org may have some extended downtime very soon, perhaps starting later this evening (GMT-7). It's moving to a new server, so I have to move a bunch of stuff from it, and it can't be being *used* while the stuff is moving. And even after I move all the stuff, I have to wait for a Mozilla Foundation administrator to be available to make the DNS switch. So there's a chance that if I take the machine down tonight, it won't come up again until tomorrow. The IRC bots and the tinderboxes have already been moved (except for the documentation tinderboxes, which will be moved later), so there should be very minimal effect from the box being closed off. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From mart at degeneration.co.uk Fri Jul 1 09:59:52 2005 From: mart at degeneration.co.uk (Martin Atkins) Date: Fri, 01 Jul 2005 10:59:52 +0100 Subject: Status of OpenID Consumer in Bugzilla In-Reply-To: <1120189057.18801.122.camel@localhost.localdomain> References: <1120189057.18801.122.camel@localhost.localdomain> Message-ID: Rob Lanphier wrote: > * Where should the OpenID URI be stored? LiveJournal does this by having a separate identity map table. Every new OpenID user gets a userid magically allocated and an entry placed into the map table which is essentially a (userid, identity) pair. This seems reasonable since it doesn't inflate any other tables and add needless indexes for sites which aren't using OpenID. If you're eventually going to need to separate out email addresses anyway, perhaps it would be a good idea to have a "user" table and an "identity" table. The "user" table would just have a numeric userid that no-one ever sees, while the identity table would store one or more ways that user can log in. A type field which can be either "email" or "openid" can differentiate the two. Not sure where you'd put the password in the email case, though. Need to think about this more. This would obviously be separate from the contact email address used when a user adds himself to CC: or whatever, as many OpenID users will probably still want to recieve email. Users would also have to choose a primary "display" identity, which dictates which of the identities will be used on the website to identify a user. I imagine that some installations will want the ability to mandate a contact email address, too. > * Should user log in using email or by OpenID? Ideally in the long term Bugzilla shouldn't need to know email addresses, I think. However, I realise that right now the email address is essentially Bugzilla's primary key so you can't really get rid of them that easily. Automatically allocating a gibberish email address wouldn't fly because users would then be unable to opt to recieve email without changing it. > * Should email verification process still occur? No. As above, ideally Bugzilla shouldn't need my email address unless I want to be contacted through it, in which case I'll provide it when I've logged in. The address I'm identified by on LiveJournal's bugzilla installation doesn't actually work anymore, but I've done nothing about it because I don't want email from Bugzilla anyway. I don't really see why I should have to provide it if I'm not going to use it as a login identifier, especially on LiveJournal's Bugzilla where email isn't used as a primary means of contact. > * Should a confirm hash style verification (ala Mailman or GForge) be > created, as opposed to mailing a password to the user? Given that I don't want email verification at all, I think I can ignore this one. ;) > * How should createaccount.cgi modification be done? I don't really know enough about the Bugzilla code to answer this, but what you've written on the wiki (about making a separate create_account function) seems like a good idea in general anyway. > I'd like some other opinions on this, as well. Since I'm not personally > going to be running this in production (I'm just doing this to learn how > OpenID and BZ work), it'd be good to hear from someone who will be > running in production. My idea of how I'd like this to work in an ideal world is as follows: * OpenID identities rather than email addresses are used as the user identifier in the interface. (or, more likely, allow both) * To log in with OpenID, I just supply my OpenID URL and no password. * For migration purposes, existing users should be able to log in by email address and then do an OpenID login to add a new identity to that account. In the interests of getting a working version out quickly, though, I'd accept as a short term solution just binding an OpenID identity to an existing email-bound account. That way I won't have to remember my password. :) (I should probably note, since this is also going to a mailing list where I'm a stranger, that despite the LiveJournal references here I'm not a LiveJournal staffer and the opinions here are mine alone rather than any kind of Six Apart-endorsed wishlist.) From gerv at mozilla.org Tue Jul 5 09:34:48 2005 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 05 Jul 2005 10:34:48 +0100 Subject: Wiki space for Bugzilla In-Reply-To: <42C37F42.1050608@bugzilla.org> References: <42C37F42.1050608@bugzilla.org> Message-ID: <42CA5438.6000902@mozilla.org> David Miller wrote: > Since a couple people are working on things that would be good to have > some wiki space for so people have a general "white board" type place to > edit for it, I've set up a namespace on the Mozilla Wiki for > Bugzilla-related pages. > > Starting off at http://wiki.mozilla.org/Bugzilla:Main_Page This is cool; but what is the plan for the relationship between the wiki and the Bugzilla Guide? For example, this content: http://wiki.mozilla.org/Bugzilla:Modifying_Your_Installation seems fairly "Guide-y". Gerv From mkanat at bugzilla.org Wed Jul 6 08:39:30 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 06 Jul 2005 01:39:30 -0700 Subject: The New Landfill! Message-ID: <1120639171.5480.34.camel@localhost.localdomain> Hey everybody. OK, so landfill.bugzilla.org has been pretty much completely moved, now. For the most part, nothing should be different except that it's much faster. If there's anything that's not working, or anything that I forgot to move, just let me know. There are one or two MySQL DBs that didn't get moved, but I'm pretty sure they weren't critical. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From mkanat at bugzilla.org Wed Jul 6 08:48:28 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 06 Jul 2005 01:48:28 -0700 Subject: The New Landfill! In-Reply-To: <1120639171.5480.34.camel@localhost.localdomain> References: <1120639171.5480.34.camel@localhost.localdomain> Message-ID: <1120639708.5480.36.camel@localhost.localdomain> Oh, and also, if you still need to get to the old landfill this week for some reason, it lives at: landfill-old.bugzilla.org. If there's anything left over there that should be copied over, let me know. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From mkanat at bugzilla.org Thu Jul 7 05:36:27 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 06 Jul 2005 22:36:27 -0700 Subject: Status of 2.20rc1 Message-ID: <1120714587.5856.34.camel@localhost.localdomain> Hey hey. Just a quick update: RC1 is almost ready to release. We're awaiting approval for the Release Notes bugs, and also for somebody to complete the Status Update. Glob has started on the Status Update; if anybody else wants to work on it you can come into IRC and attempt to get what he has so far from him or I. The Status Update bug is: https://bugzilla.mozilla.org/show_bug.cgi?id=297742 -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From bugzilla at glob.com.au Thu Jul 7 06:15:00 2005 From: bugzilla at glob.com.au (byron) Date: Thu, 7 Jul 2005 14:15:00 +0800 (WST) Subject: Status of 2.20rc1 Message-ID: <20050707061500.1D6C84BCE24@sweep.bur.st> > RC1 is almost ready to release. We're awaiting approval for the Release > Notes bugs, and also for somebody to complete the Status Update. Glob > has started on the Status Update; if anybody else wants to work on it > you can come into IRC and attempt to get what he has so far from him or > I. there i was thinking that i'd have a week of spare time at work after i gave in my notice, then work spoilt the plan by quickly hiring my replacement; so i've been in handover mode. i've attached what i've done thus far on the bug. -b begin-base64 644 signature.gif R0lGODlhbQAHAIAAAABPo////ywAAAAAbQAHAAACfAxuGAnch+Bibkn7FL1p XgVl4Ig1jjlZRoqybgun2Cur5uOunq7u/Ipq7WIyIc7XG9JquEgumPzdlhTf h0O83kDJaXEm8mRHwXKJy5sac7qYOpT+gtv0n+0ujQOfdqh16caWt0foBViH N1PRMXimiLUGt3ElVimlgbllWAAAOw== ==== From bugzilla at colinogilvie.co.uk Thu Jul 7 23:24:05 2005 From: bugzilla at colinogilvie.co.uk (Colin Ogilvie) Date: Fri, 8 Jul 2005 00:24:05 +0100 Subject: The New Landfill! In-Reply-To: <1120639171.5480.34.camel@localhost.localdomain> References: <1120639171.5480.34.camel@localhost.localdomain> Message-ID: <20050707232405.GA26648@colinogilvie.co.uk> On Wed, Jul 06, 2005 at 01:39:30AM -0700, Max Kanat-Alexander wrote: > If there's anything that's not working, or anything that I forgot to > move, just let me know. There are one or two MySQL DBs that didn't get > moved, but I'm pretty sure they weren't critical. A couple of things I've noticed: *) As far as I can tell, the documentation for landfill implies that I'm meant to be able to create folders in /var/www/html but I don't appear to be able to so at the moment. *) The documentation won't build using the old system as per explination below: /usr/share/sgml/docbook/ldp/ldp.dsl needs to be edited so that the bit at the top which currently reads ]]> ]]> reads ]]> ]]> as per http://lxr.mozilla.org/bugzilla/source/docs/README.docs *) There's still no docs tinderbox ;) Speaking of docs tinderbox, would someone be able to dump the docs tinderbox scripts into my home dir (/home/colin) for me? Colin -- Colin Ogilvie bugzilla at colinogilvie.co.uk From mkanat at bugzilla.org Fri Jul 8 03:03:18 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 07 Jul 2005 20:03:18 -0700 Subject: The New Landfill! In-Reply-To: <20050707232405.GA26648@colinogilvie.co.uk> References: <1120639171.5480.34.camel@localhost.localdomain> <20050707232405.GA26648@colinogilvie.co.uk> Message-ID: <1120791799.5464.7.camel@localhost.localdomain> On Fri, 2005-07-08 at 00:24 +0100, Colin Ogilvie wrote: > *) As far as I can tell, the documentation for landfill implies that I'm > meant to be able to create folders in /var/www/html but I don't appear > to be able to so at the moment. Well, the /tools/ should be able to. Do you need to create them directly yourself? I can change that, also. > /usr/share/sgml/docbook/ldp/ldp.dsl needs to be edited so that the bit > at the top which currently reads [snip] OK, fixed. > *) There's still no docs tinderbox ;) Ahh, fixed. :-) They'll all show up in the next few minutes. > Speaking of docs tinderbox, would someone be able to dump the docs > tinderbox scripts into my home dir (/home/colin) for me? Sure, done. There's a tinderbox-docs.tar.bz2 there, now. Don't run them on landfill, though, since they're already running. :-) -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From bugzilla at colinogilvie.co.uk Fri Jul 8 08:11:47 2005 From: bugzilla at colinogilvie.co.uk (Colin Ogilvie) Date: Fri, 08 Jul 2005 09:11:47 +0100 Subject: The New Landfill! In-Reply-To: <1120791799.5464.7.camel@localhost.localdomain> References: <1120639171.5480.34.camel@localhost.localdomain><20050707232405.GA26648@colinogilvie.co.uk> <1120791799.5464.7.camel@localhost.localdomain> Message-ID: <42CE3543.4080302@colinogilvie.co.uk> Max Kanat-Alexander wrote: > Well, the /tools/ should be able to. Do you need to create them > directly yourself? I can change that, also. > The /tools/ enables me to create Bugzilla directories; I just need a publicly-accessible folder to put test documentation in - having a full Bugzilla install seems slightly overkill :) Colin -- Colin Ogilvie bugzilla at colinogilvie.co.uk From mkanat at bugzilla.org Fri Jul 8 08:38:58 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Fri, 08 Jul 2005 01:38:58 -0700 Subject: The New Landfill! In-Reply-To: <42CE3543.4080302@colinogilvie.co.uk> References: <1120639171.5480.34.camel@localhost.localdomain> <20050707232405.GA26648@colinogilvie.co.uk> <1120791799.5464.7.camel@localhost.localdomain> <42CE3543.4080302@colinogilvie.co.uk> Message-ID: <1120811939.8182.0.camel@localhost.localdomain> On Fri, 2005-07-08 at 09:11 +0100, Colin Ogilvie wrote: > The /tools/ enables me to create Bugzilla directories; I just need a > publicly-accessible folder to put test documentation in - having a full > Bugzilla install seems slightly overkill :) OK. You should be able to make dirs in /var/www/html/ now. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From justdave at bugzilla.org Fri Jul 8 10:00:45 2005 From: justdave at bugzilla.org (David Miller) Date: Fri, 08 Jul 2005 06:00:45 -0400 Subject: Branch release problems Message-ID: <42CE4ECD.6000505@bugzilla.org> Tonight we released a 2.18.2 release with a non-functioning query page. I had to post an announcement telling people not to download it and wait for an update. That's not a fun thing to do. This has also happened before (branch releases going out with major regressions in them) with versions 2.16.9 and 2.14.5. This is really unacceptable and it messes badly with the public perception of our credibility. We really need some kind of better QA process on our branch releases. I know it's hard because all of the developers run the cvs tip or the developer releases for their own installations, so nobody's familiar with the branches, but that's what we have landfill for, and we need to make sure things get tested before they go out. At a minimum we need to put together some kind of smoke test document with lists of features to test for each branch, then we need to make sure that testing *everything* on that list is made part of the release process, before a tarball is rolled, no matter how few patches actually got checked in, or what they touched. I'd welcome any other ideas anyone has, too. We've also got almost zero actual QA since MattyT got busy with real life. It'd probably be a cool thing to get some people to actually do QA type things for us again. Bugzilla is growing by leaps and bounds, and we definitely have a big enough product to badly need a whole QA team, let alone the one-man-show that MattyT used to run. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From LpSolit at gmail.com Fri Jul 8 10:28:03 2005 From: LpSolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Fri, 08 Jul 2005 12:28:03 +0200 Subject: Branch release problems In-Reply-To: <42CE4ECD.6000505@bugzilla.org> References: <42CE4ECD.6000505@bugzilla.org> Message-ID: <42CE5533.30708@gmail.com> > versions 2.16.9 and 2.14.5. This is really unacceptable and it messes > badly with the public perception of our credibility. > I'd welcome any other ideas anyone has, too. Create a (small) QA team, if possible including some reviewers (who should be the most familiar with bz code), and ask them to create this smoke test document you are talking about. At least 24 hours before any release, no more checkin is allowed. And security patches have to be applied manually to avoid making them public (no CVS upload). During this "really frozen" period, the QA team checks *all* points of the smoke test document, such as: - Queries, including query.cgi, buglist.cgi and Search.pm - Creating/changing bugs and attachments, including flags - UI - Charts/reports - E-Mails, including BugMail.pm and *whine*.* - Admin pages (product, component, ... creation and deletion) - Account creation/ prefs settings - Some "security" tests - Fresh installation/upgrade from older ones - Improve and check sanitycheck.cgi (or create your own releasecheck.cgi) I am a reviewer, I have access to all security bugs related to Webtools and I already do some "QA testing" (kind of). So I agree to belong to this QA team. But doing checkins 15 minutes before releasing any new version is far too short for me, especially when I'm away at this precise moment. :) Frederic "LpSolit" Buclin From ed.fuentetaja at gmail.com Fri Jul 8 10:56:33 2005 From: ed.fuentetaja at gmail.com (Ed) Date: Fri, 8 Jul 2005 12:56:33 +0200 Subject: Branch release problems In-Reply-To: <42CE5533.30708@gmail.com> References: <42CE4ECD.6000505@bugzilla.org> <42CE5533.30708@gmail.com> Message-ID: <4a6b55ad05070803562bdb055a@mail.gmail.com> I'd suggest to use Test Runner to document smoke test and keep a track record of their outcome. Kind regards, Ed On 7/8/05, Fr?d?ric Buclin wrote: > > versions 2.16.9 and 2.14.5. This is really unacceptable and it messes > > badly with the public perception of our credibility. > > > I'd welcome any other ideas anyone has, too. > > Create a (small) QA team, if possible including some reviewers (who > should be the most familiar with bz code), and ask them to create this > smoke test document you are talking about. At least 24 hours before any > release, no more checkin is allowed. And security patches have to be > applied manually to avoid making them public (no CVS upload). During > this "really frozen" period, the QA team checks *all* points of the > smoke test document, such as: > > - Queries, including query.cgi, buglist.cgi and Search.pm > - Creating/changing bugs and attachments, including flags > - UI > - Charts/reports > - E-Mails, including BugMail.pm and *whine*.* > - Admin pages (product, component, ... creation and deletion) > - Account creation/ prefs settings > - Some "security" tests > - Fresh installation/upgrade from older ones > - Improve and check sanitycheck.cgi (or create your own releasecheck.cgi) > > I am a reviewer, I have access to all security bugs related to Webtools > and I already do some "QA testing" (kind of). So I agree to belong to > this QA team. > > But doing checkins 15 minutes before releasing any new version is far > too short for me, especially when I'm away at this precise moment. :) > > Frederic "LpSolit" Buclin > - > To view or change your list settings, click here: > > From jremillardshop at letterboxes.org Fri Jul 8 13:34:10 2005 From: jremillardshop at letterboxes.org (Jason Remillard) Date: Fri, 08 Jul 2005 09:34:10 -0400 Subject: Branch release problems In-Reply-To: <42CE4ECD.6000505@bugzilla.org> References: <42CE4ECD.6000505@bugzilla.org> Message-ID: <42CE80D2.7020909@letterboxes.org> Hi, David Miller wrote: > Tonight we released a 2.18.2 release with a non-functioning query page. > > I had to post an announcement telling people not to download it and wait > for an update. That's not a fun thing to do. This has also happened > before (branch releases going out with major regressions in them) with > versions 2.16.9 and 2.14.5. This is really unacceptable and it messes > badly with the public perception of our credibility. > > We really need some kind of better QA process on our branch releases. I > know it's hard because all of the developers run the cvs tip or the > developer releases for their own installations, so nobody's familiar > with the branches, but that's what we have landfill for, and we need to > make sure things get tested before they go out. > > At a minimum we need to put together some kind of smoke test document > with lists of features to test for each branch, then we need to make > sure that testing *everything* on that list is made part of the release > process, before a tarball is rolled, no matter how few patches actually > got checked in, or what they touched. > > I'd welcome any other ideas anyone has, too. > I wrote a set or perl tests scripts using the LWP modules, HTML::Form, HTML::LinkExtractor, HTML::Lint that are used to test codestriker out. It is pretty easy to test a web base application with perl. You write a proxy .pm for each page in bugzilla. The proxy uses LWP, and friends to manipulate the actual service. Your .t files then use the proxies to do the tests. We used to have a smoke test document. The smoke test is all automated now + a bunch of other tests that we were not doing before. Compared to the complexity of bugzilla, these tests would really not be that big of a deal to write. It is really easy to at least make sure all of the links are good, and the generated html is well formed. The code is here. http://cvs.sourceforge.net/viewcvs.py/codestriker/codestriker/test/ Once the infrastructure is in place, then you can insist that every new features get checked in with test cases. I know that there are plans to test the pm files inside of bugzilla directly, but you really can't escape the fact that it needs to work property at the http/html level. I don't think doing both is unreasonable. Not everything will be easy to automate, so a test document is also a good idea. Thanks Jason. From kevin.benton at amd.com Fri Jul 8 14:39:04 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Fri, 8 Jul 2005 07:39:04 -0700 Subject: Branch release problems Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42016BDD09@ssvlexmb2.amd.com> > Tonight we released a 2.18.2 release with a non-functioning query page. > > I had to post an announcement telling people not to download it and wait > for an update. That's not a fun thing to do. This has also happened > before (branch releases going out with major regressions in them) with > versions 2.16.9 and 2.14.5. This is really unacceptable and it messes > badly with the public perception of our credibility. > > We really need some kind of better QA process on our branch releases. I > know it's hard because all of the developers run the cvs tip or the > developer releases for their own installations, so nobody's familiar > with the branches, but that's what we have landfill for, and we need to > make sure things get tested before they go out. > > At a minimum we need to put together some kind of smoke test document > with lists of features to test for each branch, then we need to make > sure that testing *everything* on that list is made part of the release > process, before a tarball is rolled, no matter how few patches actually > got checked in, or what they touched. > > I'd welcome any other ideas anyone has, too. > > We've also got almost zero actual QA since MattyT got busy with real > life. It'd probably be a cool thing to get some people to actually do > QA type things for us again. Bugzilla is growing by leaps and bounds, > and we definitely have a big enough product to badly need a whole QA > team, let alone the one-man-show that MattyT used to run. Dave - that's why I'm actively working on a pre-release testing guide for Bugzilla use here. Part of what I'm doing, however, is making it so I can produce the necessary documentation for general Bugzilla testing as well. The process of creating this guide is so involved, however, that I don't see it being done for at least a few months. --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. From Axel.Thimm at ATrpms.net Fri Jul 8 19:24:04 2005 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Fri, 8 Jul 2005 21:24:04 +0200 Subject: 2.18.2: Can't find param named cookiedomain at Bugzilla/Config.pm line 150. Message-ID: <20050708192404.GD23768@neu.nirvana> I upgraded from 2.18rc2 to 2.18.2 and upon logging in or trying to perform a search I get this response. I tried both a CVS upgrade and a new install with copying over localconfig (and running checksetup.pl in both cases). I don't think this is a bugzilla bug, but probably a local configuration issue. How can I find the problem? Help! ;) -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From justdave at bugzilla.org Fri Jul 8 19:26:39 2005 From: justdave at bugzilla.org (David Miller) Date: Fri, 08 Jul 2005 15:26:39 -0400 Subject: 2.18.2: Can't find param named cookiedomain at Bugzilla/Config.pm In-Reply-To: <20050708192404.GD23768@neu.nirvana> References: <20050708192404.GD23768@neu.nirvana> Message-ID: <42CED36F.1060901@bugzilla.org> Axel Thimm wrote: > I upgraded from 2.18rc2 to 2.18.2 and upon logging in or trying to > perform a search I get this response. I tried both a CVS upgrade and a > new install with copying over localconfig (and running checksetup.pl > in both cases). > > I don't think this is a bugzilla bug, but probably a local > configuration issue. How can I find the problem? It's a Bugzilla bug. Delete line 193 in Bugzilla/CGI.pm (it's the line that says cookiedomain in it). -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From Axel.Thimm at ATrpms.net Fri Jul 8 19:36:39 2005 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Fri, 8 Jul 2005 21:36:39 +0200 Subject: 2.18.2: Can't find param named cookiedomain at Bugzilla/Config.pm In-Reply-To: <42CED36F.1060901@bugzilla.org> References: <20050708192404.GD23768@neu.nirvana> <42CED36F.1060901@bugzilla.org> Message-ID: <20050708193639.GE23768@neu.nirvana> On Fri, Jul 08, 2005 at 03:26:39PM -0400, David Miller wrote: > Axel Thimm wrote: > > I upgraded from 2.18rc2 to 2.18.2 and upon logging in or trying to > > perform a search I get this response. I tried both a CVS upgrade and a > > new install with copying over localconfig (and running checksetup.pl > > in both cases). > > > > I don't think this is a bugzilla bug, but probably a local > > configuration issue. How can I find the problem? > > It's a Bugzilla bug. Delete line 193 in Bugzilla/CGI.pm (it's the line > that says cookiedomain in it). Thanks a lot, David, that did it. :) I'll patch up the bugzilla rpms at ATrpms to remove this line. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From justdave at bugzilla.org Fri Jul 8 19:47:40 2005 From: justdave at bugzilla.org (David Miller) Date: Fri, 08 Jul 2005 15:47:40 -0400 Subject: 2.18.2: Can't find param named cookiedomain at Bugzilla/Config.pm In-Reply-To: <20050708193639.GE23768@neu.nirvana> References: <20050708192404.GD23768@neu.nirvana> <42CED36F.1060901@bugzilla.org> <20050708193639.GE23768@neu.nirvana> Message-ID: <42CED85C.4090101@bugzilla.org> Axel Thimm wrote: > I'll patch up the bugzilla rpms at ATrpms to remove this line. Or just skip it and package 2.18.3, coming later tonight. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From wurblzap at gmail.com Fri Jul 8 20:27:54 2005 From: wurblzap at gmail.com (Marc Schumann) Date: Fri, 8 Jul 2005 22:27:54 +0200 Subject: 2.18.2: Can't find param named cookiedomain at Bugzilla/Config.pm line 150. In-Reply-To: <20050708192404.GD23768@neu.nirvana> References: <20050708192404.GD23768@neu.nirvana> Message-ID: Please see https://bugzilla.mozilla.org/show_bug.cgi?id=268146. 2005/7/8, Axel Thimm : > I upgraded from 2.18rc2 to 2.18.2 and upon logging in or trying to > perform a search I get this response. I tried both a CVS upgrade and a > new install with copying over localconfig (and running checksetup.pl > in both cases). > > I don't think this is a bugzilla bug, but probably a local > configuration issue. How can I find the problem? -- http://wurblzap.net/ Bugzilla hosting and professional support From mkanat at bugzilla.org Sun Jul 10 00:01:10 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 09 Jul 2005 17:01:10 -0700 Subject: Landfill Updates for 2.20 Branch Message-ID: <1120953670.6840.4.camel@localhost.localdomain> Howdy! Well, we now have a bugzilla-2.20-branch install on landfill that's accessible from the main page. Also, using the /tools/ interface you can create a 2.20-branch install. Oh, and by the way, for anybody who hasn't looked at Tinderbox lately, or has been away for a bit: "The trunk is now OPEN for development approaching version 2.22. Checkins still require the approval flag to be set by justdave or myk, but in general we'll be pretty lenient." -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From mkanat at bugzilla.org Sun Jul 10 00:43:30 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 09 Jul 2005 17:43:30 -0700 Subject: Goals for 2.22 Message-ID: <1120956210.6840.11.camel@localhost.localdomain> OK! Originally, I think that I was hoping that we could have a LOT of stuff in Bugzilla 2.22, enough to call it 3.0. Due to our EXTREMELY delayed release of Bugzilla 2.20rc1, we don't have as much time as I'd hoped before our 2.22 freeze. However! I think that we may still have enough time to get the following things done: * mod_perl support (Bug 87406) * A Bug.pm that can write to the DB (bug 122922) * Basic Custom Fields * Eliminate SendSQL Of course, we won't hold the release for these things, but I think they're good things to shoot for and focus on. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From luis.villa at gmail.com Sun Jul 10 01:40:53 2005 From: luis.villa at gmail.com (Luis Villa) Date: Sat, 9 Jul 2005 21:40:53 -0400 Subject: Goals for 2.22 In-Reply-To: <1120956210.6840.11.camel@localhost.localdomain> References: <1120956210.6840.11.camel@localhost.localdomain> Message-ID: <2cb10c4405070918401af5bb84@mail.gmail.com> On 7/9/05, Max Kanat-Alexander wrote: > OK! Originally, I think that I was hoping that we could have a LOT of > stuff in Bugzilla 2.22, enough to call it 3.0. Due to our EXTREMELY > delayed release of Bugzilla 2.20rc1, we don't have as much time as I'd > hoped before our 2.22 freeze. FWIW, GNOME and KDE count their time-based releases from the date of their actual .0, not the planned .0- if X-1 slips, X slips too. Luis From mkanat at bugzilla.org Sun Jul 10 01:51:17 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 09 Jul 2005 18:51:17 -0700 Subject: Goals for 2.22 In-Reply-To: <2cb10c4405070918401af5bb84@mail.gmail.com> References: <1120956210.6840.11.camel@localhost.localdomain> <2cb10c4405070918401af5bb84@mail.gmail.com> Message-ID: <1120960277.6840.13.camel@localhost.localdomain> On Sat, 2005-07-09 at 21:40 -0400, Luis Villa wrote: > FWIW, GNOME and KDE count their time-based releases from the date of > their actual .0, not the planned .0- if X-1 slips, X slips too. It's up to justdave, but I think that we should try and keep our freeze goal for 2.22. It may be a small release, yes, but our branch maintenance times depend on our releases, and I don't really want to be maintaining 2.16 forever. :-) -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From luis.villa at gmail.com Sun Jul 10 02:01:23 2005 From: luis.villa at gmail.com (Luis Villa) Date: Sat, 9 Jul 2005 22:01:23 -0400 Subject: Goals for 2.22 In-Reply-To: <1120960277.6840.13.camel@localhost.localdomain> References: <1120956210.6840.11.camel@localhost.localdomain> <2cb10c4405070918401af5bb84@mail.gmail.com> <1120960277.6840.13.camel@localhost.localdomain> Message-ID: <2cb10c44050709190134a677b8@mail.gmail.com> On 7/9/05, Max Kanat-Alexander wrote: > On Sat, 2005-07-09 at 21:40 -0400, Luis Villa wrote: > > FWIW, GNOME and KDE count their time-based releases from the date of > > their actual .0, not the planned .0- if X-1 slips, X slips too. > > It's up to justdave, but I think that we should try and keep our freeze > goal for 2.22. It may be a small release, yes, And it's good in general to be content with small releases, IMHO :) > but our branch maintenance times depend on our releases, and I don't really want to be > maintaining 2.16 forever. :-) Is the plan to maintain a given release for X number of years, or to maintain X number of total releases at any one time? Luis From justdave at bugzilla.org Sun Jul 10 02:02:23 2005 From: justdave at bugzilla.org (David Miller) Date: Sat, 09 Jul 2005 22:02:23 -0400 Subject: Goals for 2.22 In-Reply-To: <1120960277.6840.13.camel@localhost.localdomain> References: <1120956210.6840.11.camel@localhost.localdomain> <2cb10c4405070918401af5bb84@mail.gmail.com> <1120960277.6840.13.camel@localhost.localdomain> Message-ID: <42D081AF.5040705@bugzilla.org> Max Kanat-Alexander wrote: > On Sat, 2005-07-09 at 21:40 -0400, Luis Villa wrote: > >>FWIW, GNOME and KDE count their time-based releases from the date of >>their actual .0, not the planned .0- if X-1 slips, X slips too. > > It's up to justdave, but I think that we should try and keep our freeze > goal for 2.22. It may be a small release, yes, but our branch > maintenance times depend on our releases, and I don't really want to be > maintaining 2.16 forever. :-) I'm with Max, the sooner we can drop 2.16 support, the better :) -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From mkanat at bugzilla.org Sun Jul 10 02:24:13 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 09 Jul 2005 19:24:13 -0700 Subject: Release Maintenance (WAS Re: Goals for 2.22) In-Reply-To: <2cb10c44050709190134a677b8@mail.gmail.com> References: <1120956210.6840.11.camel@localhost.localdomain> <2cb10c4405070918401af5bb84@mail.gmail.com> <1120960277.6840.13.camel@localhost.localdomain> <2cb10c44050709190134a677b8@mail.gmail.com> Message-ID: <1120962253.8180.8.camel@localhost.localdomain> On Sat, 2005-07-09 at 22:01 -0400, Luis Villa wrote: > Is the plan to maintain a given release for X number of years, or to > maintain X number of total releases at any one time? Well, I seem to recall the plan being to support releases on a basically time-based schedule, but that we'd be freezing on a time-based schedule anyhow... so I'm pretty sure it's for X number of releases. I'm pretty sure that our support period was planned to be 1.5 years (although that's probably too long), which would give us three branches and a trunk, with only one branch getting actual bugfixes *most* of the time, except during RC periods, where two branches would be getting standard bugfixes. Looking at that now, I think that's probably not fully realistic for the actual number of developers/reviewers that we have currently. :-) Perhaps a 12-month support period for a release would be better. Consultants could pick up the slack on old releases, if they so desired. People could probably start whole businesses around that, if they felt like it. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From justdave at bugzilla.org Sun Jul 10 02:36:08 2005 From: justdave at bugzilla.org (David Miller) Date: Sat, 09 Jul 2005 22:36:08 -0400 Subject: Goals for 2.22 In-Reply-To: <2cb10c44050709190134a677b8@mail.gmail.com> References: <1120956210.6840.11.camel@localhost.localdomain> <2cb10c4405070918401af5bb84@mail.gmail.com> <1120960277.6840.13.camel@localhost.localdomain> <2cb10c44050709190134a677b8@mail.gmail.com> Message-ID: <42D08998.7040706@bugzilla.org> Luis Villa wrote: > On 7/9/05, Max Kanat-Alexander wrote: > >>but our branch maintenance times depend on our releases, and I don't really want to be >>maintaining 2.16 forever. :-) > > Is the plan to maintain a given release for X number of years, or to > maintain X number of total releases at any one time? Option A: maintain a given release for X number of years (well, months, 18 to be exact). 2.16 is a special case because there was nothing to replace it with when that normal period would have expired, so we agreed we would wait until 2.22 came out to terminate support for it (given our switch to timed releases at the time, that would have given it 12 months after the version replacing it came out, except that 2.18 slipped so far it sort of became 18). We're going to do general bugfixes (but no feature enhancements) for 6 months into each release, and then security-only support for the following 12 months after that, which should give us 3 releases to maintain at any given time (plus the trunk), but only the current stable release will be getting bugfix support at any given time, the previous two will be security only. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From mkanat at bugzilla.org Sun Jul 10 19:00:41 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sun, 10 Jul 2005 12:00:41 -0700 Subject: Useful things to know about MySQL 4 Message-ID: <1121022042.5762.6.camel@localhost.localdomain> So, as many of us know, we will soon be requiring MySQL 4.0 for Bugzilla to run. (Actually, at least 4.0.2 and perhaps some higher version.) Here's a few things that are good to know about MySQL 4: + It has a query cache, but it doesn't work for "server-side prepared statements," per the MySQL docs. I'm not quite sure how this works with DBI, perhaps somebody else knows? + It supports UNION. So does PostgreSQL, so we can use UNION if it's necessary or makes life simpler. I know that PostgreSQL basically treats a UNION as two independent queries, performance-wise; I suspect MySQL does the same, but I'm not sure how it will use indexes in a UNION. + It has an expanded DELETE syntax that allows you to DELETE from multiple tables at once. I'm not sure how PostgreSQL is on this, but I suspect it probably works equally well on PostgreSQL. If you aren't familiar with what any of these things are, feel free to ask me here or in IRC and I'll try to explain. There are also some other useful features in MySQL4. You can see all the changelogs here: http://dev.mysql.com/doc/mysql/en/news-4-0-x.html -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From justdave at bugzilla.org Mon Jul 11 00:30:43 2005 From: justdave at bugzilla.org (David Miller) Date: Sun, 10 Jul 2005 20:30:43 -0400 Subject: handling blocking flags Message-ID: <42D1BDB3.8040100@bugzilla.org> Just so it doesn't catch anyone off-guard, I've told Max (mkanat) that he can grant/deny blocking flags and otherwise twiddle them (and given him the necessary privs to actually do so). Since he's actually the release manager, it only makes sense to give him the authority to be effective in his job. If you disagree with any of the decisions he makes in that regard, please get with me. You still need myself or Myk for approval flags. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From justdave at bugzilla.org Mon Jul 11 05:16:35 2005 From: justdave at bugzilla.org (David Miller) Date: Mon, 11 Jul 2005 01:16:35 -0400 Subject: We have a QA Manager! Message-ID: <42D200B3.4070005@bugzilla.org> Fr?d?ric Buclin (aka LpSolit) has graciously volunteered to head up our QA team for the Bugzilla project. I'd like to officially welcome him to the position. Note that I said "team" :) Bugzilla's too big for QA to be a one-man show anymore like it was when MattyT used to do it. Fr?d is going to need help, and if anyone wants to volunteer to help him out, I'm sure your help will be much appreciated. Just what exactly he needs your help with will get hashed out in the next day or two, but I'm imagining it'll be general discussion of QA practices in the beginning so we can nail down some good policies to keep us on the right track. I know the work will eventually involve actually testing Bugzilla :) -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From mkanat at bugzilla.org Mon Jul 11 05:28:05 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sun, 10 Jul 2005 22:28:05 -0700 Subject: We have a QA Manager! In-Reply-To: <42D200B3.4070005@bugzilla.org> References: <42D200B3.4070005@bugzilla.org> Message-ID: <1121059685.7852.2.camel@localhost.localdomain> On Mon, 2005-07-11 at 01:16 -0400, David Miller wrote: > Fr?d?ric Buclin (aka LpSolit) has graciously volunteered to head up our > QA team for the Bugzilla project. I'd like to officially welcome him to > the position. Great! :-) Glad to have you as QA Manager, LpSolit. :-) As far as Releases go, the things I'd really like to see in QA are twofold: (1) That the QA process doesn't significantly impact the speed of the Release Process. (A one-day delay is probably OK.) Releases are already really difficult to push through. (2) That they prevent us from having to do releases within two days of each other. :-) I'm quite excited that somebody is taking charge of actually doing Bugzilla QA. :-) I'll probably still triage a bug or two as it comes in, if nobody minds. :-) -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From gerv at mozilla.org Mon Jul 11 19:29:40 2005 From: gerv at mozilla.org (Gervase Markham) Date: Mon, 11 Jul 2005 20:29:40 +0100 Subject: Gerv's Whereabouts Message-ID: <42D2C8A4.6080102@mozilla.org> I've set up a Yahoo Calendar so it's easy to see when I'm working for the MoFo, when I'm working for Data Connection, and when I'm doing neither :-) http://calendar.yahoo.com/gervmarkham/ The rule of thumb is if the day begins with T, I'm working for the MoFo, unless I'm away. (I tried using the Hula project's public test installation for this, but I couldn't see how to publish calendars publicly.) Gerv From MDaskalov at technologica.com Mon Jul 11 19:51:59 2005 From: MDaskalov at technologica.com (Michael Daskalov) Date: Mon, 11 Jul 2005 22:51:59 +0300 Subject: Useful things to know about MySQL 4 Message-ID: <15F26D0D9E18E24583D912511D668FF8B637AB@exchange.ad.tlogica.com> Hi, about the following: + It has an expanded DELETE syntax that allows you to DELETE from multiple tables at once. I'm not sure how PostgreSQL is on this, but I suspect it probably works equally well on PostgreSQL. I don't know about multiple deletes in PostgreSQL, but for sure they are not supported in Oracle (and I think in DB2 and Sybase also), so I propose to not use them, just because the new MySQL 4 supports them. Regards, Mihail Daskalov -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Max Kanat-Alexander Sent: Sunday, July 10, 2005 10:01 PM To: developers at bugzilla.org Subject: Useful things to know about MySQL 4 So, as many of us know, we will soon be requiring MySQL 4.0 for Bugzilla to run. (Actually, at least 4.0.2 and perhaps some higher version.) Here's a few things that are good to know about MySQL 4: + It has a query cache, but it doesn't work for "server-side prepared statements," per the MySQL docs. I'm not quite sure how this works with DBI, perhaps somebody else knows? + It supports UNION. So does PostgreSQL, so we can use UNION if it's necessary or makes life simpler. I know that PostgreSQL basically treats a UNION as two independent queries, performance-wise; I suspect MySQL does the same, but I'm not sure how it will use indexes in a UNION. + It has an expanded DELETE syntax that allows you to DELETE from multiple tables at once. I'm not sure how PostgreSQL is on this, but I suspect it probably works equally well on PostgreSQL. If you aren't familiar with what any of these things are, feel free to ask me here or in IRC and I'll try to explain. There are also some other useful features in MySQL4. You can see all the changelogs here: http://dev.mysql.com/doc/mysql/en/news-4-0-x.html -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. - To view or change your list settings, click here: From gerv at mozilla.org Mon Jul 11 21:01:13 2005 From: gerv at mozilla.org (Gervase Markham) Date: Mon, 11 Jul 2005 22:01:13 +0100 Subject: We have a QA Manager! In-Reply-To: <1121059685.7852.2.camel@localhost.localdomain> References: <42D200B3.4070005@bugzilla.org> <1121059685.7852.2.camel@localhost.localdomain> Message-ID: <42D2DE19.60507@mozilla.org> Max Kanat-Alexander wrote: > As far as Releases go, the things I'd really like to see in QA are > twofold: > > (1) That the QA process doesn't significantly impact the speed of the > Release Process. (A one-day delay is probably OK.) Releases are already > really difficult to push through. On the contrary; if we have to hold up a release a couple of days to avoid your point 2), I think that's a great trade. I would hope it would be possible to have a QA process which didn't need that, but I don't think it's a requirement. Gerv From myk at mozilla.org Mon Jul 11 21:06:02 2005 From: myk at mozilla.org (Myk Melez) Date: Mon, 11 Jul 2005 14:06:02 -0700 Subject: We have a QA Manager! In-Reply-To: <42D2DE19.60507@mozilla.org> References: <42D200B3.4070005@bugzilla.org> <1121059685.7852.2.camel@localhost.localdomain> <42D2DE19.60507@mozilla.org> Message-ID: <42D2DF3A.1040801@mozilla.org> Gervase Markham wrote: > On the contrary; if we have to hold up a release a couple of days to > avoid your point 2), I think that's a great trade. > > I would hope it would be possible to have a QA process which didn't > need that, but I don't think it's a requirement. Are we still blocked (as we were a few years ago) on moving Bugzilla bugs to their own installation running the (or close to the) tip? Eating our own dogfood would be an excellent way of ensuring at least the tip stays stable, even if it doesn't help on branches. -myk From gerv at mozilla.org Mon Jul 11 21:16:41 2005 From: gerv at mozilla.org (Gervase Markham) Date: Mon, 11 Jul 2005 22:16:41 +0100 Subject: Release Maintenance (WAS Re: Goals for 2.22) In-Reply-To: <1120962253.8180.8.camel@localhost.localdomain> References: <1120956210.6840.11.camel@localhost.localdomain> <2cb10c4405070918401af5bb84@mail.gmail.com> <1120960277.6840.13.camel@localhost.localdomain> <2cb10c44050709190134a677b8@mail.gmail.com> <1120962253.8180.8.camel@localhost.localdomain> Message-ID: <42D2E1B9.2010902@mozilla.org> Max Kanat-Alexander wrote: > Perhaps a 12-month support period for a release would be better. > Consultants could pick up the slack on old releases, if they so desired. > People could probably start whole businesses around that, if they felt > like it. The alternative is an 18-month support period but with 9-month releases instead of six. Yet another alternative is picking one release to be "long-lived (e.g. 2.18) and only supporting the in-between releases for next-release-plus-three-months. Gerv From gerv at mozilla.org Mon Jul 11 21:17:52 2005 From: gerv at mozilla.org (Gervase Markham) Date: Mon, 11 Jul 2005 22:17:52 +0100 Subject: The state of charting Message-ID: <42D2E200.60104@mozilla.org> [This is the third time I've tried to send this! Fat fingers...] [Update: since I wrote this, you've branched for 2.20. How does that affect things?] Dear developers, First, an apology for having dropped the ball on New Charts for so long. I understand that at least one New Charts-related bug is a release blocker. I'd like to knock them into shape, and work out the minimum possible work to do that. I'd like feedback on whether this is the right approach, and whether it fits with current release plans, or if it's too much too late - and, if so, what an alternative plan might be. The major change I feel is necessary is to link products directly to their series categories. I made an original design decision not to do this; it was probably the wrong one. People expect the category name to change if the product gets renamed, and for the category to pick up the product's visibility. There are several technical issues - for example, how do you merge product IDs (1-based, incrementing) with category IDs (1-based, incrementing) without clashes? How do you migrate from where we are to establishing a link? There's no bug number for this, but it would reduce the need for the UI planned in bug 257346 (the release blocker). I also want to: - Remove the "frequency" stuff - it's over-engineered and causes display problems when showing series with different frequencies. Bug 288148 and bug 238835. - Improve debuggability - we get loads of questions in the newsgroups. Bug 286724 and any other ideas people might have. - Change the idea of a "creator" to an "owner", and allow admins to change who it is. This solves some practical issues. Bug 288150 or bug 257350. What do you think? Gerv From mkanat at bugzilla.org Mon Jul 11 21:41:36 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Mon, 11 Jul 2005 14:41:36 -0700 Subject: Useful things to know about MySQL 4 In-Reply-To: <15F26D0D9E18E24583D912511D668FF8B637AB@exchange.ad.tlogica.com> References: <15F26D0D9E18E24583D912511D668FF8B637AB@exchange.ad.tlogica.com> Message-ID: <1121118096.5487.4.camel@localhost.localdomain> On Mon, 2005-07-11 at 22:51 +0300, Michael Daskalov wrote: > I don't know about multiple deletes in PostgreSQL, but for sure they are > not supported in Oracle (and I think in DB2 and Sybase also), > so I propose to not use them, just because the new MySQL 4 supports > them. I agree. They're a bit strange to use anyway, and they won't really make our lives a whole lot easier. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From mkanat at bugzilla.org Mon Jul 11 22:15:51 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Mon, 11 Jul 2005 15:15:51 -0700 Subject: The state of charting In-Reply-To: <42D2E200.60104@mozilla.org> References: <42D2E200.60104@mozilla.org> Message-ID: <1121120151.5487.10.camel@localhost.localdomain> On Mon, 2005-07-11 at 22:17 +0100, Gervase Markham wrote: > I'd like to knock them into shape, and work out the minimum possible > work to do that. I'd like feedback on whether this is the right > approach, and whether it fits with current release plans, or if it's too > much too late - and, if so, what an alternative plan might be. It's definitely not too late to work out the two release blockers, I think. Those are bug 247936 and bug 276230. > The major change I feel is necessary is to link products directly to > their series categories. I fully agree, but I think it's probably too late in the 2.20 development cycle to do that. Also, even the 2.18 branch has a blocker on bug 276230. > There's no bug number for this, but it would reduce the need for the UI > planned in bug 257346 (the release blocker). Hrm... well, I think probably if you think that that re-work would be *less* invasive to existing code than creating a UI, I'd say to go for it. My concern is changing code that works, and having that push off the release. At the least, we'd have to have another RC. Or, alternately, we could ship another release without bug 276230, and push it entirely off to 2.22, with a guarantee of it being there (since you're available to code on it). > [snip] > What do you think? I think all your ideas sound great, personally. :-) I'm all for simplifying things. :-) Most of them sound like 2.22-cycle stuff, of course. :-) -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From bugzilla at glob.com.au Tue Jul 12 02:46:06 2005 From: bugzilla at glob.com.au (byron) Date: Tue, 12 Jul 2005 10:46:06 +0800 (WST) Subject: We have a QA Manager! Message-ID: <20050712024606.48A1F4BC961@sweep.bur.st> > Are we still blocked (as we were a few years ago) on moving Bugzilla > bugs to their own installation running the (or close to the) tip? > Eating our own dogfood would be an excellent way of ensuring at least > the tip stays stable, even if it doesn't help on branches. that's a good idea. -b begin-base64 644 signature.gif R0lGODlhbQAHAIAAAABPo////ywAAAAAbQAHAAACfAxuGAnch+Bibkn7FL1p XgVl4Ig1jjlZRoqybgun2Cur5uOunq7u/Ipq7WIyIc7XG9JquEgumPzdlhTf h0O83kDJaXEm8mRHwXKJy5sac7qYOpT+gtv0n+0ujQOfdqh16caWt0foBViH N1PRMXimiLUGt3ElVimlgbllWAAAOw== ==== From mkanat at bugzilla.org Tue Jul 12 03:00:08 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Mon, 11 Jul 2005 20:00:08 -0700 Subject: We have a QA Manager! In-Reply-To: <20050712024606.48A1F4BC961@sweep.bur.st> References: <20050712024606.48A1F4BC961@sweep.bur.st> Message-ID: <1121137208.5496.6.camel@localhost.localdomain> On Tue, 2005-07-12 at 10:46 +0800, byron wrote: > > Are we still blocked (as we were a few years ago) on moving Bugzilla > > bugs to their own installation running the (or close to the) tip? > > Eating our own dogfood would be an excellent way of ensuring at least > > the tip stays stable, even if it doesn't help on branches. > > that's a good idea. Yeah, and it would make us keep the move.pl and importxml.pl scripts actually up-to-date, for moving certain bugs back to Products on bmo. :-) That's definitely an area where we could use some dogfood. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From mkanat at bugzilla.org Tue Jul 12 05:29:30 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Mon, 11 Jul 2005 22:29:30 -0700 Subject: landfill: pgclone and pgdrop Message-ID: <1121146170.5496.11.camel@localhost.localdomain> PostgreSQL now has the same tools that MySQL has, on landfill. pgclone - Copies a database on Pg to another, brand- new DB. pgdrop - Drops a database in PostgreSQL. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From vladd at bugzilla.org Tue Jul 12 05:36:38 2005 From: vladd at bugzilla.org (Vlad Dascalu) Date: Tue, 12 Jul 2005 08:36:38 +0300 Subject: Commercial advertisments (signatures) in public announcements Message-ID: <42D356E6.90703@bugzilla.org> Hello, I'm worried about using commercial advertisments in the signatures of our public official announcements and security advisories. I've started this based on Mkanat's signature in the 2.18.3 announcement, in which he advertises his company at the bottom of the announcement. I do think we should avoid this path. Rewarding Bugzilla contributions with the ability to promote your own company is a road that I'd like to avoid. But I'd thought I'd ask for feedback. :-) It's "only" a signature, but, nonetheless, I do think that official Bugzilla announcements or other official emails, sent in the name of the Bugzilla team, should not promote a company or a service. We already have a page for those, where we list them, more or less equaly. I do remember the idea of Google Ads for financial support, but we even dropped that one. Thanks, Vlad. From mkanat at bugzilla.org Tue Jul 12 06:07:05 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Mon, 11 Jul 2005 23:07:05 -0700 Subject: Commercial advertisments (signatures) in public announcements In-Reply-To: <42D356E6.90703@bugzilla.org> References: <42D356E6.90703@bugzilla.org> Message-ID: <1121148425.5496.15.camel@localhost.localdomain> On Tue, 2005-07-12 at 08:36 +0300, Vlad Dascalu wrote: > I've started this based on Mkanat's signature in the 2.18.3 > announcement, in which he advertises his company at the bottom of the > announcement. > > I do think we should avoid this path. Rewarding Bugzilla contributions > with the ability to promote your own company is a road that I'd like to > avoid. But I'd thought I'd ask for feedback. :-) Yeah. Actually, I left that in there on purpose. I spend hours and hours doing release management of Bugzilla for absolutely free. The only small compensation that I receive is the signature in the announcements. I used to remove it, because I agreed with you. However, I think it doesn't hurt to slightly recompense me for the amount of time that I put into the release process, without which we may never have released anything starting with 2.18 onward. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From justdave at bugzilla.org Tue Jul 12 06:34:30 2005 From: justdave at bugzilla.org (David Miller) Date: Tue, 12 Jul 2005 02:34:30 -0400 Subject: Commercial advertisments (signatures) in public announcements In-Reply-To: <42D356E6.90703@bugzilla.org> References: <42D356E6.90703@bugzilla.org> Message-ID: <42D36476.8030200@bugzilla.org> Vlad Dascalu wrote: > I'm worried about using commercial advertisments in the signatures of > our public official announcements and security advisories. > > I've started this based on Mkanat's signature in the 2.18.3 > announcement, in which he advertises his company at the bottom of the > announcement. > > I do think we should avoid this path. Rewarding Bugzilla contributions > with the ability to promote your own company is a road that I'd like to > avoid. But I'd thought I'd ask for feedback. :-) Looking back in history, I see my signatures on the release announcements included a link to Syndicomm when I was working there, and as you see below, there's a link to mozilla.org now (my current employer). But that's what's always in my signature, and I just didn't think to turn it off or change it. But yes, it's probably best if we keep commercial references out of our official announcements unless they're related to the announcement. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From gerv at mozilla.org Tue Jul 12 08:22:12 2005 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 12 Jul 2005 09:22:12 +0100 Subject: Commercial advertisments (signatures) in public announcements In-Reply-To: <42D36476.8030200@bugzilla.org> References: <42D356E6.90703@bugzilla.org> <42D36476.8030200@bugzilla.org> Message-ID: <42D37DB4.1020000@mozilla.org> David Miller wrote: > Looking back in history, I see my signatures on the release > announcements included a link to Syndicomm when I was working there, and > as you see below, there's a link to mozilla.org now (my current > employer). But that's what's always in my signature, and I just didn't > think to turn it off or change it. On the other hand, Syndicomm didn't do Bugzilla work and your sig wasn't an ad for consulting services... I see Max's point about being compensated for the work he does, but I think that anyone who has any connection with Bugzilla and who drops by the newsgroup will see him answering questions with his sig there in its full glory. :-) Lots of people contribute to Bugzilla in different ways and, while I am very pleased that Max has taken on the job of making releases, in hindsight it seems a bit unfair on people who "just" do back-end work but also offer consulting services. Gerv From mkanat at bugzilla.org Tue Jul 12 08:36:59 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 12 Jul 2005 01:36:59 -0700 Subject: landfill: /tools/ now understands PostgreSQL Message-ID: <1121157420.5496.25.camel@localhost.localdomain> You can now use the standard landfill test-install-creating tools to create a Bugzilla that runs on PostgreSQL, in addition to MySQL. http://landfill.bugzilla.org/tools/ -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From gerv at mozilla.org Tue Jul 12 10:43:22 2005 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 12 Jul 2005 11:43:22 +0100 Subject: The state of charting In-Reply-To: <1121120151.5487.10.camel@localhost.localdomain> References: <42D2E200.60104@mozilla.org> <1121120151.5487.10.camel@localhost.localdomain> Message-ID: <42D39ECA.9070607@mozilla.org> Max Kanat-Alexander wrote: > It's definitely not too late to work out the two release blockers, I > think. Those are bug 247936 and bug 276230. These two bugs cut right to the heart of things. The first one is about series going away when products go away. Currently, with no official link between the two, it's not obvious what should happen. The current behaviour is arguably the correct one. The second is about setting groups on categories - but really, it's about syncing the groups of categories with their matching products. Again, establishing the link would solve the problem and mean we didn't need extra UI. Much nicer. > Hrm... well, I think probably if you think that that re-work would be > *less* invasive to existing code than creating a UI, I'd say to go for > it. It's hard to say. I think we need to figure out a technical plan for associating products with their categories, and see how invasive it is. > Or, alternately, we could ship another release without bug 276230, and > push it entirely off to 2.22, with a guarantee of it being there (since > you're available to code on it). We could always do that - particularly if we plan a short 2.22 (famous last words). Gerv From gerv at mozilla.org Tue Jul 12 10:49:13 2005 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 12 Jul 2005 11:49:13 +0100 Subject: We have a QA Manager! In-Reply-To: <42D2DF3A.1040801@mozilla.org> References: <42D200B3.4070005@bugzilla.org> <1121059685.7852.2.camel@localhost.localdomain> <42D2DE19.60507@mozilla.org> <42D2DF3A.1040801@mozilla.org> Message-ID: <42D3A029.5020601@mozilla.org> Myk Melez wrote: > Are we still blocked (as we were a few years ago) on moving Bugzilla > bugs to their own installation running the (or close to the) tip? > Eating our own dogfood would be an excellent way of ensuring at least > the tip stays stable, even if it doesn't help on branches. Come on, let's work this out. What do we need? - A lossless way of moving bugs between installations (i.e. each comment becomes a separate comment, attachments move, etc.) - Upgrade b.m.o. to a version supporting that. - Install a new installation just for us. - Move the bugs across, and redirect potential bug filers. The first thing is the important one. Bug moving is currently a real mess, and not well maintained. I suggest we abandon that, and do the following: - Make it possible to do all-info XML export (inc. attachments and everything) - Make it possible to do all-info XML import, as if a new bug had been filed and a load of comments and attachments added. Have a mode which ignores some errors, like missing accounts for CC list members. This is a reasonably big project. Gerv From Guillaume.Rousse at inria.fr Tue Jul 12 11:31:51 2005 From: Guillaume.Rousse at inria.fr (Guillaume Rousse) Date: Tue, 12 Jul 2005 13:31:51 +0200 Subject: landfill: /tools/ now understands PostgreSQL In-Reply-To: <1121157420.5496.25.camel@localhost.localdomain> References: <1121157420.5496.25.camel@localhost.localdomain> Message-ID: <42D3AA27.4040506@inria.fr> Max Kanat-Alexander wrote: > You can now use the standard landfill test-install-creating tools to > create a Bugzilla that runs on PostgreSQL, in addition to MySQL. > > http://landfill.bugzilla.org/tools/ Maybe a stupid question (I didn't even attempted to read the code), but as bugzilla is using DBI instead of native drivers, why are you tied to PostgreSQL or MySQL rather than to any supported database ? Are there so much non-standard SQL constructs? -- If at first you don't succeed, call in an airstrike -- Murphy's Military Laws n?115 From Guillaume.Rousse at inria.fr Tue Jul 12 11:47:38 2005 From: Guillaume.Rousse at inria.fr (Guillaume Rousse) Date: Tue, 12 Jul 2005 13:47:38 +0200 Subject: Potential contribution: owner exchange Message-ID: <42D3ADDA.80908@inria.fr> We are using bugzilla for packaging projects, such as PLF (plf.zarb.org) or jpackage (jpackage.org). I developped a specific script to allows packagers to drop and pick maintainership of their packages, and the code is available at http://www.zarb.org/cgi-bin/viewcvs.cgi/youri/bugzilla/maintainers.cgi?rev=1.1&view=log I'd be happy to contribute it upstream, but there is a slight problem: I cheated with default bugzilla database model, where only product have version, and only components have owners. I mapped packages to product, and use ghost components with the same owner to achieve something more adapted to our needs. So, I guess it is a bit too much specific to be interesting directly, but if there is any interest, I think I'd have just to change the SQL queries to make it suitable. BTW, is there any provision for people that like to use non-standard database model for specific purposes ? -- Never tell the Captain or Deputy Captain you have nothing to do -- Murphy's Military Laws n?61 From mkanat at bugzilla.org Tue Jul 12 12:22:52 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 12 Jul 2005 05:22:52 -0700 Subject: landfill: /tools/ now understands PostgreSQL In-Reply-To: <42D3AA27.4040506@inria.fr> References: <1121157420.5496.25.camel@localhost.localdomain> <42D3AA27.4040506@inria.fr> Message-ID: <1121170972.5457.18.camel@localhost.localdomain> On Tue, 2005-07-12 at 13:31 +0200, Guillaume Rousse wrote: > Maybe a stupid question (I didn't even attempted to read the code), but > as bugzilla is using DBI instead of native drivers, why are you tied to > PostgreSQL or MySQL rather than to any supported database ? Are there so > much non-standard SQL constructs? The problem isn't so much non-standard constructs as it is the fact that almost no database fully supports ANSI SQL. That is, we could write Bugzilla to be totally ANSI, and then no database would support it. :-) MySQL, in particular, is quite far from full ANSI support. Most of the work involved to get Bugzilla to support PostgreSQL was in making as much of Bugzilla's SQL ANSI-compliant as possible. So yes, now that we support PostgreSQL, supporting other databases should be much easier. However, every database system has its quirks, and so every time we want to support another database, we have to make some adjustments to Bugzilla itself. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From luis.villa at gmail.com Tue Jul 12 12:29:17 2005 From: luis.villa at gmail.com (Luis Villa) Date: Tue, 12 Jul 2005 08:29:17 -0400 Subject: We have a QA Manager! In-Reply-To: <42D3A029.5020601@mozilla.org> References: <42D200B3.4070005@bugzilla.org> <1121059685.7852.2.camel@localhost.localdomain> <42D2DE19.60507@mozilla.org> <42D2DF3A.1040801@mozilla.org> <42D3A029.5020601@mozilla.org> Message-ID: <2cb10c44050712052932b6a167@mail.gmail.com> On 7/12/05, Gervase Markham wrote: > Myk Melez wrote: > > Are we still blocked (as we were a few years ago) on moving Bugzilla > > bugs to their own installation running the (or close to the) tip? > > Eating our own dogfood would be an excellent way of ensuring at least > > the tip stays stable, even if it doesn't help on branches. > > Come on, let's work this out. What do we need? > > - A lossless way of moving bugs between installations (i.e. each comment > becomes a separate comment, attachments move, etc.) > > - Upgrade b.m.o. to a version supporting that. > > - Install a new installation just for us. > > - Move the bugs across, and redirect potential bug filers. > > The first thing is the important one. Bug moving is currently a real > mess, and not well maintained. I suggest we abandon that, and do the > following: > > - Make it possible to do all-info XML export (inc. attachments and > everything) > > - Make it possible to do all-info XML import, as if a new bug had been > filed and a load of comments and attachments added. Have a mode which > ignores some errors, like missing accounts for CC list members. Can I suggest finishing up XML-RPC bug writing instead? Adding an imported bug/comment should just be a special case of the more general XML-RPC mechanism, not its own mechanism, it seems to me. Luis From chicks at chicks.net Tue Jul 12 13:10:41 2005 From: chicks at chicks.net (Christopher Hicks) Date: Tue, 12 Jul 2005 09:10:41 -0400 (EDT) Subject: Commercial advertisments (signatures) in public announcements In-Reply-To: <42D356E6.90703@bugzilla.org> References: <42D356E6.90703@bugzilla.org> Message-ID: On Tue, 12 Jul 2005, Vlad Dascalu wrote: > I'm worried about using commercial advertisments in the signatures of our > public official announcements and security advisories. > > It's "only" a signature, but, nonetheless, I do think that official Bugzilla > announcements or other official emails, sent in the name of the Bugzilla > team, should not promote a company or a service. We already have a page for > those, where we list them, more or less equaly. I do remember the idea of > Google Ads for financial support, but we even dropped that one. A signature is typically a place for personal expression. Whether that expression is political, religious, humorous, or commercial its the personal expression of the person. Even mkanat recognized that some extra consideration should be made about the appropriateness of sigs while functioning in an official BZ role by removing it for sometime. But beyond that if its clearly part of the signature and not part of body then it seems to be associated with that person personally and not part of their official execution of duty. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) From kevin.benton at amd.com Tue Jul 12 14:13:20 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Tue, 12 Jul 2005 07:13:20 -0700 Subject: We have a QA Manager! Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE02F@ssvlexmb2.amd.com> > Myk Melez wrote: > > Are we still blocked (as we were a few years ago) on moving Bugzilla > > bugs to their own installation running the (or close to the) tip? > > Eating our own dogfood would be an excellent way of ensuring at least > > the tip stays stable, even if it doesn't help on branches. > > Come on, let's work this out. What do we need? > > - A lossless way of moving bugs between installations (i.e. each comment > becomes a separate comment, attachments move, etc.) > > - Upgrade b.m.o. to a version supporting that. > > - Install a new installation just for us. > > - Move the bugs across, and redirect potential bug filers. > > The first thing is the important one. Bug moving is currently a real > mess, and not well maintained. I suggest we abandon that, and do the > following: > > - Make it possible to do all-info XML export (inc. attachments and > everything) > > - Make it possible to do all-info XML import, as if a new bug had been > filed and a load of comments and attachments added. Have a mode which > ignores some errors, like missing accounts for CC list members. > > This is a reasonably big project. I agree. Don't forget, many also rely on existing bug numbers so migration might need to include turning off auto-increment for the bugs table during the migration. --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. From gerv at mozilla.org Tue Jul 12 14:25:50 2005 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 12 Jul 2005 15:25:50 +0100 Subject: We have a QA Manager! In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE02F@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE02F@ssvlexmb2.amd.com> Message-ID: <42D3D2EE.2090203@mozilla.org> Benton, Kevin wrote: > Don't forget, many also rely on existing bug numbers so migration might > need to include turning off auto-increment for the bugs table during the > migration. Urk - please, no :-) We can't try and match bug numbers up. That way lies madness. A better solution would be for a bug which is RESOLVED MOVED to automatically redirect to the new bug in the new Bugzilla... but perhaps some people wouldn't like that. Gerv From kevin.benton at amd.com Tue Jul 12 14:37:05 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Tue, 12 Jul 2005 07:37:05 -0700 Subject: RESOLVED/... (was RE: We have a QA Manager!) Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE044@ssvlexmb2.amd.com> > Benton, Kevin wrote: > > Don't forget, many also rely on existing bug numbers so migration might > > need to include turning off auto-increment for the bugs table during the > > migration. > > Urk - please, no :-) We can't try and match bug numbers up. That way > lies madness. > > A better solution would be for a bug which is RESOLVED MOVED to > automatically redirect to the new bug in the new Bugzilla... but perhaps > some people wouldn't like that. EWWW! Since you brought it up, I think this RESOLVED/LATER and RESOLVED/... for things that really don't resolve the issue should be changed to something that tells the real story, especially for process monitoring software. It's difficult to handle "stopping the performance clock" properly with RESOLVED since it doesn't always (in Bugzilla) mean the issue is truly resolved. Also, our process dings people when things get reopened, so having them go to RESOLVED/LATER then to an active status dings the assignee for "not handling the bug properly the first time." It seems we ought to look this whole thing over from a process management perspective. --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. From gerv at mozilla.org Tue Jul 12 14:39:56 2005 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 12 Jul 2005 15:39:56 +0100 Subject: RESOLVED/... (was RE: We have a QA Manager!) In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE044@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE044@ssvlexmb2.amd.com> Message-ID: <42D3D63C.8030106@mozilla.org> Benton, Kevin wrote: > EWWW! Since you brought it up, I think this RESOLVED/LATER and > RESOLVED/... for things that really don't resolve the issue should be > changed to something that tells the real story, especially for process > monitoring software. I completely agree about REMIND and LATER, but I do think that MOVED is a resolution, because it means that no further work should be done on this bug in this place. Gerv From luis.villa at gmail.com Tue Jul 12 14:46:56 2005 From: luis.villa at gmail.com (Luis Villa) Date: Tue, 12 Jul 2005 10:46:56 -0400 Subject: RESOLVED/... (was RE: We have a QA Manager!) In-Reply-To: <42D3D63C.8030106@mozilla.org> References: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE044@ssvlexmb2.amd.com> <42D3D63C.8030106@mozilla.org> Message-ID: <2cb10c4405071207464e88b295@mail.gmail.com> On 7/12/05, Gervase Markham wrote: > Benton, Kevin wrote: > > EWWW! Since you brought it up, I think this RESOLVED/LATER and > > RESOLVED/... for things that really don't resolve the issue should be > > changed to something that tells the real story, especially for process > > monitoring software. > > I completely agree about REMIND and LATER, but I do think that MOVED is > a resolution, because it means that no further work should be done on > this bug in this place. Thirded. Does this mean we can get a patch for bug 13534 into 2.20? Luis (who realizes that Kevin is a newbie, and so has an excuse for not realizing there has been a bug open about REMIND/LATER for *six years*.) From luis.villa at gmail.com Tue Jul 12 14:48:16 2005 From: luis.villa at gmail.com (Luis Villa) Date: Tue, 12 Jul 2005 10:48:16 -0400 Subject: RESOLVED/... (was RE: We have a QA Manager!) In-Reply-To: <2cb10c4405071207464e88b295@mail.gmail.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE044@ssvlexmb2.amd.com> <42D3D63C.8030106@mozilla.org> <2cb10c4405071207464e88b295@mail.gmail.com> Message-ID: <2cb10c4405071207482f29a218@mail.gmail.com> On 7/12/05, Luis Villa wrote: > On 7/12/05, Gervase Markham wrote: > > Benton, Kevin wrote: > > > EWWW! Since you brought it up, I think this RESOLVED/LATER and > > > RESOLVED/... for things that really don't resolve the issue should be > > > changed to something that tells the real story, especially for process > > > monitoring software. > > > > I completely agree about REMIND and LATER, but I do think that MOVED is > > a resolution, because it means that no further work should be done on > > this bug in this place. > > Thirded. Does this mean we can get a patch for bug 13534 into 2.20? > > Luis (who realizes that Kevin is a newbie, and so has an excuse for > not realizing there has been a bug open about REMIND/LATER for *six > years*.) Hrm. This may not have come out quite right, probably should have put newbie in quotes. Kevin is only a newbie relative to the age of that completely embarassing bug. Luis From luis.villa at gmail.com Tue Jul 12 15:41:11 2005 From: luis.villa at gmail.com (Luis Villa) Date: Tue, 12 Jul 2005 11:41:11 -0400 Subject: mouseover help busted? Message-ID: <2cb10c440507120841312768b3@mail.gmail.com> Poking at landfill with firefox 1.0.4/linux, the tooltip help: http://landfill.bugzilla.org/bugzilla-2.20-branch/query.cgi?help=1&format=advanced doesn't come up for me. Anyone know offhand if this is a bugzilla or a firefox problem? Thanks- Luis From luis.villa at gmail.com Tue Jul 12 15:44:22 2005 From: luis.villa at gmail.com (Luis Villa) Date: Tue, 12 Jul 2005 11:44:22 -0400 Subject: mouseover help busted? In-Reply-To: <2cb10c440507120841312768b3@mail.gmail.com> References: <2cb10c440507120841312768b3@mail.gmail.com> Message-ID: <2cb10c440507120844b0aab1c@mail.gmail.com> On 7/12/05, Luis Villa wrote: > Poking at landfill with firefox 1.0.4/linux, the tooltip help: > > http://landfill.bugzilla.org/bugzilla-2.20-branch/query.cgi?help=1&format=advanced > > doesn't come up for me. Ah-ha, I lied. They do come up. But only at the bottom of the page- you have to scroll down to see them. Bugzilla doing the wrong thing, I assume? Luis From reks at iiap.res.in Tue Jul 12 15:53:41 2005 From: reks at iiap.res.in (Rekhesh Mohan) Date: Tue, 12 Jul 2005 21:23:41 +0530 (IST) Subject: mouseover help busted? In-Reply-To: <2cb10c440507120841312768b3@mail.gmail.com> Message-ID: On Tue, 12 Jul 2005, Luis Villa wrote: > Poking at landfill with firefox 1.0.4/linux, the tooltip help: > > http://landfill.bugzilla.org/bugzilla-2.20-branch/query.cgi?help=1&format=advanced > > doesn't come up for me. Anyone know offhand if this is a bugzilla or a > firefox problem? > Tooltip (with firefox) is appearing at the bottom of the page! Incidently, why are we using javascript for tooltips? Isn't it possible with " along with some css to make it noticable? --Reks -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean. From luis.villa at gmail.com Tue Jul 12 15:10:34 2005 From: luis.villa at gmail.com (Luis Villa) Date: Tue, 12 Jul 2005 11:10:34 -0400 Subject: REMIND and LATER considered harmful [was Re: RESOLVED] In-Reply-To: <2cb10c4405071207464e88b295@mail.gmail.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE044@ssvlexmb2.amd.com> <42D3D63C.8030106@mozilla.org> <2cb10c4405071207464e88b295@mail.gmail.com> Message-ID: <2cb10c440507120810543edf60@mail.gmail.com> On 7/12/05, Luis Villa wrote: > On 7/12/05, Gervase Markham wrote: > > Benton, Kevin wrote: > > > EWWW! Since you brought it up, I think this RESOLVED/LATER and > > > RESOLVED/... for things that really don't resolve the issue should be > > > changed to something that tells the real story, especially for process > > > monitoring software. > > > > I completely agree about REMIND and LATER, but I do think that MOVED is > > a resolution, because it means that no further work should be done on > > this bug in this place. > > Thirded. Does this mean we can get a patch for bug 13534 into 2.20? Note that I'm looking at this right now, but... guh, I've never touched checksetup.pl, and I suddenly have the nagging feeling that getting this Right in the upgrade case will be hard. (It is easy in the clean install case, I can likely throw up some patches to do that before lunch, including for docs.) Luis P.S. The reason I get pissy about this is that I believe firmly that software should be useful out of the box, and we've shipped now for six years with defaults that we acknowledge are deeply broken. It makes it harder to recommend bugzilla when I've had very smart people come to me and say 'well, I just installed bugzilla like you told me, and there are these weird resolutions- but I know there must be a reason for them, or else why would they be in bugzilla? I guess we'll just figure out how to use them.' From kevin.benton at amd.com Tue Jul 12 17:21:38 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Tue, 12 Jul 2005 10:21:38 -0700 Subject: REMIND and LATER considered harmful [was Re: RESOLVED] Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE0C9@ssvlexmb2.amd.com> Just thinking out loud... > On 7/12/05, Luis Villa wrote: > > On 7/12/05, Gervase Markham wrote: > > > Benton, Kevin wrote: > > > > EWWW! Since you brought it up, I think this RESOLVED/LATER and > > > > RESOLVED/... for things that really don't resolve the issue should > be > > > > changed to something that tells the real story, especially for > process > > > > monitoring software. > > > > > > I completely agree about REMIND and LATER, but I do think that MOVED > is > > > a resolution, because it means that no further work should be done on > > > this bug in this place. > > > > Thirded. Does this mean we can get a patch for bug 13534 into 2.20? > > Note that I'm looking at this right now, but... guh, I've never > touched checksetup.pl, and I suddenly have the nagging feeling that > getting this Right in the upgrade case will be hard. (It is easy in > the clean install case, I can likely throw up some patches to do that > before lunch, including for docs.) Thanks :) After any such changes were made, it seems to me that we'd also need to have a pending reason along with a date the status is expected to change from PENDING to ASSIGNED. > P.S. The reason I get pissy about this is that I believe firmly that > software should be useful out of the box, and we've shipped now for > six years with defaults that we acknowledge are deeply broken. It > makes it harder to recommend bugzilla when I've had very smart people > come to me and say 'well, I just installed bugzilla like you told me, > and there are these weird resolutions- but I know there must be a > reason for them, or else why would they be in bugzilla? I guess we'll > just figure out how to use them.' I agree. The challenge is - producing useful software first, then tuning it. I don't have a problem with how REMIND and LATER were implemented at the time and I'm sure the person who developed it thought that having a "PENDING" status would also be nice, but they probably weren't ready to code it at the time. I think, if we have PENDING, we could easily reuse the resolution field (assuming it gets converted to an index rather than an enum - which may have already happened), changing its name to status_info. With a PENDING status, I would hope we'd also implement comentonpending in the configuration section as putting a status into PENDING requires more information. I'd also hope we'd somehow implement (maybe in a second phase) automatic status changes to take a bug out of PENDING after a pre-defined period. In my view, there are two types of transitions that could be made to PENDING. First, is from NEW/ASSIGNED to PENDING where an engineer has acknowledged the bug but is not able to (for whatever reason) handle the issue immediately. The other transition into a PENDING status is when QA is similarly awaiting information and unable to handle the issue immediately. From my perspective, PENDING is not an excuse to stop the clock. PENDING is meant only for situations where the bug owner is waiting on something outside his/her control and not able to move forward until that other piece is resolved. In my mind, a bug could be pending: Customer or Third Party Feedback Customer or Third Party Action Review Approval Another Bug (in which case it should reference the bug or bugs - depends_on) Other (catch-all for things I haven't thought of - would need to be policed, however). --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. From dwilliss at microimages.com Wed Jul 13 14:06:34 2005 From: dwilliss at microimages.com (Dave Williss) Date: Wed, 13 Jul 2005 09:06:34 -0500 Subject: REMIND and LATER considered harmful [was Re: RESOLVED] References: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE0C9@ssvlexmb2.amd.com> Message-ID: <561e01c587b4$1717dcb0$4b00000a@opus2> ----- Original Message ----- From: "Benton, Kevin" To: Sent: Tuesday, July 12, 2005 12:21 PM Subject: Re: REMIND and LATER considered harmful [was Re: RESOLVED] > > In my view, there are two types of transitions that could be made to > PENDING. First, is from NEW/ASSIGNED to PENDING where an engineer has > acknowledged the bug but is not able to (for whatever reason) handle the > issue immediately. The other transition into a PENDING status is when > QA is similarly awaiting information and unable to handle the issue > immediately. From my perspective, PENDING is not an excuse to stop the > clock. PENDING is meant only for situations where the bug owner is > waiting on something outside his/her control and not able to move > forward until that other piece is resolved. > > In my mind, a bug could be pending: > > Customer or Third Party Feedback > Customer or Third Party Action > Review > Approval > Another Bug (in which case it should reference the bug or bugs - > depends_on) > Other (catch-all for things I haven't thought of - would need to be > policed, however). I like this idea. We've had to use RESOLVED/INVALID as a way to indicate that a bug report lacks enough information to handle it. A status of PENDING would be wonderful! If the admin configuration had a way to easily change the possible pending status values, it could come with some reasonable defaults out-of-the-box, but could also be easily customizable by the end user. For us, besides the 3rd-party feedback, the biggest reason for a bug to be pending would be lack of data. A lot of the errors we get can't be reproduced without the customer sending us the files they're working on. From kevin.benton at amd.com Wed Jul 13 14:11:40 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Wed, 13 Jul 2005 07:11:40 -0700 Subject: REMIND and LATER considered harmful [was Re: RESOLVED] Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE23@ssvlexmb2.amd.com> > For us, besides the 3rd-party feedback, the biggest reason for a bug to be > pending > would be lack of data. A lot of the errors we get can't be reproduced > without > the customer sending us the files they're working on. Isn't that a case where a bug should be unconfirmed? --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. From dberlin at dberlin.org Wed Jul 13 14:19:22 2005 From: dberlin at dberlin.org (Daniel Berlin) Date: Wed, 13 Jul 2005 10:19:22 -0400 Subject: REMIND and LATER considered harmful [was Re: RESOLVED] In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE23@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE23@ssvlexmb2.amd.com> Message-ID: <1121264362.8387.2.camel@linux.site> On Wed, 2005-07-13 at 07:11 -0700, Benton, Kevin wrote: > > For us, besides the 3rd-party feedback, the biggest reason for a bug > to be > > pending > > would be lack of data. A lot of the errors we get can't be reproduced > > without > > the customer sending us the files they're working on. > > Isn't that a case where a bug should be unconfirmed? GCC Bugzilla actually has a "WAITING" state for this, so you can tell the difference between bugs sitting around doing nothing and bugs waiting for feedback from the reporter. From dwilliss at microimages.com Wed Jul 13 14:25:26 2005 From: dwilliss at microimages.com (Dave Williss) Date: Wed, 13 Jul 2005 09:25:26 -0500 Subject: Large attachments Message-ID: <564001c587b6$bbba17e0$4b00000a@opus2> A while back, I saw something about a plan to handle large attachments in BZ by storing them as files rather than database fields. Does anybody know the Bug # of this or where I could find more details? -- Dave Williss ------ Meddle not in the affairs of dragons, for you are crunchy and taste good with catsup -------------- next part -------------- An HTML attachment was scrubbed... URL: From kevin.benton at amd.com Wed Jul 13 14:35:32 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Wed, 13 Jul 2005 07:35:32 -0700 Subject: Large attachments Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE28@ssvlexmb2.amd.com> A while back, I saw something about a plan to handle large attachments in BZ by storing them as files rather than database fields. Does anybody know the Bug # of this or where I could find more details? That's actually been implemented in 2.19.3 if that helps --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. -------------- next part -------------- An HTML attachment was scrubbed... URL: From wicked at etlicon.fi Wed Jul 13 14:44:57 2005 From: wicked at etlicon.fi (wicked at etlicon.fi) Date: Wed, 13 Jul 2005 17:44:57 +0300 Subject: Large attachments In-Reply-To: <564001c587b6$bbba17e0$4b00000a@opus2> References: <564001c587b6$bbba17e0$4b00000a@opus2> Message-ID: <42D528E9.4020607@etlicon.com> Dave Williss wrote: > A while back, I saw something about a plan to handle large attachments in BZ > by storing them as files rather than database fields. Does anybody know the > Bug # of this or where I could find more details? That feature is available in 2.20rc1, see http://www.bugzilla.org/releases/2.20/new-features.html#la for details. The bug that added the feature (first available on 2.19.3 as Kevin pointed out) is https://bugzilla.mozilla.org/show_bug.cgi?id=252272 -- Teemu Mannermaa System Specialist "Anything is possible. It's all about probabilities." From jpyeron at pdinc.us Wed Jul 13 14:49:31 2005 From: jpyeron at pdinc.us (Jason Pyeron) Date: Wed, 13 Jul 2005 10:49:31 -0400 (EDT) Subject: Large attachments In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE28@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE28@ssvlexmb2.amd.com> Message-ID: 2.19.3 litters the file system? On Wed, 13 Jul 2005, Benton, Kevin wrote: > > That's actually been implemented in 2.19.3 if that helps > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Partner & Sr. Manager 7 West 24th Street #100 - - +1 (443) 921-0381 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. From dberlin at dberlin.org Wed Jul 13 14:54:22 2005 From: dberlin at dberlin.org (Daniel Berlin) Date: Wed, 13 Jul 2005 10:54:22 -0400 Subject: Large attachments In-Reply-To: References: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE28@ssvlexmb2.amd.com> Message-ID: <1121266462.8387.9.camel@linux.site> If you tell it to, yes (IE you have to explicitly turn this on) If not, no. On Wed, 2005-07-13 at 10:49 -0400, Jason Pyeron wrote: > 2.19.3 litters the file system? > > On Wed, 13 Jul 2005, Benton, Kevin wrote: > > > > That's actually been implemented in 2.19.3 if that helps > > > From kevin.benton at amd.com Wed Jul 13 14:59:57 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Wed, 13 Jul 2005 07:59:57 -0700 Subject: Large attachments Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE2F@ssvlexmb2.amd.com> Thankfully, yes, you do have to turn it on in the Parameters menu. --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Daniel Berlin Sent: Wednesday, July 13, 2005 8:54 AM To: developers at bugzilla.org Subject: Re: Large attachments If you tell it to, yes (IE you have to explicitly turn this on) If not, no. On Wed, 2005-07-13 at 10:49 -0400, Jason Pyeron wrote: > 2.19.3 litters the file system? > > On Wed, 13 Jul 2005, Benton, Kevin wrote: > > > > That's actually been implemented in 2.19.3 if that helps > > > - To view or change your list settings, click here: From justdave at bugzilla.org Wed Jul 13 15:24:02 2005 From: justdave at bugzilla.org (David Miller) Date: Wed, 13 Jul 2005 11:24:02 -0400 Subject: REMIND and LATER considered harmful In-Reply-To: <2cb10c440507120810543edf60@mail.gmail.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE044@ssvlexmb2.amd.com> <42D3D63C.8030106@mozilla.org> <2cb10c4405071207464e88b295@mail.gmail.com> <2cb10c440507120810543edf60@mail.gmail.com> Message-ID: <42D53212.5020805@bugzilla.org> Luis Villa wrote: > P.S. The reason I get pissy about this is that I believe firmly that > software should be useful out of the box, and we've shipped now for > six years with defaults that we acknowledge are deeply broken. It > makes it harder to recommend bugzilla when I've had very smart people > come to me and say 'well, I just installed bugzilla like you told me, > and there are these weird resolutions- but I know there must be a > reason for them, or else why would they be in bugzilla? I guess we'll > just figure out how to use them.' Yeah, it sat there for years because MattyT promised us Custom Resolutions "really soon now" and then didn't deliver, and it was all supposed to go away with custom resolutions. I think the best way to do this is fix it for new installs, and let people with existing installs remove it manually once we have a resolutions editor (which we may already have? resolutions are actually stored in a table now as of 2.20, instead of being enums) -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From mkanat at bugzilla.org Wed Jul 13 03:43:57 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 12 Jul 2005 20:43:57 -0700 Subject: Moving a Product Between Installations Message-ID: <1121226237.5465.8.camel@localhost.localdomain> Hey, just so you know, I think that everybody on the team seems to be magically aligned about how we should do this product move -- I filed this bug a few hours before we actually had the on-list discussion about it: https://bugzilla.mozilla.org/show_bug.cgi?id=300434 -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From Martin.Danjou at neterion.com Wed Jul 13 15:52:24 2005 From: Martin.Danjou at neterion.com (Martin d'Anjou) Date: Wed, 13 Jul 2005 11:52:24 -0400 (EDT) Subject: REMIND and LATER considered harmful In-Reply-To: <42D53212.5020805@bugzilla.org> Message-ID: > I think the best way to do this is fix it for new installs, and let > people with existing installs remove it manually once we have a > resolutions editor (which we may already have? resolutions are actually > stored in a table now as of 2.20, instead of being enums) Excuse me for interfering, but would it be beneficial to have the entire bug flow customizable instead of just the bug resolution part of it? This way people could define their own bug flow. Bugzilla would just be a big state machine manager/history tracker, where states, outputs and transitions are provided by the users. Martin From kevin.benton at amd.com Wed Jul 13 15:58:36 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Wed, 13 Jul 2005 08:58:36 -0700 Subject: REMIND and LATER considered harmful Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE46@ssvlexmb2.amd.com> > > I think the best way to do this is fix it for new installs, and let > > people with existing installs remove it manually once we have a > > resolutions editor (which we may already have? resolutions are actually > > stored in a table now as of 2.20, instead of being enums) > > Excuse me for interfering, but would it be beneficial to have the entire > bug flow customizable instead of just the bug resolution part of it? This > way people could define their own bug flow. Bugzilla would just be a big > state machine manager/history tracker, where states, outputs and > transitions are provided by the users. That sounds reasonable. How would you envision it? --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. From luis.villa at gmail.com Wed Jul 13 16:13:09 2005 From: luis.villa at gmail.com (Luis Villa) Date: Wed, 13 Jul 2005 12:13:09 -0400 Subject: REMIND and LATER considered harmful In-Reply-To: <42D53212.5020805@bugzilla.org> References: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE044@ssvlexmb2.amd.com> <42D3D63C.8030106@mozilla.org> <2cb10c4405071207464e88b295@mail.gmail.com> <2cb10c440507120810543edf60@mail.gmail.com> <42D53212.5020805@bugzilla.org> Message-ID: <2cb10c4405071309131448a878@mail.gmail.com> On 7/13/05, David Miller wrote: > Luis Villa wrote: > > > P.S. The reason I get pissy about this is that I believe firmly that > > software should be useful out of the box, and we've shipped now for > > six years with defaults that we acknowledge are deeply broken. It > > makes it harder to recommend bugzilla when I've had very smart people > > come to me and say 'well, I just installed bugzilla like you told me, > > and there are these weird resolutions- but I know there must be a > > reason for them, or else why would they be in bugzilla? I guess we'll > > just figure out how to use them.' > > Yeah, it sat there for years because MattyT promised us Custom > Resolutions "really soon now" and then didn't deliver, and it was all > supposed to go away with custom resolutions. > > I think the best way to do this is fix it for new installs, I've attached patches to the bug that'll fix it for new installs (AFAICT, i don't have a setup to test with right now) - but it may have issues with collectstats.pl. > and let > people with existing installs remove it manually once we have a > resolutions editor (which we may already have? resolutions are actually > stored in a table now as of 2.20, instead of being enums) I'm a little worried about the upgrade scenario- from a code read, it *should* be safe to do what I did, but I can't test, so... :/ luis From Martin.Danjou at neterion.com Wed Jul 13 16:51:39 2005 From: Martin.Danjou at neterion.com (Martin d'Anjou) Date: Wed, 13 Jul 2005 12:51:39 -0400 (EDT) Subject: REMIND and LATER considered harmful In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE46@ssvlexmb2.amd.com> Message-ID: > > > I think the best way to do this is fix it for new installs, and let > > > people with existing installs remove it manually once we have a > > > resolutions editor (which we may already have? resolutions are > actually > > > stored in a table now as of 2.20, instead of being enums) > > > > Excuse me for interfering, but would it be beneficial to have the > entire > > bug flow customizable instead of just the bug resolution part of it? > This > > way people could define their own bug flow. Bugzilla would just be a > big > > state machine manager/history tracker, where states, outputs and > > transitions are provided by the users. > > That sounds reasonable. How would you envision it? Sorry, but I have given no thoughts to this. I was just asking a general question. Martin From myk at mozilla.org Wed Jul 13 17:28:34 2005 From: myk at mozilla.org (Myk Melez) Date: Wed, 13 Jul 2005 10:28:34 -0700 Subject: Large attachments In-Reply-To: <1121266462.8387.9.camel@linux.site> References: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE28@ssvlexmb2.amd.com> <1121266462.8387.9.camel@linux.site> Message-ID: <42D54F42.6040001@mozilla.org> Right. And we should make it clear that we don't recommend that Bugzilla installations use this feature, since it adds a dependency on the filesystem that imposes limits on your use of Bugzilla. In particular, you can't easily increase Bugzilla capacity by setting up a second instance of the app, since you then have to share a filesystem, which is harder than sharing a database. Of course, the feature is the only workable solution for attachments greater than 16MB in size on MySQL 3.23, which imposes that limit on the size of communication packets. But MySQL 4.0.1+ accept packets up to 1GB in size, and 2.22 will require MySQL 4.0.2+, so perhaps this feature is no longer necessary and can be removed in 2.22. Thoughts? -myk Daniel Berlin wrote: > If you tell it to, yes (IE you have to explicitly turn this on) > > If not, no. > On Wed, 2005-07-13 at 10:49 -0400, Jason Pyeron wrote: > >> 2.19.3 litters the file system? >> >> On Wed, 13 Jul 2005, Benton, Kevin wrote: >> >>> That's actually been implemented in 2.19.3 if that helps >>> >>> > > - > To view or change your list settings, click here: > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jpyeron at pdinc.us Wed Jul 13 17:29:26 2005 From: jpyeron at pdinc.us (Jason Pyeron) Date: Wed, 13 Jul 2005 13:29:26 -0400 (EDT) Subject: REMIND and LATER considered harmful In-Reply-To: References: Message-ID: I brought this up on the list a month ago, the solution rpms are up on our web site. you need the compat rpms. http://public.pdinc.us/rpms/mysql Jason Pyeron On Wed, 13 Jul 2005, Martin d'Anjou wrote: >>>> I think the best way to do this is fix it for new installs, and let >>>> people with existing installs remove it manually once we have a >>>> resolutions editor (which we may already have? resolutions are >> actually >>>> stored in a table now as of 2.20, instead of being enums) >>> >>> Excuse me for interfering, but would it be beneficial to have the >> entire >>> bug flow customizable instead of just the bug resolution part of it? >> This >>> way people could define their own bug flow. Bugzilla would just be a >> big >>> state machine manager/history tracker, where states, outputs and >>> transitions are provided by the users. >> >> That sounds reasonable. How would you envision it? > > Sorry, but I have given no thoughts to this. I was just asking a general > question. > > Martin > > > - > To view or change your list settings, click here: > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Partner & Sr. Manager 7 West 24th Street #100 - - +1 (443) 921-0381 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. From jpyeron at pdinc.us Wed Jul 13 17:39:58 2005 From: jpyeron at pdinc.us (Jason Pyeron) Date: Wed, 13 Jul 2005 13:39:58 -0400 (EDT) Subject: Large attachments In-Reply-To: <42D54F42.6040001@mozilla.org> References: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE28@ssvlexmb2.amd.com> <1121266462.8387.9.camel@linux.site> <42D54F42.6040001@mozilla.org> Message-ID: As much as I am against this feature, some may still ?need? it. Just put big red warnings around it, instead of removing it. -Jason Pyeron On Wed, 13 Jul 2005, Myk Melez wrote: > Of course, the feature is the only workable solution for attachments greater > than 16MB in size on MySQL 3.23, which imposes that limit on the size of > communication packets. But MySQL 4.0.1+ accept packets up to 1GB in size, > and 2.22 will require MySQL 4.0.2+, so perhaps this feature is no longer > necessary and can be removed in 2.22. > > Thoughts? > > -myk -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Partner & Sr. Manager 7 West 24th Street #100 - - +1 (443) 921-0381 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. From ghendricks at novell.com Wed Jul 13 17:49:52 2005 From: ghendricks at novell.com (Gregary Hendricks) Date: Wed, 13 Jul 2005 11:49:52 -0600 Subject: REMIND and LATER considered harmful [was Re: RESOLVED] Message-ID: <42D4FFDD.3532.00D2.0@novell.com> On Wednesday 13 July 2005 08:19, Daniel Berlin wrote: > On Wed, 2005-07-13 at 07:11 -0700, Benton, Kevin wrote: > > > For us, besides the 3rd-party feedback, the biggest reason for a bug > > > > to be > > > > > pending > > > would be lack of data. A lot of the errors we get can't be reproduced > > > without > > > the customer sending us the files they're working on. > > > > Isn't that a case where a bug should be unconfirmed? > > GCC Bugzilla actually has a "WAITING" state for this, so you can tell > the difference between bugs sitting around doing nothing and bugs > waiting for feedback from the reporter. > > For this we, as well as a number of bugzillae, have implemented a NEEDINFO status. Along with it we have an added field of who we need information from (reporter, last commentor, or someone else entirely) who is then CC'd on the bug for the duration that the bug is in the NEEDINFO state. This places the responsibility of the bug squarely on the shoulders of the info provider until they come back with the additional information. This really helps in the processing of a bug as it is obvious by the status that no work can be completed until someone (usually the reporter) comes back with something more than was initially provided. -- Greg Hendricks Novell IS&T Engineer GHendricks at novell.com www.novell.com From jay at veggiespam.com Wed Jul 13 18:14:03 2005 From: jay at veggiespam.com (jay ball) Date: Wed, 13 Jul 2005 14:14:03 -0400 Subject: Large attachments In-Reply-To: References: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE28@ssvlexmb2.amd.com> <1121266462.8387.9.camel@linux.site> <42D54F42.6040001@mozilla.org> Message-ID: <42D559EB.8040409@veggiespam.com> I agree with Jason, leave it there for 2.22+. In the past, many of my installations would have worked better if the files were stored outside of the DB. Plus, many companies, like my very large one, have different inter-departmental billing codes for DB utilization vs file system space. I have also seen ISPs charging different rates for buying extra DB space vs web server space. As a matter of cost savings, it'd be nice to keep it. With all the warnings and flashing lights still intact. -jay (permanent lurker) Jason Pyeron wrote: > As much as I am against this feature, some may still ?need? it. Just put > big red warnings around it, instead of removing it. > > -Jason Pyeron > > On Wed, 13 Jul 2005, Myk Melez wrote: > >> Of course, the feature is the only workable solution for attachments >> greater than 16MB in size on MySQL 3.23, which imposes that limit on >> the size of communication packets. But MySQL 4.0.1+ accept packets up >> to 1GB in size, and 2.22 will require MySQL 4.0.2+, so perhaps this >> feature is no longer necessary and can be removed in 2.22. >> >> Thoughts? >> >> -myk > > From jake at bugzilla.org Wed Jul 13 18:19:00 2005 From: jake at bugzilla.org (Jake) Date: Wed, 13 Jul 2005 14:19:00 -0400 Subject: We have a QA Manager! In-Reply-To: <42D3D2EE.2090203@mozilla.org> References: <6F7DA19D05F3CF40B890C7CA2DB13A42016BE02F@ssvlexmb2.amd.com> <42D3D2EE.2090203@mozilla.org> Message-ID: <42D55B14.20607@bugzilla.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gervase Markham wrote: > Urk - please, no :-) We can't try and match bug numbers up. That > way lies madness. I agree. We could possibly do something where if a bug doesn't have an alias it becomes, fe, bmo-74996. The real issue, IMHO, will be making it so that if bmo's bug 74996 becomes bbo (or whatever) bug 134 that some comment in bmo bug 73665 that mentions "bug 74996" is somehow translated into "bug 134". > A better solution would be for a bug which is RESOLVED MOVED to > automatically redirect to the new bug in the new Bugzilla... but > perhaps some people wouldn't like that. Perhaps a direct redirect may meet some resistance, but I don't see any issue with a prominate link (perhaps next to the MOVED kinda like the DUPLICATE of link). This could also help at least a little with the above mentioned issue. The comment "bug 74996" could be encoded somehow to link to bmo's bug 74996 which would then link back to bbo bug 134. A bit of a kludge, but better than doing nothing. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC1VqoPFshtZHeR6kRAgszAJ4joS6iD2FioEpPT504aXczUDzQyACbBrsy y5ihtazE9nRvpJJQgHvNLYI= =VHS2 -----END PGP SIGNATURE----- From jake at bugzilla.org Wed Jul 13 18:28:41 2005 From: jake at bugzilla.org (Jake) Date: Wed, 13 Jul 2005 14:28:41 -0400 Subject: REMIND and LATER considered harmful In-Reply-To: References: Message-ID: <42D55D59.60504@bugzilla.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin d'Anjou wrote: >Excuse me for interfering, but would it be beneficial to have the entire >bug flow customizable instead of just the bug resolution part of it? This >way people could define their own bug flow. Bugzilla would just be a big >state machine manager/history tracker, where states, outputs and >transitions are provided by the users. Sure would. That was going to be MattyT's next step: https://bugzilla.mozilla.org/show_bug.cgi?id=bz-custstat -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC1V1ZPFshtZHeR6kRAn3wAJ9RldBQ4ZXQ83hql4Vf3/K0CZH1YgCePIP9 RLMC65TxwYNdUvwr9SZYPDw= =MOuK -----END PGP SIGNATURE----- From gerv at mozilla.org Wed Jul 13 18:51:29 2005 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 13 Jul 2005 19:51:29 +0100 Subject: Large attachments In-Reply-To: <42D559EB.8040409@veggiespam.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE28@ssvlexmb2.amd.com> <1121266462.8387.9.camel@linux.site> <42D54F42.6040001@mozilla.org> <42D559EB.8040409@veggiespam.com> Message-ID: <42D562B1.9000706@mozilla.org> jay ball wrote: > I agree with Jason, leave it there for 2.22+. In the past, many of my > installations would have worked better if the files were stored outside > of the DB. > > Plus, many companies, like my very large one, have different > inter-departmental billing codes for DB utilization vs file system > space. I have also seen ISPs charging different rates for buying extra > DB space vs web server space. I think this isn't a massively good excuse for retaining a feature with significant downsides. I remember all of these issues being raised when it was implemented... Gerv From mkanat at bugzilla.org Thu Jul 14 08:03:58 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 14 Jul 2005 01:03:58 -0700 Subject: 2.20 Release: Dates Message-ID: <1121328239.6553.11.camel@localhost.localdomain> I'd like to start the process of releasing Bugzilla 2.20 on July 27. Here is a list of all the blockers: http://tinyurl.com/9565b Ideally, they should be resolved before Monday, the 25th. It would be nice, of course, also, if they are resolved in a fashion that involves the least possible code change (so that we don't have to have another RC). Also, if there's anything else you'd like to see as a blocker, please nominate it! :-) -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From gerv at mozilla.org Thu Jul 14 09:28:38 2005 From: gerv at mozilla.org (Gervase Markham) Date: Thu, 14 Jul 2005 10:28:38 +0100 Subject: mouseover help busted? In-Reply-To: <2cb10c440507120841312768b3@mail.gmail.com> References: <2cb10c440507120841312768b3@mail.gmail.com> Message-ID: <42D63046.2010509@mozilla.org> Luis Villa wrote: > Poking at landfill with firefox 1.0.4/linux, the tooltip help: > > http://landfill.bugzilla.org/bugzilla-2.20-branch/query.cgi?help=1&format=advanced > > doesn't come up for me. Anyone know offhand if this is a bugzilla or a > firefox problem? It depends how you look at it :-) The JS needs to add "px" to the values it is using to set the top and left positioning of the
. This used to work; so either we switched to an HTML Strict DTD or something like that, or Firefox got fixed. https://bugzilla.mozilla.org/show_bug.cgi?id=300743 Gerv From mkanat at bugzilla.org Thu Jul 14 11:40:16 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 14 Jul 2005 04:40:16 -0700 Subject: mouseover help busted? In-Reply-To: <42D63046.2010509@mozilla.org> References: <2cb10c440507120841312768b3@mail.gmail.com> <42D63046.2010509@mozilla.org> Message-ID: <1121341216.5443.4.camel@localhost.localdomain> On Thu, 2005-07-14 at 10:28 +0100, Gervase Markham wrote: > so either we switched > to an HTML Strict DTD or something like that, Yeah, we added a URI to the HTML Transitional DTD, so we trigger standards-compliance mode, now. This is actually the first problem I've seen from it, so I guess that shows us that we were coding pretty decent HTML and JS even before we switched. :-) -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From mkanat at bugzilla.org Thu Jul 14 12:01:17 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 14 Jul 2005 05:01:17 -0700 Subject: Perl-DBD-Pg passes incorrect data In-Reply-To: <42D65100.3060108@gmail.com> References: <42D65100.3060108@gmail.com> Message-ID: <1121342477.5742.0.camel@localhost.localdomain> On Thu, 2005-07-14 at 13:48 +0200, Fr?d?ric Buclin wrote: > Using DBD::Pg 1.40 and PostgreSQL 8.0.1 on Mandrake Linux 10.2, all data > sent from Perl are seen as VARCHAR by PostgreSQL when we omit to write e.g. > $sth->bind_param(2, $schema_version, DBI::SQL_NUMERIC) Have you tried upgrading beyond 1.40 yet? There's an entry in the changelog for 1.41 that sounds like it fixes this problem. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From LpSolit at gmail.com Thu Jul 14 12:09:56 2005 From: LpSolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Thu, 14 Jul 2005 14:09:56 +0200 Subject: Perl-DBD-Pg passes incorrect data In-Reply-To: <1121342477.5742.0.camel@localhost.localdomain> References: <42D65100.3060108@gmail.com> <1121342477.5742.0.camel@localhost.localdomain> Message-ID: <42D65614.5070100@gmail.com> > Have you tried upgrading beyond 1.40 yet? There's an entry in the > changelog for 1.41 that sounds like it fixes this problem. I have a compilation error using 1.43. So I'm stick with 1.40. From luis.villa at gmail.com Thu Jul 14 12:46:34 2005 From: luis.villa at gmail.com (Luis Villa) Date: Thu, 14 Jul 2005 08:46:34 -0400 Subject: mouseover help busted? In-Reply-To: <42D63046.2010509@mozilla.org> References: <2cb10c440507120841312768b3@mail.gmail.com> <42D63046.2010509@mozilla.org> Message-ID: <2cb10c44050714054625de1fba@mail.gmail.com> On 7/14/05, Gervase Markham wrote: > Luis Villa wrote: > > Poking at landfill with firefox 1.0.4/linux, the tooltip help: > > > > http://landfill.bugzilla.org/bugzilla-2.20-branch/query.cgi?help=1&format=advanced > > > > doesn't come up for me. Anyone know offhand if this is a bugzilla or a > > firefox problem? > > It depends how you look at it :-) > > The JS needs to add "px" to the values it is using to set the top and > left positioning of the
. This used to work; so either we switched > to an HTML Strict DTD or something like that, or Firefox got fixed. > https://bugzilla.mozilla.org/show_bug.cgi?id=300743 Should this be a 2.20 showstopper? (esp. since the fix is so easy to review?) Luis From timeless at myrealbox.com Thu Jul 14 18:12:18 2005 From: timeless at myrealbox.com (timeless) Date: Thu, 14 Jul 2005 11:12:18 -0700 Subject: REMIND and LATER considered harmful [was Re: RESOLVED] In-Reply-To: <42D4FFDD.3532.00D2.0@novell.com> References: <42D4FFDD.3532.00D2.0@novell.com> Message-ID: <42D6AB02.2080002@myrealbox.com> Gregary Hendricks wrote: > For this we, as well as a number of bugzillae, have implemented a > NEEDINFO status. Along with it we have an added field of who we > need information from (reporter, last commentor, or someone else > entirely) who is then CC'd on the bug for the duration that the bug > is in the NEEDINFO state. This places the responsibility of the bug > squarely on the shoulders of the info provider until they come back > with the additional information. This really helps in the processing > of a bug as it is obvious by the status that no work can be > completed until someone (usually the reporter) comes back with > something more than was initially provided. i much prefer this (both ideally and having seen it) over all the other forms suggested in this thread. From kevin.benton at amd.com Thu Jul 14 20:51:21 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Thu, 14 Jul 2005 13:51:21 -0700 Subject: REMIND and LATER considered harmful [was Re: RESOLVED] Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42018CE0B1@ssvlexmb2.amd.com> >From a process monitoring perspective, "NEEDINFO" by itself isn't enough from my point of view. There are other reasons a bug may be in a PENDING state besides a need for additional information. --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of timeless Sent: Thursday, July 14, 2005 12:12 PM To: developers at bugzilla.org Subject: Re: REMIND and LATER considered harmful [was Re: RESOLVED] Gregary Hendricks wrote: > For this we, as well as a number of bugzillae, have implemented a > NEEDINFO status. Along with it we have an added field of who we > need information from (reporter, last commentor, or someone else > entirely) who is then CC'd on the bug for the duration that the bug > is in the NEEDINFO state. This places the responsibility of the bug > squarely on the shoulders of the info provider until they come back > with the additional information. This really helps in the processing > of a bug as it is obvious by the status that no work can be > completed until someone (usually the reporter) comes back with > something more than was initially provided. i much prefer this (both ideally and having seen it) over all the other forms suggested in this thread. - To view or change your list settings, click here: From LpSolit at gmail.com Fri Jul 15 13:28:25 2005 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Fri, 15 Jul 2005 15:28:25 +0200 Subject: QA team Message-ID: <42D7B9F9.6050709@gmail.com> Due to our broken 2.18.2 release last week, we decided to create a QA team to avoid such thing again. Actually, we are two reviewers in this team: Teemu Mannermaa (aka wicked or Zornreich) and myself. A third reviewer may join the team soon depending on his new job: Byron Jones (aka glob). The PostgreSQL support is still experimental in 2.20 but we will very soon require someone using it on a daily basis to test and make sure everything works fine in future releases. So if some of you (no need to be a Bugzilla expert to help) are interested in joining the team or simply help us occasionally to have non-broken releases (let's hope 2.18.4 will not be followed two days later by 2.18.5), please contact me, either directly in IRC (nick: LpSolit) or per email at LpSolit at gmail.com, or by replying to developers at bugzilla.org. Also, I'm especially interested in users or developers using Bugzilla on Windows and/or using PostgreSQL. A few words about what will change for future releases: - No checkin will be allowed at least 24/48 hours before a release, allowing the QA team to test the new release as much as possible and fix regressions *before* the release instead of after. For comparison, we did 24 checkins less than 18 hours before releasing 2.20rc1/2.18.2. That was far too much and gave us no chance to catch regressions on time (in fact, a first regression was found and fixed on time, but we missed the second one). - For those who have editbugs privileges on b.m.o, you are free to add the 'qawanted' keyword to bugs to specify that some attention is required from the QA team. Use this keyword when a bug needs a testcase, additional information or looks like a regression. If you cannot add this keyword due to restrictions on your account, please set the flag to either blocking2.18.x? or blocking2.20? depending on which versions are affected. mkanat, justdave, myk or anyone else with enough privileges can then set the 'qawanted' keyword for you. Please *do not* use this keyword for bugs requesting new features (bugs marked as 'enhancement'). I will ignore those bugs. Please don't remove the 'qawanted' keyword unless you belong to the QA team. - Remaining things are internal to the QA team. ;) Thank you for your attention. Have a nice week-end, Frederic "LpSolit" Buclin From luis.villa at gmail.com Fri Jul 15 13:35:27 2005 From: luis.villa at gmail.com (Luis Villa) Date: Fri, 15 Jul 2005 09:35:27 -0400 Subject: QA team In-Reply-To: <42D7B9F9.6050709@gmail.com> References: <42D7B9F9.6050709@gmail.com> Message-ID: <2cb10c4405071506357bcbc6b2@mail.gmail.com> Any plans to do automated/scripted testing? Luis On 7/15/05, Fr?d?ric Buclin wrote: > Due to our broken 2.18.2 release last week, we decided to create a QA > team to avoid such thing again. Actually, we are two reviewers in this > team: Teemu Mannermaa (aka wicked or Zornreich) and myself. A third > reviewer may join the team soon depending on his new job: Byron Jones > (aka glob). > > The PostgreSQL support is still experimental in 2.20 but we will very > soon require someone using it on a daily basis to test and make sure > everything works fine in future releases. > > So if some of you (no need to be a Bugzilla expert to help) are > interested in joining the team or simply help us occasionally to have > non-broken releases (let's hope 2.18.4 will not be followed two days > later by 2.18.5), please contact me, either directly in IRC (nick: > LpSolit) or per email at LpSolit at gmail.com, or by replying to > developers at bugzilla.org. Also, I'm especially interested in users or > developers using Bugzilla on Windows and/or using PostgreSQL. > > > A few words about what will change for future releases: > > - No checkin will be allowed at least 24/48 hours before a release, > allowing the QA team to test the new release as much as possible and fix > regressions *before* the release instead of after. For comparison, we > did 24 checkins less than 18 hours before releasing 2.20rc1/2.18.2. That > was far too much and gave us no chance to catch regressions on time (in > fact, a first regression was found and fixed on time, but we missed the > second one). > > - For those who have editbugs privileges on b.m.o, you are free to add > the 'qawanted' keyword to bugs to specify that some attention is > required from the QA team. Use this keyword when a bug needs a testcase, > additional information or looks like a regression. If you cannot add > this keyword due to restrictions on your account, please set the flag to > either blocking2.18.x? or blocking2.20? depending on which versions are > affected. mkanat, justdave, myk or anyone else with enough privileges > can then set the 'qawanted' keyword for you. Please *do not* use this > keyword for bugs requesting new features (bugs marked as 'enhancement'). > I will ignore those bugs. > > Please don't remove the 'qawanted' keyword unless you belong to the > QA team. > > - Remaining things are internal to the QA team. ;) > > > Thank you for your attention. > > Have a nice week-end, > > Frederic "LpSolit" Buclin > - > To view or change your list settings, click here: > > From LpSolit at gmail.com Fri Jul 15 13:54:31 2005 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Fri, 15 Jul 2005 15:54:31 +0200 Subject: QA team In-Reply-To: <2cb10c4405071506357bcbc6b2@mail.gmail.com> References: <42D7B9F9.6050709@gmail.com> <2cb10c4405071506357bcbc6b2@mail.gmail.com> Message-ID: <42D7C017.5080001@gmail.com> Luis Villa a ?crit : > Any plans to do automated/scripted testing? That would be fine. glob said he wrote such automated scripts in the past. That's why I hope he will join the QA team. :) So for now, we test Bugzilla manually. Which is fine too, because I often found bugs unrelated to what I was testing, and I'm not sure an automated script would catch these bugs too. But having/doing both would be better, sure! Fred From luis.villa at gmail.com Fri Jul 15 14:00:03 2005 From: luis.villa at gmail.com (Luis Villa) Date: Fri, 15 Jul 2005 10:00:03 -0400 Subject: QA team In-Reply-To: <42D7C017.5080001@gmail.com> References: <42D7B9F9.6050709@gmail.com> <2cb10c4405071506357bcbc6b2@mail.gmail.com> <42D7C017.5080001@gmail.com> Message-ID: <2cb10c4405071507001f814a40@mail.gmail.com> On 7/15/05, Fr?d?ric Buclin wrote: > Luis Villa a ?crit : > > Any plans to do automated/scripted testing? > > That would be fine. glob said he wrote such automated scripts in the > past. That's why I hope he will join the QA team. :) Oh, that's great. I have no experience with them, unfortunately, else I'd join :) > So for now, we test Bugzilla manually. Which is fine too, because I > often found bugs unrelated to what I was testing, Of course. > and I'm not sure an > automated script would catch these bugs too. But having/doing both would > be better, sure! It seems like you could definitely catch a lot of the worst/most embarassing bugs (like the one that necessitated 2.18.3) with well written/comprehensive automated testing. That's really what brought it to mind. Luis From dwilliss at microimages.com Fri Jul 15 14:29:07 2005 From: dwilliss at microimages.com (Dave Williss) Date: Fri, 15 Jul 2005 09:29:07 -0500 Subject: Large attachments References: <6F7DA19D05F3CF40B890C7CA2DB13A42018CDE28@ssvlexmb2.amd.com> <1121266462.8387.9.camel@linux.site> <42D54F42.6040001@mozilla.org> Message-ID: <613501c58949$90a35b90$4b00000a@opus2> ----- Original Message ----- From: Myk Melez To: developers at bugzilla.org Sent: Wednesday, July 13, 2005 12:28 PM Subject: Re: Large attachments > Right. And we should make it clear that we don't recommend that Bugzilla > installations use this feature, since it adds a dependency on the > filesystem > that imposes limits on your use of Bugzilla. In particular, you can't > easily > increase Bugzilla capacity by setting up a second instance of the app, > since > you then have to share a filesystem, which is harder than sharing a > database. I would have to disagree here. Sharing a filesystem on Unix is pretty easy. I've never tried to share a database, but it didn't seem easy. Of course that may just be the learning curve. Once you know how to, it may be easy. > Of course, the feature is the only workable solution for attachments > greater > than 16MB in size on MySQL 3.23, which imposes that limit on the size > of communication packets. But MySQL 4.0.1+ accept packets up to > 1GB in size, and 2.22 will require MySQL 4.0.2+, so perhaps this feature > is no longer necessary and can be removed in 2.22. In our industry (GIS), it is not uncommon these days for datasets to reach several hunderd Megabytes, with multi-gigabyte datasets from time to time. Keeping track of these as in Bugzilla as attachments won't work for obvious reasons. What we've been doing is placing them on a shared drive on our fileserver in a directory named errdata, with the subdirectory for each bug (named using the submitters initials (out of tradition from our pre-bugzill days) followed by the bugzilla id). The only thing we put as attachments are things like screen-shots. I wrote a script that fires off via cron every night which looks for bugs that have been closed for 14 days or more which still have data in errdata and delete it to keep from accumulating old data. I'd like to be able to manage this errdata directory via bugzilla, but I think doing so in a general way is impractical. > Thoughts? > -myk Daniel Berlin wrote: If you tell it to, yes (IE you have to explicitly turn this on) If not, no. On Wed, 2005-07-13 at 10:49 -0400, Jason Pyeron wrote: 2.19.3 litters the file system? On Wed, 13 Jul 2005, Benton, Kevin wrote: That's actually been implemented in 2.19.3 if that helps - To view or change your list settings, click here: MailScanner has detected a possible fraud attempt from "bugzilla.org" claiming to be MailScanner has detected a possible fraud attempt from "bugzilla.org" claiming to be From micklweiss at gmx.net Fri Jul 15 15:31:24 2005 From: micklweiss at gmx.net (Mick Weiss) Date: Fri, 15 Jul 2005 11:31:24 -0400 Subject: QA team In-Reply-To: <42D7B9F9.6050709@gmail.com> References: <42D7B9F9.6050709@gmail.com> Message-ID: <42D7D6CC.4050104@gmx.net> Fr?d?ric Buclin wrote: I think that a QA team is a great idea. I'm working on this on other projects. If I wasn't so busy with the other projects, I would have volunteered. I just had a thought though, would someone be willing to setup a box with Bugzilla on Windows or Bugzilla w/ Postgresql for use with testing? Obviously the box would need to be up all the time. I say this since I'm sure that there are developers out there who don't have access to a box (I can't be the only person). I only run OSX and Linux/*BSD. So here is an example... I personally don't use Windows, and I haven't needed to set it up in ages. (this is not meant to be flame bait so please don't flame me). Not to mention, I don't have the extra hardware. Someone may argue that hardware is cheap now-a-days.... and I may be the only person with this problem. My thought was, someone could perhaps setup a box w/ VMWare (or similar), with various versions of Windows (since different things happen in different versions) and have automatic installs of the latest version of Bugzilla. Then have both automatic and manual tests. This is just a thought. For people new to writing test cases in Perl, I recommend that you look @: http://perlunit.sourceforge.net/ and http://search.cpan.org/dist/Test-Simple/ (of course Test::Deep and Test::More) there was an article on perl.com about creating Test libraries a while back otherwise a really basic example is here: http://search.cpan.org/dist/Test-Simple/lib/Test/Tutorial.pod - Mick > Due to our broken 2.18.2 release last week, we decided to create a QA > team to avoid such thing again. Actually, we are two reviewers in this > team: Teemu Mannermaa (aka wicked or Zornreich) and myself. A third > reviewer may join the team soon depending on his new job: Byron Jones > (aka glob). > > The PostgreSQL support is still experimental in 2.20 but we will very > soon require someone using it on a daily basis to test and make sure > everything works fine in future releases. > > So if some of you (no need to be a Bugzilla expert to help) are > interested in joining the team or simply help us occasionally to have > non-broken releases (let's hope 2.18.4 will not be followed two days > later by 2.18.5), please contact me, either directly in IRC (nick: > LpSolit) or per email at LpSolit at gmail.com, or by replying to > developers at bugzilla.org. Also, I'm especially interested in users or > developers using Bugzilla on Windows and/or using PostgreSQL. > > > A few words about what will change for future releases: > > - No checkin will be allowed at least 24/48 hours before a release, > allowing the QA team to test the new release as much as possible and > fix regressions *before* the release instead of after. For comparison, > we did 24 checkins less than 18 hours before releasing 2.20rc1/2.18.2. > That was far too much and gave us no chance to catch regressions on > time (in fact, a first regression was found and fixed on time, but we > missed the second one). > > - For those who have editbugs privileges on b.m.o, you are free to add > the 'qawanted' keyword to bugs to specify that some attention is > required from the QA team. Use this keyword when a bug needs a > testcase, additional information or looks like a regression. If you > cannot add this keyword due to restrictions on your account, please > set the flag to either blocking2.18.x? or blocking2.20? depending on > which versions are affected. mkanat, justdave, myk or anyone else with > enough privileges can then set the 'qawanted' keyword for you. Please > *do not* use this keyword for bugs requesting new features (bugs > marked as 'enhancement'). I will ignore those bugs. > > Please don't remove the 'qawanted' keyword unless you belong to the > QA team. > > - Remaining things are internal to the QA team. ;) > > > Thank you for your attention. > > Have a nice week-end, > > Frederic "LpSolit" Buclin > - > To view or change your list settings, click here: > > > From zach at zachlipton.com Fri Jul 15 16:36:13 2005 From: zach at zachlipton.com (Zach Lipton) Date: Fri, 15 Jul 2005 09:36:13 -0700 Subject: Bugzilla T-Shirt Message-ID: The Mozilla Store is going to be reopening soon (finally!) and one of the items that we're looking to offer is a Bugzilla t-shirt. We are thinking of using the bug on bugzilla.mozilla.org for the main image, but are looking for suggestions on: * What color shirt would go well with the artwork * A tagline to put on the back Of course, Justdave could always do a signing party and offer signed shirts to the first customers... --zach From jpyeron at pdinc.us Fri Jul 15 16:58:32 2005 From: jpyeron at pdinc.us (Jason Pyeron) Date: Fri, 15 Jul 2005 12:58:32 -0400 (EDT) Subject: asterisk integration Message-ID: Anyone heard, or seen such a thing as Bugzilla - Asterisk integration? -Jason Pyeron -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Partner & Sr. Manager 7 West 24th Street #100 - - +1 (443) 921-0381 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. From justdave at bugzilla.org Fri Jul 15 18:29:58 2005 From: justdave at bugzilla.org (David Miller) Date: Fri, 15 Jul 2005 14:29:58 -0400 Subject: Bugzilla T-Shirt In-Reply-To: References: Message-ID: <42D800A6.30401@bugzilla.org> Zach Lipton wrote: > The Mozilla Store is going to be reopening soon (finally!) and one of > the items that we're looking to offer is a Bugzilla t-shirt. We are > thinking of using the bug on bugzilla.mozilla.org for the main image Oh, THAT bug? I thought Marcia wanted "Buggy" (the cartoon guy from bugzilla.org), that's the EPS file I mailed her. I have no clue where the electron microscope thing came from. :) That was well before my time. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From justdave at bugzilla.org Fri Jul 15 18:32:23 2005 From: justdave at bugzilla.org (David Miller) Date: Fri, 15 Jul 2005 14:32:23 -0400 Subject: asterisk integration In-Reply-To: References: Message-ID: <42D80137.9040807@bugzilla.org> Jason Pyeron wrote: > Anyone heard, or seen such a thing as Bugzilla - Asterisk integration? I haven't heard of anything (though with Terry Weissman having worked for TellMe after leaving Netscape, and that being the kind of thing TellMe does, it would make sense if they had a commercial offering that did that). That would be way cool though. I'd imagine calling in via phone, and having it read a bug report to you, or using your touch tones to perform actions on a bug? -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From myk at mozilla.org Fri Jul 15 18:42:32 2005 From: myk at mozilla.org (Myk Melez) Date: Fri, 15 Jul 2005 11:42:32 -0700 Subject: Bugzilla T-Shirt In-Reply-To: <42D800A6.30401@bugzilla.org> References: <42D800A6.30401@bugzilla.org> Message-ID: <42D80398.2090207@mozilla.org> David Miller wrote: > Zach Lipton wrote: > >> The Mozilla Store is going to be reopening soon (finally!) and one >> of the items that we're looking to offer is a Bugzilla t-shirt. We >> are thinking of using the bug on bugzilla.mozilla.org for the main >> image > > Oh, THAT bug? I thought Marcia wanted "Buggy" (the cartoon guy from > bugzilla.org), that's the EPS file I mailed her. I would think buggy a more appropriate mascot for the t-shirt. -myk From zach at zachlipton.com Fri Jul 15 18:45:11 2005 From: zach at zachlipton.com (Zach Lipton) Date: Fri, 15 Jul 2005 11:45:11 -0700 Subject: Bugzilla T-Shirt In-Reply-To: <42D800A6.30401@bugzilla.org> References: <42D800A6.30401@bugzilla.org> Message-ID: <082070A4-82E7-481C-8BC4-6CC52C4A830C@zachlipton.com> On Jul 15, 2005, at 11:29 AM, David Miller wrote: > Zach Lipton wrote: > > >> The Mozilla Store is going to be reopening soon (finally!) and one >> of the items that we're looking to offer is a Bugzilla t-shirt. >> We are thinking of using the bug on bugzilla.mozilla.org for the >> main image >> > > Oh, THAT bug? I thought Marcia wanted "Buggy" (the cartoon guy > from bugzilla.org), that's the EPS file I mailed her. I have no > clue where the electron microscope thing came from. :) That was > well before my time. > Sorry. My mistake. I did mean "Buggy," he's far cuter for a t-shirt anyway... Tagline suggestions would be great. --zach From katsumi at gmail.com Fri Jul 15 19:22:25 2005 From: katsumi at gmail.com (katsumi liquer) Date: Fri, 15 Jul 2005 15:22:25 -0400 Subject: Bugzilla T-Shirt In-Reply-To: <082070A4-82E7-481C-8BC4-6CC52C4A830C@zachlipton.com> References: <42D800A6.30401@bugzilla.org> <082070A4-82E7-481C-8BC4-6CC52C4A830C@zachlipton.com> Message-ID: <70dbf54d05071512225259d957@mail.gmail.com> On 7/15/05, Zach Lipton wrote: > > On Jul 15, 2005, at 11:29 AM, David Miller wrote: > > > Zach Lipton wrote: > > > > > >> The Mozilla Store is going to be reopening soon (finally!) and one > >> of the items that we're looking to offer is a Bugzilla t-shirt. > >> We are thinking of using the bug on bugzilla.mozilla.org for the > >> main image > >> > > > > Oh, THAT bug? I thought Marcia wanted "Buggy" (the cartoon guy > > from bugzilla.org), that's the EPS file I mailed her. I have no > > clue where the electron microscope thing came from. :) That was > > well before my time. > > > Sorry. My mistake. I did mean "Buggy," he's far cuter for a t-shirt > anyway... > > Tagline suggestions would be great. How about "This bug's for you" :) Can the t-shirt be black?? :) katsu From Chris.Raplee at portalplayer.com Fri Jul 15 19:35:46 2005 From: Chris.Raplee at portalplayer.com (Chris Raplee) Date: Fri, 15 Jul 2005 12:35:46 -0700 Subject: Bugzilla T-Shirt Message-ID: <59FA134614736A4AB04061CA4B07908C07ECA4@peach.portalplayersc.com> Could do "Bugzilla" in red spray-paint style letters (ala the DARE t-shirts) with a "Just Say NO to Bugs!" tagline. --Chris Raplee Now, we must all fear evil men. But there is another kind of evil which we must fear most, and that is the indifference of good men. -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of katsumi liquer Sent: Friday, July 15, 2005 12:22 PM To: developers at bugzilla.org Subject: Re: Bugzilla T-Shirt On 7/15/05, Zach Lipton wrote: > > On Jul 15, 2005, at 11:29 AM, David Miller wrote: > > > Zach Lipton wrote: > > > > > >> The Mozilla Store is going to be reopening soon (finally!) and one > >> of the items that we're looking to offer is a Bugzilla t-shirt. We > >> are thinking of using the bug on bugzilla.mozilla.org for the main > >> image > >> > > > > Oh, THAT bug? I thought Marcia wanted "Buggy" (the cartoon guy from > > bugzilla.org), that's the EPS file I mailed her. I have no clue > > where the electron microscope thing came from. :) That was well > > before my time. > > > Sorry. My mistake. I did mean "Buggy," he's far cuter for a t-shirt > anyway... > > Tagline suggestions would be great. How about "This bug's for you" :) Can the t-shirt be black?? :) katsu - To view or change your list settings, click here: From gerv at mozilla.org Fri Jul 15 19:40:17 2005 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 15 Jul 2005 20:40:17 +0100 Subject: Bugzilla T-Shirt In-Reply-To: <082070A4-82E7-481C-8BC4-6CC52C4A830C@zachlipton.com> References: <42D800A6.30401@bugzilla.org> <082070A4-82E7-481C-8BC4-6CC52C4A830C@zachlipton.com> Message-ID: <42D81121.8050907@mozilla.org> Zach Lipton wrote: > Tagline suggestions would be great. "He's cute. Squash him anyway." "Bugzilla. Because Post-Its don't cut it". "Bugzilla. Because Excel doesn't". "Bugzilla is server software designed to help you manage software development." (Or maybe not.) Gerv From mkanat at bugzilla.org Fri Jul 15 23:27:27 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Fri, 15 Jul 2005 16:27:27 -0700 Subject: QA team In-Reply-To: <42D7D6CC.4050104@gmx.net> References: <42D7B9F9.6050709@gmail.com> <42D7D6CC.4050104@gmx.net> Message-ID: <1121470048.5458.11.camel@localhost.localdomain> On Fri, 2005-07-15 at 11:31 -0400, Mick Weiss wrote: > I just had a thought though, would someone be willing to setup a box > with Bugzilla on Windows or Bugzilla w/ Postgresql for use with testing? http://landfill.bugzilla.org/bugzilla-tip-pg/ Also, if you'd like access to the landfill installation-creating tools and SSH access to landfill, you can make a case to me that you ought to have such access for testing PostgreSQL. In addition, though, you're right -- a Windows testing machine would be nice. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From bugreport at peshkin.net Sat Jul 16 17:40:59 2005 From: bugreport at peshkin.net (Joel Peshkin) Date: Sat, 16 Jul 2005 10:40:59 -0700 Subject: Bugzilla T-Shirt In-Reply-To: References: Message-ID: <42D946AB.2050308@peshkin.net> A nice dark color background would be good. How about doing polo shirts as well? By the way, this would be a great prize for me to give people for filing good bug reports. From justdave at bugzilla.org Sun Jul 17 01:24:19 2005 From: justdave at bugzilla.org (David Miller) Date: Sat, 16 Jul 2005 21:24:19 -0400 Subject: Bugzilla T-Shirt In-Reply-To: <42D946AB.2050308@peshkin.net> References: <42D946AB.2050308@peshkin.net> Message-ID: <42D9B343.3080807@bugzilla.org> Joel Peshkin wrote: > A nice dark color background would be good. How about doing polo shirts > as well? Ya know, that's a good idea. I'd love to have a polo shirt with the Bugzilla logo on it, similar to the one the old store sold with the Firefox logo on it. Given the existing color scheme of the Bugzilla logo, I'd imagine tan would be a good color for the polo shirt (The Firefox one was an olive green I think) -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From jremillardshop at letterboxes.org Sun Jul 17 01:41:12 2005 From: jremillardshop at letterboxes.org (Jason Remillard) Date: Sat, 16 Jul 2005 21:41:12 -0400 Subject: Bugzilla T-Shirt In-Reply-To: References: Message-ID: <42D9B738.4070909@letterboxes.org> Hi, Zach Lipton wrote: > * A tagline to put on the back tagline: Zarro Boogs Jason From spam at tachegroup.com Sun Jul 17 03:13:17 2005 From: spam at tachegroup.com (TGS) Date: Sat, 16 Jul 2005 23:13:17 -0400 Subject: Bugzilla T-Shirt In-Reply-To: <42D9B343.3080807@bugzilla.org> References: <42D946AB.2050308@peshkin.net> <42D9B343.3080807@bugzilla.org> Message-ID: <5bc86d927357720bf7b0ad46c0eb1538@tachegroup.com> I second a Polo - T-shirts do work in some corporate environments. On Jul 16, 2005, at 9:24 PM, David Miller wrote: > Joel Peshkin wrote: >> A nice dark color background would be good. How about doing polo >> shirts as well? > > Ya know, that's a good idea. I'd love to have a polo shirt with the > Bugzilla logo on it, similar to the one the old store sold with the > Firefox logo on it. Given the existing color scheme of the Bugzilla > logo, I'd imagine tan would be a good color for the polo shirt (The > Firefox one was an olive green I think) > > -- > Dave Miller http://www.justdave.net/ > System Administrator, Mozilla Foundation http://www.mozilla.org/ > Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ > - > To view or change your list settings, click here: > > From zach at zachlipton.com Sun Jul 17 03:26:27 2005 From: zach at zachlipton.com (Zach Lipton) Date: Sat, 16 Jul 2005 20:26:27 -0700 Subject: Bugzilla T-Shirt In-Reply-To: <42D9B343.3080807@bugzilla.org> References: <42D946AB.2050308@peshkin.net> <42D9B343.3080807@bugzilla.org> Message-ID: On Jul 16, 2005, at 6:24 PM, David Miller wrote: > Joel Peshkin wrote: > >> A nice dark color background would be good. How about doing polo >> shirts as well? >> > > Ya know, that's a good idea. I'd love to have a polo shirt with > the Bugzilla logo on it, similar to the one the old store sold with > the Firefox logo on it. Given the existing color scheme of the > Bugzilla logo, I'd imagine tan would be a good color for the polo > shirt (The Firefox one was an olive green I think) I agree that a polo would be nice (not that I often find myself in situations where a Bugzilla polo would be appropriate but a t-shirt would not ;). Marcia said that the store is going to be starting with a T-Shirt though, and that we can investigate a polo and other offerings once the shirt is done. Polos cost more then shirts and presumably don't sell as well, so I think she wants to get going with the shirt first. --zach From bugreport at peshkin.net Sun Jul 17 03:57:21 2005 From: bugreport at peshkin.net (Joel Peshkin) Date: Sat, 16 Jul 2005 20:57:21 -0700 Subject: Bugzilla T-Shirt In-Reply-To: References: <42D946AB.2050308@peshkin.net> <42D9B343.3080807@bugzilla.org> Message-ID: <42D9D721.6080007@peshkin.net> Zach Lipton wrote: > I agree that a polo would be nice (not that I often find myself in > situations where a Bugzilla polo would be appropriate but a t-shirt > would not ;). Marcia said that the store is going to be starting with > a T-Shirt though, and that we can investigate a polo and other > offerings once the shirt is done. Polos cost more then shirts and > presumably don't sell as well, so I think she wants to get going with > the shirt first. > > --zach I could be willing to seed this with an order for enough of the polos (12 or so) to get over that hump. If you publish the proposed shirt details and pricing, I'll look at what it takes to pre-order enough to get that started. -Joel From spam at tachegroup.com Sun Jul 17 05:39:24 2005 From: spam at tachegroup.com (TGS) Date: Sun, 17 Jul 2005 01:39:24 -0400 Subject: Bugzilla T-Shirt In-Reply-To: <42D9D721.6080007@peshkin.net> References: <42D946AB.2050308@peshkin.net> <42D9B343.3080807@bugzilla.org> <42D9D721.6080007@peshkin.net> Message-ID: Also, I think Buggy on a dark blue (Navy) Polo, as in the default theme would be just dandy. On Jul 16, 2005, at 11:57 PM, Joel Peshkin wrote: > Zach Lipton wrote: > >> I agree that a polo would be nice (not that I often find myself in >> situations where a Bugzilla polo would be appropriate but a t-shirt >> would not ;). Marcia said that the store is going to be starting with >> a T-Shirt though, and that we can investigate a polo and other >> offerings once the shirt is done. Polos cost more then shirts and >> presumably don't sell as well, so I think she wants to get going with >> the shirt first. >> >> --zach > > I could be willing to seed this with an order for enough of the polos > (12 or so) to get over that hump. If you publish the proposed shirt > details and pricing, I'll look at what it takes to pre-order enough to > get that started. > > -Joel > > - > To view or change your list settings, click here: > > From LpSolit at gmail.com Sun Jul 17 12:37:18 2005 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Sun, 17 Jul 2005 14:37:18 +0200 Subject: Bugzilla T-Shirt In-Reply-To: <42D9B738.4070909@letterboxes.org> References: <42D9B738.4070909@letterboxes.org> Message-ID: <42DA50FE.4060303@gmail.com> Jason Remillard a ?crit : >> * A tagline to put on the back > > > tagline: Zarro Boogs Haha! Yes, I like this one! :) From gerv at mozilla.org Sun Jul 17 14:19:28 2005 From: gerv at mozilla.org (Gervase Markham) Date: Sun, 17 Jul 2005 15:19:28 +0100 Subject: Bugzilla T-Shirt In-Reply-To: <42DA50FE.4060303@gmail.com> References: <42D9B738.4070909@letterboxes.org> <42DA50FE.4060303@gmail.com> Message-ID: <42DA68F0.6010301@mozilla.org> Fr?d?ric Buclin wrote: > Jason Remillard a ?crit : >> tagline: Zarro Boogs > > Haha! Yes, I like this one! :) It's been used before on a t-shirt to mean something different. Here's the explanation: http://www.faqs.org/docs/bugzilla/glossary.html#gloss-zarro Zarro Boogs isn't really a Bugzilla thing, it's a Netscape thing. And I don't think it's real meaning fits well with our t-shirts. After all, our software's not buggy :-) Gerv From LpSolit at gmail.com Sun Jul 17 14:36:43 2005 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Sun, 17 Jul 2005 16:36:43 +0200 Subject: Bugzilla T-Shirt In-Reply-To: <42DA68F0.6010301@mozilla.org> References: <42D9B738.4070909@letterboxes.org> <42DA50FE.4060303@gmail.com> <42DA68F0.6010301@mozilla.org> Message-ID: <42DA6CFB.2050604@gmail.com> > It's been used before on a t-shirt to mean something different. Here's > the explanation: > http://www.faqs.org/docs/bugzilla/glossary.html#gloss-zarro > > Zarro Boogs isn't really a Bugzilla thing, it's a Netscape thing. And I > don't think it's real meaning fits well with our t-shirts. After all, > our software's not buggy :-) I know this explanation already. And I think it's very appropriate here. Some humor doesn't hurt at all. And when I said "I like it", I had this definition of "Zarro Boogs" in mind already. Fred From Guillaume.Rousse at inria.fr Mon Jul 18 19:32:33 2005 From: Guillaume.Rousse at inria.fr (Guillaume Rousse) Date: Mon, 18 Jul 2005 21:32:33 +0200 Subject: Linux installation Message-ID: <42DC03D1.1040402@inria.fr> I just found that the installation guide has a section about Mandrake 8.0, which is quite outdated. And there is no mention of other Linux distributions, such as Debian, whereas just running apt-get install bugzilla is enough. Rather than updating it, I rewrote it in a more general fashion for all Linux distributions. Here it is. -- If you can keep your head when all about you are losing theirs, maybe you just don't understand the situation -- Sad Truths of Life n?17 -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: installation.patch URL: From mkanat at bugzilla.org Mon Jul 18 21:05:43 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Mon, 18 Jul 2005 14:05:43 -0700 Subject: 2.20: Status, How You Can Help Message-ID: <1121720744.3919.3.camel@localhost.localdomain> Hey hey! So, we're nine days away from the target release date for Bugzilla 2.20. Here is the list of blockers: http://tinyurl.com/9565b Right now there are 14 blockers there, but most of them have patches. If one of those patches is awaiting your review, do it today or tomorrow! :-) If one of those bugs is assigned to you and needs a new patch, get a new patch on it (today or tomorrow). :-) Finally, some of the bugs listed are "NEW" meaning that they have no patch. These are the bugs we need the *most* help with! Pleeeeease, somebody, get us some patches on those bugs! :-) We'll be your new best friends. :-) -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From wurblzap at gmail.com Mon Jul 18 22:14:37 2005 From: wurblzap at gmail.com (Marc Schumann) Date: Tue, 19 Jul 2005 00:14:37 +0200 Subject: Linux installation In-Reply-To: <42DC03D1.1040402@inria.fr> References: <42DC03D1.1040402@inria.fr> Message-ID: Guillaume, 2005/7/18, Guillaume Rousse : > I just found that the installation guide has a section about Mandrake > 8.0, which is quite outdated. And there is no mention of other Linux > distributions, such as Debian, whereas just running apt-get install > bugzilla is enough. Rather than updating it, I rewrote it in a more > general fashion for all Linux distributions. Here it is. while I'm entirely unable to judge your patch, I think it should undergo the normal review process. This involves your patch getting attached to the corresponding bug in Bugzilla (please file a new bug if the bug doesn't exist yet) and ask for review (by setting review? on your patch attachment). Please do so -- you may experience some useful feedback, and it enhances visibility and the chance of your patch actually getting checked in :) Kind regards Marc -- http://wurblzap.net/ Bugzilla hosting and professional support From stethomas at ebay.com Tue Jul 19 20:40:17 2005 From: stethomas at ebay.com (Thomas, Steve) Date: Tue, 19 Jul 2005 14:40:17 -0600 Subject: Screen shots for Bugzilla Message-ID: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> Hello folks, Our users like to use the Windows Print Screen functionality to quickly paste a screenshot of a bug into email. Now that we're moving them to Bugzilla I'd like to try to get them something similar. I can probably hack something together myself, but does anybody know if anybody else has done this? In short, I'd like: a) The Bug Entry page to allow attachments (yes, I know, there is no Bug ID yet, so that is a pain) b) An attachment to be cut/pasted into a buffer and then saved into a JPG Thanks, Steve Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From LpSolit at gmail.com Tue Jul 19 20:59:25 2005 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Tue, 19 Jul 2005 22:59:25 +0200 Subject: Screen shots for Bugzilla In-Reply-To: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> Message-ID: <42DD69AD.4050907@gmail.com> > a) The Bug Entry page to allow attachments (yes, I know, there is no > Bug ID yet, so that is a pain) This feature is discussed in bug 5179. From zach at zachlipton.com Tue Jul 19 21:01:59 2005 From: zach at zachlipton.com (Zach Lipton) Date: Tue, 19 Jul 2005 14:01:59 -0700 Subject: Screen shots for Bugzilla In-Reply-To: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> Message-ID: <8F2E99D7-E562-4A80-AD4F-8BDB78870E55@zachlipton.com> On Jul 19, 2005, at 1:40 PM, Thomas, Steve wrote: > Our users like to use the Windows Print Screen functionality to > quickly paste a screenshot of a bug into email. First of all, does this mean that Ebay is going to be using Bugzilla? If so, cool! :-) > a) The Bug Entry page to allow attachments (yes, I know, there > is no Bug ID yet, so that is a pain) This likely wouldn't take too much work. Add a file upload field to the enter bug template and then adjust post_bug.cgi to create a new attachment after the bug itself is created (basically just copy insert () from attachment.cgi). Of course, you'll need to add the new attachment ID to the bug. > b) An attachment to be cut/pasted into a buffer and then saved > into a JPG This creates a much different sort of problem. HTML doesn't have a tag for a widget that you can copy/paste an image into (mac users would call this an image well). Users would have to copy their screengrabs into an image editing program and save them as a JPG manually. If you really had the time and inclination to do this, you could build a custom XUL application that your users would copy/paste images into and have them uploaded to Bugzilla, but that would only work in Mozilla and Firefox and would involve a fair amount of difficulty. Presumably, there is some kind of ActiveX control that could be built to accomplish the same effect. Alternatively, you could teach your users how to properly use the email bug submission gateway (the script and documentation are in bugzilla/contrib) and let them attach a screenshot to their email and have it submitted that way. The downside is that everyone submitting bugs through email needs to know how to specify the fields properly (e.g. they have to pick a valid product and component and format their email according to bugmail_help.html). Hope this helps, --zach From stethomas at ebay.com Tue Jul 19 21:32:11 2005 From: stethomas at ebay.com (Thomas, Steve) Date: Tue, 19 Jul 2005 15:32:11 -0600 Subject: Screen shots for Bugzilla Message-ID: <8E1982313133E740ABCCF578C7060FEC0589B725@DEN-EXM-02.corp.ebay.com> Zach Lipton wrote: > On Jul 19, 2005, at 1:40 PM, Thomas, Steve wrote: >> Our users like to use the Windows Print Screen functionality to >> quickly paste a screenshot of a bug into email. > > First of all, does this mean that Ebay is going to be using Bugzilla? > If so, cool! :-) eBay has been using Bugzilla on various projects for quite sometime, as I understand it. Note that this is for INTERNAL DEVELOPMENT of IT projects here not end-users of ebay.com etc. As for a), yes, I thought about that. Simply adding the attachment widget to the Enter Bug page would be a good start. As for the email bug submission gateway, I will check that out--that may in fact be the solution if I can get LookOut! to cooperate. Thanks for your help, Steve Thomas -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Zach Lipton Sent: Tuesday, July 19, 2005 2:02 PM To: developers at bugzilla.org Subject: Re: Screen shots for Bugzilla > a) The Bug Entry page to allow attachments (yes, I know, there > is no Bug ID yet, so that is a pain) This likely wouldn't take too much work. Add a file upload field to the enter bug template and then adjust post_bug.cgi to create a new attachment after the bug itself is created (basically just copy insert () from attachment.cgi). Of course, you'll need to add the new attachment ID to the bug. > b) An attachment to be cut/pasted into a buffer and then saved > into a JPG This creates a much different sort of problem. HTML doesn't have a tag for a widget that you can copy/paste an image into (mac users would call this an image well). Users would have to copy their screengrabs into an image editing program and save them as a JPG manually. If you really had the time and inclination to do this, you could build a custom XUL application that your users would copy/paste images into and have them uploaded to Bugzilla, but that would only work in Mozilla and Firefox and would involve a fair amount of difficulty. Presumably, there is some kind of ActiveX control that could be built to accomplish the same effect. Alternatively, you could teach your users how to properly use the email bug submission gateway (the script and documentation are in bugzilla/contrib) and let them attach a screenshot to their email and have it submitted that way. The downside is that everyone submitting bugs through email needs to know how to specify the fields properly (e.g. they have to pick a valid product and component and format their email according to bugmail_help.html). Hope this helps, --zach - To view or change your list settings, click here: From gerv at mozilla.org Wed Jul 20 20:05:01 2005 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 20 Jul 2005 21:05:01 +0100 Subject: Screen shots for Bugzilla In-Reply-To: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> Message-ID: <42DEAE6D.7010008@mozilla.org> Thomas, Steve wrote: > Our users like to use the Windows Print Screen functionality to quickly > paste a screenshot of a bug into email. > > Now that we?re moving them to Bugzilla I?d like to try to get them > something similar. I can probably hack something together myself, but > does anybody know if anybody else has done this? Apart from Joel Spolsky for FogBugz? ;-) Probably the smoothest way would be for you to write a tray icon app which read the clipboard, created an image file, and attached it to a given bug number. So you press Alt-PrtScrn, click on the tray icon, and enter the bug number in the box which pops up. Gerv From jpyeron at pdinc.us Wed Jul 20 20:35:50 2005 From: jpyeron at pdinc.us (Jason Pyeron) Date: Wed, 20 Jul 2005 16:35:50 -0400 (EDT) Subject: Screen shots for Bugzilla In-Reply-To: <42DEAE6D.7010008@mozilla.org> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> <42DEAE6D.7010008@mozilla.org> Message-ID: Wouldn't a signed java applet be best suited for this? It would be as system indipendant as possible (save the java dep) then the attachment page could have a button besides Browse, all else the same the browser would take the BASE64 data from the applet on post. On Wed, 20 Jul 2005, Gervase Markham wrote: > Thomas, Steve wrote: >> Our users like to use the Windows Print Screen functionality to quickly >> paste a screenshot of a bug into email. >> >> Now that we?re moving them to Bugzilla I?d like to try to get them >> something similar. I can probably hack something together myself, but does >> anybody know if anybody else has done this? > > Apart from Joel Spolsky for FogBugz? ;-) > > Probably the smoothest way would be for you to write a tray icon app which > read the clipboard, created an image file, and attached it to a given bug > number. So you press Alt-PrtScrn, click on the tray icon, and enter the bug > number in the box which pops up. > > Gerv > - > To view or change your list settings, click here: > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Partner & Sr. Manager 7 West 24th Street #100 - - +1 (443) 921-0381 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. From gerv at mozilla.org Wed Jul 20 21:37:17 2005 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 20 Jul 2005 22:37:17 +0100 Subject: Screen shots for Bugzilla In-Reply-To: References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> <42DEAE6D.7010008@mozilla.org> Message-ID: <42DEC40D.7030506@mozilla.org> Jason Pyeron wrote: > Wouldn't a signed java applet be best suited for this? > > It would be as system indipendant as possible (save the java dep) Well, I think taking the screenshot (or reading the clipboard) would be system-specific code, wouldn't it? > then the attachment page could have a button besides Browse, all else > the same the browser would take the BASE64 data from the applet on post. That could be done, although it would require Java-to-JS communication. Gerv From andreas.hoefler at bearingpoint.com Thu Jul 21 06:08:15 2005 From: andreas.hoefler at bearingpoint.com (=?ISO-8859-1?Q?Andreas_H=F6fler?=) Date: Thu, 21 Jul 2005 08:08:15 +0200 Subject: asterisk integration In-Reply-To: References: Message-ID: <42DF3BCF.1020802@bearingpoint.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- *************************************************************************************************** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *************************************************************************************************** From jpyeron at pdinc.us Thu Jul 21 13:55:21 2005 From: jpyeron at pdinc.us (Jason Pyeron) Date: Thu, 21 Jul 2005 09:55:21 -0400 (EDT) Subject: asterisk integration In-Reply-To: <42DF3BCF.1020802@bearingpoint.com> References: <42DF3BCF.1020802@bearingpoint.com> Message-ID: On Thu, 21 Jul 2005, [ISO-8859-1] Andreas H?fler wrote: > How should this make any sense? > Asterisk is an open source PBX (telephone system). It is capable of doing IVR (interactive voice response). It could be as simple as dial the bug number and it would say this bug is RESOLVED as of June 14, 2005. etc. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Partner & Sr. Manager 7 West 24th Street #100 - - +1 (443) 921-0381 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. From kiko at async.com.br Thu Jul 21 10:33:19 2005 From: kiko at async.com.br (Christian Robottom Reis) Date: Thu, 21 Jul 2005 07:33:19 -0300 Subject: Screen shots for Bugzilla In-Reply-To: <42DEAE6D.7010008@mozilla.org> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> <42DEAE6D.7010008@mozilla.org> Message-ID: <20050721103319.GC26863@www.async.com.br> On Wed, Jul 20, 2005 at 09:05:01PM +0100, Gervase Markham wrote: > Probably the smoothest way would be for you to write a tray icon app > which read the clipboard, created an image file, and attached it to a > given bug number. So you press Alt-PrtScrn, click on the tray icon, and > enter the bug number in the box which pops up. Or even have clicking on the tray icon take the screenshot for you. I don't know how large the risk is of hitting the icon by mistake, though I don't imagine it would be particularly annoying (you get the popup dialog and cancel it). Take care, -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125 From mkanat at bugzilla.org Thu Jul 21 18:35:16 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 21 Jul 2005 11:35:16 -0700 Subject: Screen shots for Bugzilla In-Reply-To: <20050721103319.GC26863@www.async.com.br> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> <42DEAE6D.7010008@mozilla.org> <20050721103319.GC26863@www.async.com.br> Message-ID: <1121970916.3401.3.camel@localhost.localdomain> On Thu, 2005-07-21 at 07:33 -0300, Christian Robottom Reis wrote: > Or even have clicking on the tray icon take the screenshot for you. I > don't know how large the risk is of hitting the icon by mistake, though > I don't imagine it would be particularly annoying (you get the popup > dialog and cancel it). Yeah, that's how it works in GNOME, if you add the Screenshot icon to your tray. In my experience, it's very unlikely that I'll click on it by accident, and then yes, quite easy to cancel the dialog if I ever did. :-) -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From micklweiss at gmx.net Thu Jul 21 21:31:53 2005 From: micklweiss at gmx.net (Mick Weiss) Date: Thu, 21 Jul 2005 17:31:53 -0400 Subject: Bugzilla T-Shirt In-Reply-To: <42D9B738.4070909@letterboxes.org> References: <42D9B738.4070909@letterboxes.org> Message-ID: <42E01449.4060603@gmx.net> Jason Remillard wrote: > Hi, > > Zach Lipton wrote: > >> * A tagline to put on the back > > > tagline: Zarro Boogs I like it :-) - Mick > > Jason > - > To view or change your list settings, click here: > > > From Guillaume.Rousse at inria.fr Thu Jul 21 21:39:13 2005 From: Guillaume.Rousse at inria.fr (Guillaume Rousse) Date: Thu, 21 Jul 2005 23:39:13 +0200 Subject: problems with mail interface Message-ID: <42E01601.40701@inria.fr> I got some questions about the mail interface... First, it's a bit hard to figure what files exactly compose it. It seems they are the following ones: - bugzilla_email_append.pl to add new comments to an existing bug - bug_email.pl to add new bugs - BugzillaEmail.pm - bugmail_help.html - README.Mailif - bugzilla.procmailrc Wheras the following one are not related, despite the name: - sendunsentbugmail.pl - sendbugmail.pl Second, I found several problem using it: - uncoherent naming (bug_email vs bugzilla_email) - hardcoded configuration value (from header) - need to use procmail for picking the correct one - missing features (no way to close a bug) I've some ideas for solving those issues, such as merging those scripts, using a parameters for the from header in the bugzilla configuration, and completing features. Any interest ? -- Friendly fire isn't -- Murphy's Military Laws n?62 From micklweiss at gmx.net Thu Jul 21 22:21:29 2005 From: micklweiss at gmx.net (Mick Weiss) Date: Thu, 21 Jul 2005 18:21:29 -0400 Subject: asterisk integration In-Reply-To: References: <42DF3BCF.1020802@bearingpoint.com> Message-ID: <42E01FE9.2060204@gmx.net> Jason Pyeron wrote: > On Thu, 21 Jul 2005, [ISO-8859-1] Andreas H?fler wrote: > >> How should this make any sense? >> > > Asterisk is an open source PBX (telephone system). It is capable of > doing IVR (interactive voice response). > > It could be as simple as dial the bug number and it would say this bug > is RESOLVED as of June 14, 2005. etc. > If your a programmer, this should be easy enough to do (if you only want that functionality). I don't find this all too exciting though. More of a proof of concept than anything. Any other examples besides calling your office to see if a bug is fixed? - Mick From mkanat at bugzilla.org Fri Jul 22 02:23:48 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 21 Jul 2005 19:23:48 -0700 Subject: Bugzilla T-Shirt In-Reply-To: References: Message-ID: <1121999029.3371.6.camel@localhost.localdomain> On Fri, 2005-07-15 at 09:36 -0700, Zach Lipton wrote: > * A tagline to put on the back There's always "Got Bugs?" -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From Chris.Raplee at portalplayer.com Fri Jul 22 04:41:38 2005 From: Chris.Raplee at portalplayer.com (Chris Raplee) Date: Thu, 21 Jul 2005 21:41:38 -0700 Subject: Bugzilla T-Shirt Message-ID: <59FA134614736A4AB04061CA4B07908C07ECE3@peach.portalplayersc.com> I like it! --Chris Raplee Now, we must all fear evil men. But there is another kind of evil which we must fear most, and that is the indifference of good men. -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Max Kanat-Alexander Sent: Thursday, July 21, 2005 7:24 PM To: developers at bugzilla.org Subject: Re: Bugzilla T-Shirt On Fri, 2005-07-15 at 09:36 -0700, Zach Lipton wrote: > * A tagline to put on the back There's always "Got Bugs?" -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. - To view or change your list settings, click here: From gerv at mozilla.org Fri Jul 22 16:31:34 2005 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 22 Jul 2005 17:31:34 +0100 Subject: Absence Message-ID: <42E11F66.6060900@mozilla.org> Dear developers, I will be away from Saturday 23rd of June until Monday 8th August, so please do not expect any email replies during that time. :-) If some of my bugs are blockers, please do whatever is necessary to make them not so. I apologise (again) for my continual suckage on this point. Gerv From ghendricks at novell.com Fri Jul 22 21:20:20 2005 From: ghendricks at novell.com (Gregary Hendricks) Date: Fri, 22 Jul 2005 15:20:20 -0600 Subject: Screen shots for Bugzilla In-Reply-To: <42DEAE6D.7010008@mozilla.org> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> <42DEAE6D.7010008@mozilla.org> Message-ID: <42E10EB4.3532.00D2.0@novell.com> On Wednesday 20 July 2005 14:05, Gervase Markham wrote: > Thomas, Steve wrote: > > Our users like to use the Windows Print Screen functionality to quickly > > paste a screenshot of a bug into email. > > > > Now that we're moving them to Bugzilla I'd like to try to get them > > something similar. I can probably hack something together myself, but > > does anybody know if anybody else has done this? > > Apart from Joel Spolsky for FogBugz? ;-) > > Probably the smoothest way would be for you to write a tray icon app > which read the clipboard, created an image file, and attached it to a > given bug number. So you press Alt-PrtScrn, click on the tray icon, and > enter the bug number in the box which pops up. > > Gerv > - There are a number of apps for windows that do this already. I can't recall off the top of my head a name but I know I have used some in the past. One thing to watch out for that has caused us some consternation is that many of the windows apps (MS Paint especially) saves the screen shot as an uncompressed bmp file which can eat up disk space in a hurry. We have added a little hack to bugzilla to automatically convert bmp to png files when they are attached. If there is any interest i can send a patch. > To view or change your list settings, click here: > -- Greg Hendricks Novell IS&T Engineer GHendricks at novell.com Office: (801) 861-3481 www.novell.com From ghendricks at novell.com Fri Jul 22 21:35:57 2005 From: ghendricks at novell.com (Gregary Hendricks) Date: Fri, 22 Jul 2005 15:35:57 -0600 Subject: Bugzilla T-Shirt Message-ID: <42E1125D.3532.00D2.0@novell.com> On Saturday 16 July 2005 21:57, Joel Peshkin wrote: > Zach Lipton wrote: > > I agree that a polo would be nice (not that I often find myself in > > situations where a Bugzilla polo would be appropriate but a t-shirt > > would not ;). Marcia said that the store is going to be starting with > > a T-Shirt though, and that we can investigate a polo and other > > offerings once the shirt is done. Polos cost more then shirts and > > presumably don't sell as well, so I think she wants to get going with > > the shirt first. > > > > --zach > > I could be willing to seed this with an order for enough of the polos > (12 or so) to get over that hump. If you publish the proposed shirt > details and pricing, I'll look at what it takes to pre-order enough to > get that started. > > -Joel > > - I could second that with another half dozen or so and possibly more down the line. Plus having some T-shirts for good bug submissions is a wonderful idea. -- Greg Hendricks Novell IS&T Engineer GHendricks at novell.com Office: (801) 861-3481 www.novell.com From eseyman at linagora.com Fri Jul 22 22:03:57 2005 From: eseyman at linagora.com (Emmanuel Seyman) Date: Sat, 23 Jul 2005 00:03:57 +0200 (CEST) Subject: Bugzilla T-Shirt In-Reply-To: <42E1125D.3532.00D2.0@novell.com> References: <42E1125D.3532.00D2.0@novell.com> Message-ID: <49940.192.168.1.254.1122069837.squirrel@tomate.linagora.lan> Gregary Hendricks wrote: > > I could second that with another half dozen or so and possibly more > down the line. I'll third it with 4-6 polos. Emmanuel From kevin.benton at amd.com Fri Jul 22 22:06:32 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Fri, 22 Jul 2005 15:06:32 -0700 Subject: Bugzilla T-Shirt Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42018CEA59@ssvlexmb2.amd.com> > I could second that with another half dozen or so and possibly more > down the line. > Plus having some T-shirts for good bug submissions is a wonderful > idea. How about T-Shirts for Bugzilla fixes! :) --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. From luis.villa at gmail.com Fri Jul 22 22:09:58 2005 From: luis.villa at gmail.com (Luis Villa) Date: Fri, 22 Jul 2005 18:09:58 -0400 Subject: Bugzilla T-Shirt In-Reply-To: <49940.192.168.1.254.1122069837.squirrel@tomate.linagora.lan> References: <42E1125D.3532.00D2.0@novell.com> <49940.192.168.1.254.1122069837.squirrel@tomate.linagora.lan> Message-ID: <2cb10c4405072215097460e5cf@mail.gmail.com> On 7/22/05, Emmanuel Seyman wrote: > Gregary Hendricks wrote: > > > > I could second that with another half dozen or so and possibly more > > down the line. > > I'll third it with 4-6 polos. I'll take one :) Luis From mkanat at bugzilla.org Sat Jul 23 07:51:16 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 23 Jul 2005 00:51:16 -0700 Subject: Version on bmo vs (future) bbo Message-ID: <1122105076.8419.1.camel@localhost.localdomain> So, I was thinking that perhaps bmo should be our testing ground for stable releases, and bugzilla.bugzilla.org (which is hopefully coming within the next few months, I think) should be our testing ground for tip code. Then we'd have something constantly running a stable branch and getting tested, making our stable branches even more stable. We could upgrade bmo every time we have an RC on a branch. -Max From kiffin at gish.demon.nl Sat Jul 23 08:17:26 2005 From: kiffin at gish.demon.nl (Kiffin Gish) Date: Sat, 23 Jul 2005 10:17:26 +0200 Subject: CC-feld as a dropdown list ... Message-ID: <000b01c58f5e$f5f418c0$2201a8c0@ZGISH> In Bugzilla the CC-field is a free form email-address text field, meaning that if there is some guess work involved or the user misspells the email address, he/she gets a cryptic error message back. Would it be feasible to create a dropdown via a db-select so that the user has a list of names to choose from istead? If so, then how would I go about doing this? Thanks a lot in advance. -- Kiffin Rex Gish Gouda, The Netherlands -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 3488 bytes Desc: not available URL: From bugzilla at colinogilvie.co.uk Sat Jul 23 08:30:03 2005 From: bugzilla at colinogilvie.co.uk (Colin Ogilvie) Date: Sat, 23 Jul 2005 09:30:03 +0100 Subject: CC-feld as a dropdown list ... In-Reply-To: <000b01c58f5e$f5f418c0$2201a8c0@ZGISH> References: <000b01c58f5e$f5f418c0$2201a8c0@ZGISH> Message-ID: <42E2000B.2060708@colinogilvie.co.uk> Kiffin Gish wrote: > In Bugzilla the CC-field is a free form email-address text field, meaning > that if there is some guess work involved or the user misspells the email > address, he/she gets a cryptic error message back. > > Would it be feasible to create a dropdown via a db-select so that the user > has a list of names to choose from istead? > > If so, then how would I go about doing this? In Bugzilla 2.20 (currently in the RC1 stage) there is the ability to specify this behaviour through the user of a parameter. https://bugzilla.mozilla.org/show_bug.cgi?id=251669 is about this behaviour - although note it also adds it for QA Contact and Assigned To as well. Colin -- Colin Ogilvie bugzilla at colinogilvie.co.uk From myk at mozilla.org Sat Jul 23 08:49:06 2005 From: myk at mozilla.org (Myk Melez) Date: Sat, 23 Jul 2005 01:49:06 -0700 Subject: Bugzilla UI hackathon #1: July 29; attachments Message-ID: <42E20482.9040300@mozilla.org> Now that the tree is open for 2.22 development, it's time to start the UI hackathons. The first one will be next Friday, July 29, from 10am-6pm PDT (UTC-07:00). It'll focus on attachment UI, from the "edit attachment" page to the "create an attachment" page, the "show bug" attachments table, and attachment references in comments. Basically, anywhere there is (or should be) UI for accessing or manipulating attachments is fair game for hacking. I'll be on irc.mozilla.org in the #hackathon channel for the entire hackathon to discuss problems, approve solutions, and review patches. We'll start by looking over existing bugs, brainstorming new ideas, prioritizing fixes that can happen within a day, and dividing up the work between available hackers. Where possible, we'll make decisions by consensus. Otherwise, we'll air our respective views, and then I'll make a decision or defer the issue to further discussion. I welcome the participation of all Bugzilla hackers and users who want to contribute to improving this important piece of Bugzilla functionality! -myk -------------- next part -------------- An HTML attachment was scrubbed... URL: From djm at mindrot.org Sat Jul 23 11:07:35 2005 From: djm at mindrot.org (Damien Miller) Date: Sat, 23 Jul 2005 21:07:35 +1000 Subject: Bugzilla UI hackathon #1: July 29; attachments In-Reply-To: <42E20482.9040300@mozilla.org> References: <42E20482.9040300@mozilla.org> Message-ID: <42E224F7.7020304@mindrot.org> Myk Melez wrote: > > Now that the tree is open for 2.22 development, it's time to start the > UI hackathons. The first one will be next Friday, July 29, from > 10am-6pm PDT (UTC-07:00). It'll focus on attachment UI, from the "edit > attachment" page to the "create an attachment" page, the "show bug" > attachments table, and attachment references in comments. One thing I hack into OpenSSH's bugzilla is a message above the comment entry box: "Do not enter patches, source code or long debug traces here. Please use the Attachments feature instead." This is borne of frustration of users pasting huge gobs of text into comments, especially patches. Could you please consider adding a similar message, or perhaps a automatic warning if a comment is over a certain number of lines? -d From myk at mozilla.org Sat Jul 23 15:50:27 2005 From: myk at mozilla.org (Myk Melez) Date: Sat, 23 Jul 2005 08:50:27 -0700 Subject: Bugzilla UI hackathon #1: July 29; attachments In-Reply-To: <42E224F7.7020304@mindrot.org> References: <42E20482.9040300@mozilla.org> <42E224F7.7020304@mindrot.org> Message-ID: <42E26743.8020204@mozilla.org> Damien Miller wrote: > One thing I hack into OpenSSH's bugzilla is a message above the comment > entry box: "Do not enter patches, source code or long debug traces here. > Please use the Attachments feature instead." > > This is borne of frustration of users pasting huge gobs of text into > comments, especially patches. Could you please consider adding a similar > message, or perhaps a automatic warning if a comment is over a certain > number of lines? That's a good idea. I bet we could count lines (or characters, more likely) with a JavaScript event handler and display a warning if the comment gets too long. -myk From luis.villa at gmail.com Sat Jul 23 16:06:01 2005 From: luis.villa at gmail.com (Luis Villa) Date: Sat, 23 Jul 2005 12:06:01 -0400 Subject: Bugzilla UI hackathon #1: July 29; attachments In-Reply-To: <42E26743.8020204@mozilla.org> References: <42E20482.9040300@mozilla.org> <42E224F7.7020304@mindrot.org> <42E26743.8020204@mozilla.org> Message-ID: <2cb10c4405072309062adb01ba@mail.gmail.com> On 7/23/05, Myk Melez wrote: > Damien Miller wrote: > > One thing I hack into OpenSSH's bugzilla is a message above the comment > > entry box: "Do not enter patches, source code or long debug traces here. > > Please use the Attachments feature instead." > > > > This is borne of frustration of users pasting huge gobs of text into > > comments, especially patches. Could you please consider adding a similar > > message, or perhaps a automatic warning if a comment is over a certain > > number of lines? > That's a good idea. I bet we could count lines (or characters, more > likely) with a JavaScript event handler and display a warning if the > comment gets too long. As long as it is easy to disable or modify. At b.g.o we require people to put traces into the body of the bug because they aren't searchable otherwise. Luis From myk at mozilla.org Sat Jul 23 16:15:27 2005 From: myk at mozilla.org (Myk Melez) Date: Sat, 23 Jul 2005 09:15:27 -0700 Subject: Bugzilla UI hackathon #1: July 29; attachments In-Reply-To: <2cb10c4405072309062adb01ba@mail.gmail.com> References: <42E20482.9040300@mozilla.org> <42E224F7.7020304@mindrot.org> <42E26743.8020204@mozilla.org> <2cb10c4405072309062adb01ba@mail.gmail.com> Message-ID: <42E26D1F.7030309@mozilla.org> Luis Villa wrote: > On 7/23/05, Myk Melez wrote: > >> I bet we could count lines (or characters, more >> likely) with a JavaScript event handler and display a warning if the >> comment gets too long. >> > > As long as it is easy to disable or modify. Sure. > At b.g.o we require people > to put traces into the body of the bug because they aren't searchable > otherwise. > Sounds like something we should fix. :-) -myk -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcia at mozilla.org Sat Jul 23 00:43:28 2005 From: marcia at mozilla.org (Marcia Knous) Date: Fri, 22 Jul 2005 17:43:28 -0700 Subject: Bugzilla t-shirt Message-ID: <42E192B0.7070905@mozilla.org> I am getting ready to go forward with the Bugzilla shirt to be sold at the Mozilla store. I know there has been some discussion regarding the tag line. I think some of the proposals may be too "esoteric" (zarro bugs) for our audience, so I am suggesting that we go with "Bugzilla: We take bugs seriously." I would like suggestions as to what color shirt people would like to see - I know that black was mentioned, but it might be cool to do a different color shirt than black. marcia From LpSolit at gmail.com Sat Jul 23 19:25:36 2005 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Sat, 23 Jul 2005 21:25:36 +0200 Subject: Bugzilla t-shirt In-Reply-To: <42E192B0.7070905@mozilla.org> References: <42E192B0.7070905@mozilla.org> Message-ID: <42E299B0.5090701@gmail.com> > I would like suggestions as to what color shirt people would like to see > - I know that black was mentioned, but it might be cool to do a > different color shirt than black. Using HTML colors: something like #d5d5d5 or #2a8c91 ? :) From mkanat at bugzilla.org Sat Jul 23 19:56:41 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 23 Jul 2005 12:56:41 -0700 Subject: Bugzilla t-shirt In-Reply-To: <42E192B0.7070905@mozilla.org> References: <42E192B0.7070905@mozilla.org> Message-ID: <1122148601.3345.1.camel@localhost.localdomain> On Fri, 2005-07-22 at 17:43 -0700, Marcia Knous wrote: > I am suggesting that we go with "Bugzilla: We take bugs seriously." Honestly, I wouldn't be too interested in that tag line. (As in, I probably wouldn't buy the shirt myself.) Also, at least on the list, we had considerably more interest in a polo than in a T-shirt -- I know that I myself probably wouldn't buy the T-Shirt, but I'd more likely buy the polo. We had at least 21 commitments to buy a polo if one was offered, I believe, in the other thread, although I'm not sure that's enough to seed an order. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From mkanat at bugzilla.org Sat Jul 23 20:21:58 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 23 Jul 2005 13:21:58 -0700 Subject: 2.20rc2 Message-ID: <1122150118.3843.1.camel@localhost.localdomain> The upcoming release of the Bugzilla development branch will be 2.20rc2, and not 2.20 final. 2.20 will not be in a state by Wednesday to be released, and it hasn't yet been tested on bugzilla.mozilla.org. Also, 2.20rc1 had a few significant bugs, and didn't seem quite stable enough to be our final release candidate. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From afranke at ags.uni-sb.de Sat Jul 23 22:24:31 2005 From: afranke at ags.uni-sb.de (Andreas Franke) Date: Sun, 24 Jul 2005 00:24:31 +0200 Subject: Bugzilla t-shirt In-Reply-To: <1122148601.3345.1.camel@localhost.localdomain> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> Message-ID: <42E2C39F.6020505@ags.uni-sb.de> Max Kanat-Alexander wrote: > On Fri, 2005-07-22 at 17:43 -0700, Marcia Knous wrote: > >>I am suggesting that we go with "Bugzilla: We take bugs seriously." > > Honestly, I wouldn't be too interested in that tag line. (As in, I > probably wouldn't buy the shirt myself.) Me too. Maybe I'm missing something, but IMO other tag lines like "Got bugs?" are funnier, thus better. Andreas From spam at tachegroup.com Sat Jul 23 22:29:00 2005 From: spam at tachegroup.com (TGS) Date: Sat, 23 Jul 2005 18:29:00 -0400 (EDT) Subject: Bugzilla t-shirt In-Reply-To: <42E2C39F.6020505@ags.uni-sb.de> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E2C39F.6020505@ags.uni-sb.de> Message-ID: <1066.192.168.2.218.1122157740.squirrel@mailzone.astronomis.com> Me three. I think the tag line is boring. Also where does it come from? I tried to google for it, and there was no hit for that tag. I think also, before something is placed on the order site, you get a feel for if people are going to buy into it. Is there a site with a mockup of the shirt? > Max Kanat-Alexander wrote: >> On Fri, 2005-07-22 at 17:43 -0700, Marcia Knous wrote: >> >>>I am suggesting that we go with "Bugzilla: We take bugs seriously." >> >> Honestly, I wouldn't be too interested in that tag line. (As in, I >> probably wouldn't buy the shirt myself.) > > Me too. Maybe I'm missing something, but IMO other tag lines like "Got > bugs?" are funnier, thus better. > > Andreas > - > To view or change your list settings, click here: > > From mpriest at 3eti.com Sat Jul 23 22:32:34 2005 From: mpriest at 3eti.com (Priest, Mark) Date: Sat, 23 Jul 2005 18:32:34 -0400 Subject: Bugzilla t-shirt Message-ID: Hi, I am not a bugzilla developer but I would buy a shirt with the "Got bugs?" tag line. I am the bugzilla admin and I think I would get some laughs. -Mark -----Original Message----- From: Andreas Franke [mailto:afranke at ags.uni-sb.de] Sent: Saturday, July 23, 2005 6:25 PM To: developers at bugzilla.org Subject: Re: Bugzilla t-shirt Max Kanat-Alexander wrote: > On Fri, 2005-07-22 at 17:43 -0700, Marcia Knous wrote: > >>I am suggesting that we go with "Bugzilla: We take bugs seriously." > > Honestly, I wouldn't be too interested in that tag line. (As in, I > probably wouldn't buy the shirt myself.) Me too. Maybe I'm missing something, but IMO other tag lines like "Got bugs?" are funnier, thus better. Andreas - To view or change your list settings, click here: From micklweiss at gmx.net Sun Jul 24 04:17:29 2005 From: micklweiss at gmx.net (Mick Weiss) Date: Sun, 24 Jul 2005 00:17:29 -0400 Subject: Screen shots for Bugzilla In-Reply-To: <42E10EB4.3532.00D2.0@novell.com> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> <42DEAE6D.7010008@mozilla.org> <42E10EB4.3532.00D2.0@novell.com> Message-ID: <42E31659.4090904@gmx.net> Wow what timing... I'd like to get that patch :-) Reason: I'm using a modified version of MegaCap (a project on sf.net to create screenshots), to get people to send in screenshots for bugs. That saves them in bmp... I was just about to re-write the code in MegaCap, but that is an even nicer solution since 1/2 of the people use MS Paint. If you could, either post to the list (i'm not sure if it would get stripped from the emails) - otherwise just send it to my email: micklweiss at gmx.net Thanks! - Mick Gregary Hendricks wrote: > On Wednesday 20 July 2005 14:05, Gervase Markham wrote: > > >>Thomas, Steve wrote: >> >> >>>Our users like to use the Windows Print Screen functionality to >>> >>> >quickly > > >>>paste a screenshot of a bug into email. >>> >>>Now that we're moving them to Bugzilla I'd like to try to get >>> >>> >them > > >>>something similar. I can probably hack something together myself, >>> >>> >but > > >>>does anybody know if anybody else has done this? >>> >>> >>Apart from Joel Spolsky for FogBugz? ;-) >> >>Probably the smoothest way would be for you to write a tray icon app >>which read the clipboard, created an image file, and attached it to >> >> >a > > >>given bug number. So you press Alt-PrtScrn, click on the tray icon, >> >> >and > > >>enter the bug number in the box which pops up. >> >>Gerv >>- >> >> >There are a number of apps for windows that do this already. I can't >recall >off the top of my head a name but I know I have used some in the past. > >One thing to watch out for that has caused us some consternation is >that many >of the windows apps (MS Paint especially) saves the screen shot as an >uncompressed bmp file which can eat up disk space in a hurry. We have >added a >little hack to bugzilla to automatically convert bmp to png files when >they >are attached. If there is any interest i can send a patch. > > > >>To view or change your list settings, click here: >> >> >> > > > From jpyeron at pdinc.us Sun Jul 24 04:36:50 2005 From: jpyeron at pdinc.us (Jason Pyeron) Date: Sun, 24 Jul 2005 00:36:50 -0400 (EDT) Subject: Screen shots for Bugzilla In-Reply-To: <42E31659.4090904@gmx.net> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> <42DEAE6D.7010008@mozilla.org> <42E10EB4.3532.00D2.0@novell.com> <42E31659.4090904@gmx.net> Message-ID: how about open a bug, and attach it there. On Sun, 24 Jul 2005, Mick Weiss wrote: > Wow what timing... I'd like to get that patch :-) > > Reason: I'm using a modified version of MegaCap (a project on sf.net to > create screenshots), to get people to send in screenshots for bugs. That > saves them in bmp... I was just about to re-write the code in MegaCap, but > that is an even nicer solution since 1/2 of the people use MS Paint. > > If you could, either post to the list (i'm not sure if it would get stripped > from the emails) - otherwise just send it to my email: micklweiss at gmx.net > > Thanks! > > - Mick > > > Gregary Hendricks wrote: > >> On Wednesday 20 July 2005 14:05, Gervase Markham wrote: >> >>> Thomas, Steve wrote: >>> >>>> Our users like to use the Windows Print Screen functionality to >>>> >> quickly >> >>>> paste a screenshot of a bug into email. >>>> >>>> Now that we're moving them to Bugzilla I'd like to try to get >>>> >> them >> >>>> something similar. I can probably hack something together myself, >>>> >> but >> >>>> does anybody know if anybody else has done this? >>>> >>> Apart from Joel Spolsky for FogBugz? ;-) >>> >>> Probably the smoothest way would be for you to write a tray icon app >>> which read the clipboard, created an image file, and attached it to >>> >> a >> >>> given bug number. So you press Alt-PrtScrn, click on the tray icon, >>> >> and >> >>> enter the bug number in the box which pops up. >>> >>> Gerv >>> - >>> >> There are a number of apps for windows that do this already. I can't >> recall off the top of my head a name but I know I have used some in the >> past. >> >> One thing to watch out for that has caused us some consternation is >> that many of the windows apps (MS Paint especially) saves the screen shot >> as an uncompressed bmp file which can eat up disk space in a hurry. We have >> added a little hack to bugzilla to automatically convert bmp to png files >> when >> they are attached. If there is any interest i can send a patch. >> >> >>> To view or change your list settings, click here: >>> >>> >> >> > > - > To view or change your list settings, click here: > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Partner & Sr. Manager 7 West 24th Street #100 - - +1 (443) 921-0381 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. From micklweiss at gmx.net Sun Jul 24 05:11:31 2005 From: micklweiss at gmx.net (Mick Weiss) Date: Sun, 24 Jul 2005 01:11:31 -0400 Subject: Windows / Postgres Testing Box for Landfill Message-ID: <42E32303.8030401@gmx.net> Hi Everyone, I'm not sure if you guys would be interested but- I spoke with a friend of mine who has some contacts @ the local college here. They may be able to have the spare hardware / bandwidth for a bugzilla test box running Windows and Postgresql. Would this be of interest to the QA team / developers? If this wouldn't work out with this college, I personally have contacts at 3 different universities / colleges that might be able to help out. Let me know if this would be of interest and: - what things I need to consider - who should I talk to about creating a link on the site - what are the minimum hardware specs required.... etc. I can think of a few names who could help me with those questions... but they are all on this list anyhow ;-) btw: the reason that I mention universities is because they usually have really good bandwidth and they often help out with similar things (like www mirrors) etc. Open source advocates are also easy to find there :-D - Mick From kiffin at gish.demon.nl Sun Jul 24 16:42:23 2005 From: kiffin at gish.demon.nl (Kiffin Gish) Date: Sun, 24 Jul 2005 18:42:23 +0200 Subject: Bugzilla UI hackathon #1: July 29; attachments In-Reply-To: <42E20482.9040300@mozilla.org> Message-ID: <000001c5906e$ab12b760$2201a8c0@ZGISH> Here's something that be an interesting fix to the 'comments too long' problem: ---kiffin (begin)--- Bugzilla UI hackathon #1

Here's an example of how one might use javascript to keep folks from entering too much text in the certain places.

Additional Comments:
---kiffin (begin)--- Just thought you might be interested. -- Kiffin Rex Gish Gouda, The Netherlands -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Myk Melez Sent: Saturday, July 23, 2005 09:49 To: developers at bugzilla.org; Asa Dotzler Subject: Bugzilla UI hackathon #1: July 29; attachments Now that the tree is open for 2.22 development, it's time to start the UI hackathons. The first one will be next Friday, July 29, from 10am-6pm PDT (UTC-07:00). It'll focus on attachment UI, from the "edit attachment" page to the "create an attachment" page, the "show bug" attachments table, and attachment references in comments. Basically, anywhere there is (or should be) UI for accessing or manipulating attachments is fair game for hacking. I'll be on MailScanner has detected a possible fraud attempt from "ircs:" claiming to be MailScanner has detected a possible fraud attempt from "ircs:" claiming to be irc.mozilla.org in the #hackathon channel for the entire hackathon to discuss problems, approve solutions, and review patches. We'll start by looking over existing bugs, brainstorming new ideas, prioritizing fixes that can happen within a day, and dividing up the work between available hackers. Where possible, we'll make decisions by consensus. Otherwise, we'll air our respective views, and then I'll make a decision or defer the issue to further discussion. I welcome the participation of all Bugzilla hackers and users who want to contribute to improving this important piece of Bugzilla functionality! -myk -------------- next part -------------- An HTML attachment was scrubbed... URL: From myk at mozilla.org Sun Jul 24 18:23:46 2005 From: myk at mozilla.org (Myk Melez) Date: Sun, 24 Jul 2005 11:23:46 -0700 Subject: Bugzilla UI hackathon #1: July 29; attachments In-Reply-To: <000001c5906e$ab12b760$2201a8c0@ZGISH> References: <000001c5906e$ab12b760$2201a8c0@ZGISH> Message-ID: <42E3DCB2.2060306@mozilla.org> Kiffin Gish wrote: > > Here's something that be an interesting fix to the 'comments too long' > problem > I'm not inclined to forbid people from entering comments above a certain size. There may be legitimate uses for long comments, so I'd rather direct users to submit long comments as attachments while still letting them submit them as comments if they deem that appropriate. One option is to warn users if their comment exceeds a certain size. Another is to provide a "make this comment an attachment" checkbox and check it automatically if the comment exceeds a certain size. Let's discuss this further at the hackathon. -myk -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkanat at bugzilla.org Sun Jul 24 19:08:50 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sun, 24 Jul 2005 12:08:50 -0700 Subject: Windows / Postgres Testing Box for Landfill In-Reply-To: <42E32303.8030401@gmx.net> References: <42E32303.8030401@gmx.net> Message-ID: <1122232131.3848.9.camel@localhost.localdomain> On Sun, 2005-07-24 at 01:11 -0400, Mick Weiss wrote: > I'm not sure if you guys would be interested but- I spoke with a friend > of mine who has some contacts @ the local college here. They may be able > to have the spare hardware / bandwidth for a bugzilla test box running > Windows and Postgresql. > > Would this be of interest to the QA team / developers? Absolutely. :-) We were wanting to have just such a thing for a while. :-) It would be nice if it could also run MySQL, too. > - what things I need to consider Basically, we'd need to set up a Tinderbox client on your Windows box. Right now our Tinderbox clients sometimes depend on Unix system functions, so either we or you may have to re-write them. However, if you want we can give you the perl code for the clients, and let you know how it works, and you can try to get it up and running. The database-testing code is extremely system-dependent at the moment, so it would take longer to get that to run on Windows, but it wouldn't be totally impossible. You can just come into #mozwebtools on irc.mozilla.org and talk to us about it. If we're not around, just wait around until we are. :-) I think the people on IRC who know the most about the Tinderbox clients for Bugzilla would be justdave, myself, zach, and wicked. And as far as Bugzilla/Win32 glob or jth would probably be good people to help out with that. > - who should I talk to about creating a link on the site For landfill.bugzilla.org, you can ask me. (I'm mkanat in IRC, when I'm around.) If I'm not around, you can ask justdave, too, but he's usually pretty busy. > - what are the minimum hardware specs required.... etc. No min hardware specs. :-) We've run tinderboxes on Pentium machines before, I think. :-) The faster the machine is, the more different test suites it can handle simultaneously, though, and the quicker it completes them. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From ghendricks at novell.com Mon Jul 25 22:38:58 2005 From: ghendricks at novell.com (Gregary Hendricks) Date: Mon, 25 Jul 2005 16:38:58 -0600 Subject: Screen shots for Bugzilla In-Reply-To: <42E5140D.3532.00D2.0@novell.com> References: <42E5140D.3532.00D2.0@novell.com> Message-ID: <42E515A2.3532.00D2.0@novell.com> https://bugzilla.mozilla.org/show_bug.cgi?id=302083 Enjoy :-) >>> From: jpyeron at pdinc.us To: Date: 07/23/05 10:39 pm Subject: Re: Screen shots for Bugzilla how about open a bug, and attach it there. On Sun, 24 Jul 2005, Mick Weiss wrote: > Wow what timing... I'd like to get that patch :- ) > > Reason: I'm using a modified version of MegaCap (a project on sf.net to > create screenshots), to get people to send in screenshots for bugs. That > saves them in bmp... I was just about to re- write the code in MegaCap, but > that is an even nicer solution since 1/2 of the people use MS Paint. > > If you could, either post to the list (i'm not sure if it would get stripped > from the emails) - otherwise just send it to my email: micklweiss at gmx.net > > Thanks! > > - Mick > > Greg Hendricks Novell IS&T Engineer GHendricks at novell.com Office: (801) 861-3481 www.novell.com From ghendricks at novell.com Mon Jul 25 22:57:24 2005 From: ghendricks at novell.com (Gregary Hendricks) Date: Mon, 25 Jul 2005 16:57:24 -0600 Subject: Bugzilla t-shirt Message-ID: <42E519F4.3532.00D2.0@novell.com> Have you considered going with a service such as cafepress.com? http://www.cafepress.com/cp/info/sell/ They let you create any combination of shirts and other apparel (as well as other nifty things like mouse pads) and take care of all of the orders as well (made to order so it doesn't matter if there is an order for 2 shirts or 200). Also you can have all the tag lines you want as well as a variety of colors. >Me three. > >I think the tag line is boring. Also where does it come from? I tried to >google for it, and there was no hit for that tag. > >I think also, before something is placed on the order site, you get a feel >for if people are going to buy into it. Is there a site with a mockup of >the shirt? > Max Kanat- Alexander wrote: >> On Fri, 2005- 07- 22 at 17:43 - 0700, Marcia Knous wrote: >> >>>I am suggesting that we go with "Bugzilla: We take bugs seriously." >> >> Honestly, I wouldn't be too interested in that tag line. (As in, I >> probably wouldn't buy the shirt myself.) > > Me too. Maybe I'm missing something, but IMO other tag lines like "Got > bugs?" are funnier, thus better. > > Andreas > - > To view or change your list settings, click here: > > - To view or change your list settings, click here: Greg Hendricks Novell IS&T Engineer GHendricks at novell.com Office: (801) 861-3481 www.novell.com From luis.villa at gmail.com Mon Jul 25 23:04:04 2005 From: luis.villa at gmail.com (Luis Villa) Date: Mon, 25 Jul 2005 19:04:04 -0400 Subject: Bugzilla t-shirt In-Reply-To: <42E519F4.3532.00D2.0@novell.com> References: <42E519F4.3532.00D2.0@novell.com> Message-ID: <2cb10c4405072516041ebe1269@mail.gmail.com> On 7/25/05, Gregary Hendricks wrote: > Have you considered going with a service such as cafepress.com? > > http://www.cafepress.com/cp/info/sell/ > > They let you create any combination of shirts and other apparel (as > well as other nifty things like mouse pads) and take care of all of the > orders as well (made to order so it doesn't matter if there is an order > for 2 shirts or 200). Also you can have all the tag lines you want as > well as a variety of colors. Last I checked, cafepress had fairly draconian 'we own your soul' policies about artwork and such that you uploaded. Fine if you're uploading a personal scribble, but might be problematic for b.m.o > >Me three. > > > >I think the tag line is boring. Also where does it come from? I tried > to > >google for it, and there was no hit for that tag. Quadrupled. Replacing a slogan that has meaning and relevance for a small number of people with something that is dull and meaningless for everyone seems like a net loss to me. Luis From marcia at mozilla.org Mon Jul 25 23:16:30 2005 From: marcia at mozilla.org (Marcia Knous) Date: Mon, 25 Jul 2005 16:16:30 -0700 Subject: Bugzilla t-shirt In-Reply-To: <1122148601.3345.1.camel@localhost.localdomain> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> Message-ID: <42E572CE.8030207@mozilla.org> Max: First, the min order for a polo is much more than 21 shirts. Since the Mozilla store would have to take on this initial order and it would be sold on the store site, there would have to be a lot more interest in a polo before we would take that step. As far as the tag line, not sure if we could use "Got Bugs?" because of the whole "Got Milk?" campaign. The other option is to just do the shirt without any tag line and simply use the text "Bugzilla." Someone mentioned something about Cafe Press, but remember that mozilla has been given rights to use the buggie image from the creator. marcia Max Kanat-Alexander wrote: > On Fri, 2005-07-22 at 17:43 -0700, Marcia Knous wrote: > >> I am suggesting that we go with "Bugzilla: We take bugs seriously." >> > > Honestly, I wouldn't be too interested in that tag line. (As in, I > probably wouldn't buy the shirt myself.) > > Also, at least on the list, we had considerably more interest in a polo > than in a T-shirt -- I know that I myself probably wouldn't buy the > T-Shirt, but I'd more likely buy the polo. We had at least 21 > commitments to buy a polo if one was offered, I believe, in the other > thread, although I'm not sure that's enough to seed an order. > > -Max > -------------- next part -------------- An HTML attachment was scrubbed... URL: From altlst at sonic.net Mon Jul 25 23:15:32 2005 From: altlst at sonic.net (Albert Ting) Date: Mon, 25 Jul 2005 16:15:32 -0700 Subject: Bugzilla t-shirt In-Reply-To: <2cb10c4405072516041ebe1269@mail.gmail.com> References: <42E519F4.3532.00D2.0@novell.com> <2cb10c4405072516041ebe1269@mail.gmail.com> Message-ID: <17125.29332.879757.463665@gargle.gargle.HOWL> > > >Me three. > > > > > >I think the tag line is boring. Also where does it come from? I tried > > >to google for it, and there was no hit for that tag. > > Quadrupled. Replacing a slogan that has meaning and relevance for a > small number of people with something that is dull and meaningless for > everyone seems like a net loss to me. Well, for a polo shirt, I vote for the Bugzilla icon with a small "Got Bugs" slogan. Seems pretty elegant to me. For a t-shirt, I'd vote for the same thing. But perhaps on the back, have a large "Got Bugs?" text using a spray can font, similar to those Raid commercial. Heck, maybe have a bunch "evil bugs" lurking behind the "Got bugs?" sign. Albert From vseerror at lehigh.edu Mon Jul 25 23:28:02 2005 From: vseerror at lehigh.edu (Wayne Mery) Date: Mon, 25 Jul 2005 19:28:02 -0400 Subject: Bugzilla t-shirt In-Reply-To: <42E572CE.8030207@mozilla.org> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> Message-ID: <42E57582.40304@lehigh.edu> bug me (...hug me) little long but ... bug me till it hurts ? From ghendricks at novell.com Mon Jul 25 23:29:20 2005 From: ghendricks at novell.com (Gregary Hendricks) Date: Mon, 25 Jul 2005 17:29:20 -0600 Subject: Bugzilla t-shirt Message-ID: <42E52170.3532.00D2.0@novell.com> > > They let you create any combination of shirts and other apparel (as > > well as other nifty things like mouse pads) and take care of all of the > > orders as well (made to order so it doesn't matter if there is an order > > for 2 shirts or 200). Also you can have all the tag lines you want as > > well as a variety of colors. > > Last I checked, cafepress had fairly draconian 'we own your soul' > policies about artwork and such that you uploaded. Fine if you're > uploading a personal scribble, but might be problematic for b.m.o > Actually, according to the policies explained on their site, they own nothing of your work (See http://www.cafepress.com/cp/info/sell/images/images_security and http://www.cafepress.com/cp/info/sell/images/help_law ) They make their money on the base price of the item you are selling. You make money on the markup. The only reason I point it out is this way we don't have to worry about ardering 100 shirts and then only having 5 sell leaving someone holding the bag as far as expenses go. Of course it would't hurt to do both ways I suppose. Have an "Official shirt" that you give out for bug fixes and submissions etc and then have the cafepress store for the other variations on the tagline, color, etc that you want with no obligation to have a minimum order. Greg Hendricks Novell IS&T Engineer GHendricks at novell.com Office: (801) 861-3481 www.novell.com From myk at mozilla.org Tue Jul 26 02:08:27 2005 From: myk at mozilla.org (Myk Melez) Date: Mon, 25 Jul 2005 19:08:27 -0700 Subject: Bugzilla t-shirt In-Reply-To: <42E572CE.8030207@mozilla.org> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> Message-ID: <42E59B1B.6030908@mozilla.org> Marcia Knous wrote: > Max: First, the min order for a polo is much more than 21 shirts. > Since the Mozilla store would have to take on this initial order and > it would be sold on the store site, there would have to be a lot more > interest in a polo before we would take that step. Speaking only for myself, I'm looking forward to the t-shirts, since I don't wear polos. > As far as the tag line, not sure if we could use "Got Bugs?" because > of the whole "Got Milk?" campaign. Got *, where * is something an organization is advertising, is commonly used these days, and there's no indication that the Got Milk campaign has had any problem with it. We shouldn't worry about such things without reason. > The other option is to just do the shirt without any tag line and > simply use the text "Bugzilla." To me it makes sense to use the tagline preferred by the community of Bugzilla users and developers. After all, Bugzilla t-shirt users are advertising a connection to that community, and the t-shirt should reflect the community spirit. Personally, I like "Zarro Boogs", but the community (via a bunch of posts to the Bugzilla developers mailing list) seems to be leaning pretty heavily in favor of "Got Bugs", so let's go with that (provided Dave agrees--Dave?). -myk -------------- next part -------------- An HTML attachment was scrubbed... URL: From timeless at myrealbox.com Tue Jul 26 09:02:48 2005 From: timeless at myrealbox.com (timeless) Date: Tue, 26 Jul 2005 02:02:48 -0700 Subject: Screen shots for Bugzilla In-Reply-To: <42E10EB4.3532.00D2.0@novell.com> References: <8E1982313133E740ABCCF578C7060FEC0589B66A@DEN-EXM-02.corp.ebay.com> <42DEAE6D.7010008@mozilla.org> <42E10EB4.3532.00D2.0@novell.com> Message-ID: <42E5FC38.2080809@myrealbox.com> Gregary Hendricks wrote: > One thing to watch out for that has caused us some consternation is > that many > of the windows apps (MS Paint especially) saves the screen shot as an > uncompressed bmp file which can eat up disk space in a hurry. We have > added a > little hack to bugzilla to automatically convert bmp to png files when > they > are attached. If there is any interest i can send a patch. note: this is merely a default. mspaint has always supported multiple output formats, and in fact is generally pluggable, so if you have wXP or msoffice. From LpSolit at gmail.com Tue Jul 26 10:25:37 2005 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Tue, 26 Jul 2005 12:25:37 +0200 Subject: Bugzilla t-shirt In-Reply-To: <42E59B1B.6030908@mozilla.org> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> <42E59B1B.6030908@mozilla.org> Message-ID: <42E60FA1.8060109@gmail.com> > Personally, I like "Zarro Boogs", but the community (via a bunch of > posts to the Bugzilla developers mailing list) seems to be leaning > pretty heavily in favor of "Got Bugs", so let's go with that (provided "Zarro Boogs" is funny (and is in the same spirit of our two "emergency" releases 2.16.10 and 2.18.3); "Got Bugs" is too serious... and I'm almost never serious! ;-) But I prefer "Got Bugs" than "Bugzilla: We take bugs seriously." About having a big red (or any other color) "Bugzilla" or any other text in the back, as someone suggested this week-end, is not what I prefer. Fr?d?ric From David_Obler at ssaihq.com Tue Jul 26 12:09:53 2005 From: David_Obler at ssaihq.com (Dave Obler) Date: Tue, 26 Jul 2005 08:09:53 -0400 Subject: Bugzilla t-shirt In-Reply-To: <42E60FA1.8060109@gmail.com> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> <42E59B1B.6030908@mozilla.org> <42E60FA1.8060109@gmail.com> Message-ID: <42E62811.9030803@ssaihq.com> Folks I vote for Zarro Boogs found, even though I grep'd the code and changed it to 'HAL 9000 reports zero bugs' My .02 Dave Fr?d?ric Buclin wrote: > >> Personally, I like "Zarro Boogs", but the community (via a bunch of >> posts to the Bugzilla developers mailing list) seems to be leaning >> pretty heavily in favor of "Got Bugs", so let's go with that (provided > > > "Zarro Boogs" is funny (and is in the same spirit of our two > "emergency" releases 2.16.10 and 2.18.3); "Got Bugs" is too serious... > and I'm almost never serious! ;-) But I prefer "Got Bugs" than > "Bugzilla: We take bugs seriously." > > About having a big red (or any other color) "Bugzilla" or any other > text in the back, as someone suggested this week-end, is not what I > prefer. > > > Fr?d?ric > - > To view or change your list settings, click here: > >> From dberlin at dberlin.org Tue Jul 26 14:07:43 2005 From: dberlin at dberlin.org (Daniel Berlin) Date: Tue, 26 Jul 2005 10:07:43 -0400 Subject: Bugzilla t-shirt In-Reply-To: <42E62811.9030803@ssaihq.com> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> <42E59B1B.6030908@mozilla.org> <42E60FA1.8060109@gmail.com> <42E62811.9030803@ssaihq.com> Message-ID: <1122386864.6052.28.camel@dyn9002219136> Sadly, some user on gcc bugzilla reported it as a spelling error, obviously not getting it. On Tue, 2005-07-26 at 08:09 -0400, Dave Obler wrote: > Folks > > I vote for Zarro Boogs found, even though I grep'd the code and changed > it to 'HAL 9000 reports zero bugs' > > My .02 > > Dave From chicks at chicks.net Tue Jul 26 16:12:21 2005 From: chicks at chicks.net (Christopher Hicks) Date: Tue, 26 Jul 2005 12:12:21 -0400 (EDT) Subject: Bugzilla t-shirt In-Reply-To: <42E59B1B.6030908@mozilla.org> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> <42E59B1B.6030908@mozilla.org> Message-ID: On Mon, 25 Jul 2005, Myk Melez wrote: > Marcia Knous wrote: >> As far as the tag line, not sure if we could use "Got Bugs?" because of the >> whole "Got Milk?" campaign. > Got *, where * is something an organization is advertising, is commonly used > these days, and there's no indication that the Got Milk campaign has had any > problem with it. We shouldn't worry about such things without reason. Parody is considered fair use so there shouldn't be any legal issues. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) From spam at tachegroup.com Tue Jul 26 18:37:07 2005 From: spam at tachegroup.com (TGS) Date: Tue, 26 Jul 2005 14:37:07 -0400 (EDT) Subject: Bugzilla t-shirt In-Reply-To: References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> <42E59B1B.6030908@mozilla.org> Message-ID: <62518.199.46.198.233.1122403027.squirrel@mailzone.astronomis.com> In addition, not defending the "Got whatever", in every existing case that uses it, leaves the party with no standing against any other party the uses it. > On Mon, 25 Jul 2005, Myk Melez wrote: >> Marcia Knous wrote: >>> As far as the tag line, not sure if we could use "Got Bugs?" because of >>> the >>> whole "Got Milk?" campaign. >> Got *, where * is something an organization is advertising, is commonly >> used >> these days, and there's no indication that the Got Milk campaign has had >> any >> problem with it. We shouldn't worry about such things without reason. > > Parody is considered fair use so there shouldn't be any legal issues. > > -- > > > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author) > - > To view or change your list settings, click here: > > From timeless at myrealbox.com Tue Jul 26 18:55:22 2005 From: timeless at myrealbox.com (timeless) Date: Tue, 26 Jul 2005 11:55:22 -0700 Subject: CC-feld as a dropdown list ... In-Reply-To: <000b01c58f5e$f5f418c0$2201a8c0@ZGISH> References: <000b01c58f5e$f5f418c0$2201a8c0@ZGISH> Message-ID: <42E6871A.5030608@myrealbox.com> Kiffin Gish wrote: > In Bugzilla the CC-field is a free form email-address text field, meaning > that if there is some guess work involved or the user misspells the email > address, he/she gets a cryptic error message back. > > Would it be feasible to create a dropdown via a db-select so that the user > has a list of names to choose from istead? > > If so, then how would I go about doing this? > > Thanks a lot in advance. it's possible, but you'll soon find it's a very bad idea, even with only 40 users. it's a lot easier to use a 3 character substring and get a decent match than paging through 5-10 people with the same first letter of their name. we have this silly "feature" in our bugzilla and i'm very close to commandeering the bugzilla to remove it. it drives me crazy. From dberlin at dberlin.org Tue Jul 26 19:01:35 2005 From: dberlin at dberlin.org (Daniel Berlin) Date: Tue, 26 Jul 2005 15:01:35 -0400 Subject: Bugzilla t-shirt In-Reply-To: <62518.199.46.198.233.1122403027.squirrel@mailzone.astronomis.com> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> <42E59B1B.6030908@mozilla.org> <62518.199.46.198.233.1122403027.squirrel@mailzone.astronomis.com> Message-ID: <1122404495.7683.13.camel@linux.site> On Tue, 2005-07-26 at 14:37 -0400, TGS wrote: > In addition, not defending the "Got whatever", in every existing case that > uses it, leaves the party with no standing against any other party the > uses it. As an IP lawyer (in addition to my regular hackerly skills), i can tell you this doesn't actually mean crap (either fair use, or standing). They'll sue you anyway, and it'll cost you thousands just to get it thrown out. From micklweiss at gmx.net Tue Jul 26 20:02:45 2005 From: micklweiss at gmx.net (Mick Weiss) Date: Tue, 26 Jul 2005 16:02:45 -0400 Subject: Bugzilla t-shirt In-Reply-To: References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> <42E59B1B.6030908@mozilla.org> Message-ID: <42E696E5.7080400@gmx.net> Christopher Hicks wrote: > On Mon, 25 Jul 2005, Myk Melez wrote: > >> Marcia Knous wrote: >> >>> As far as the tag line, not sure if we could use "Got Bugs?" because >>> of the whole "Got Milk?" campaign. >> >> Got *, where * is something an organization is advertising, is >> commonly used these days, and there's no indication that the Got Milk >> campaign has had any problem with it. We shouldn't worry about such >> things without reason. > > > Parody is considered fair use so there shouldn't be any legal issues. > Fair use still exists? Thats news to me here in America ;-) - Mick From luis.villa at gmail.com Tue Jul 26 20:10:31 2005 From: luis.villa at gmail.com (Luis Villa) Date: Tue, 26 Jul 2005 16:10:31 -0400 Subject: Bugzilla t-shirt In-Reply-To: <42E696E5.7080400@gmx.net> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> <42E59B1B.6030908@mozilla.org> <42E696E5.7080400@gmx.net> Message-ID: <2cb10c44050726131079d620@mail.gmail.com> On 7/26/05, Mick Weiss wrote: > Christopher Hicks wrote: > > > On Mon, 25 Jul 2005, Myk Melez wrote: > > > >> Marcia Knous wrote: > >> > >>> As far as the tag line, not sure if we could use "Got Bugs?" because > >>> of the whole "Got Milk?" campaign. > >> > >> Got *, where * is something an organization is advertising, is > >> commonly used these days, and there's no indication that the Got Milk > >> campaign has had any problem with it. We shouldn't worry about such > >> things without reason. > > > > > > Parody is considered fair use so there shouldn't be any legal issues. > > > Fair use still exists? Thats news to me here in America ;-) Sure it does. To paraphrase Lessig, fair use is mostly the right to hire a lawyer. Luis From spam at tachegroup.com Sat Jul 23 05:45:52 2005 From: spam at tachegroup.com (TGS) Date: Sat, 23 Jul 2005 01:45:52 -0400 (EDT) Subject: Bugzilla T-Shirt In-Reply-To: <49940.192.168.1.254.1122069837.squirrel@tomate.linagora.lan> References: <42E1125D.3532.00D2.0@novell.com> <49940.192.168.1.254.1122069837.squirrel@tomate.linagora.lan> Message-ID: <1228.192.168.2.218.1122097552.squirrel@mailzone.astronomis.com> I will get another 2 at least, and that is without asking anyone on my development team! > Gregary Hendricks wrote: >> >> I could second that with another half dozen or so and possibly more >> down the line. > > I'll third it with 4-6 polos. > > Emmanuel > > - > To view or change your list settings, click here: > > From timeless at myrealbox.com Wed Jul 27 05:14:45 2005 From: timeless at myrealbox.com (timeless) Date: Tue, 26 Jul 2005 22:14:45 -0700 Subject: Bugzilla t-shirt In-Reply-To: <42E59B1B.6030908@mozilla.org> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> <42E59B1B.6030908@mozilla.org> Message-ID: <42E71845.4030402@myrealbox.com> Marcia Knous wrote: > Max: First, the min order for a polo is much more than 21 shirts. > Since the Mozilla store would have to take on this initial order and > it would be sold on the store site, there would have to be a lot more > interest in a polo before we would take that step. Myk Melez wrote: > Speaking only for myself, I'm looking forward to the t-shirts, since I > don't wear polos. i have lots of tshirts, but i could go for a polo i think. > Personally, I like "Zarro Boogs", but the community (via a bunch of > posts to the Bugzilla developers mailing list) seems to be leaning > pretty heavily in favor of "Got Bugs", so let's go with that (provided > Dave agrees--Dave?). i'm fine w/ either and would go for a shirt. From mkanat at bugzilla.org Wed Jul 27 07:40:36 2005 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 27 Jul 2005 00:40:36 -0700 Subject: 2.20rc2 Release Delay Message-ID: <1122450036.9743.0.camel@localhost.localdomain> I'm going to be too busy today to release Bugzilla 2.20rc2. Thus the release will be delayed about two days, most likely. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. From kevin.benton at amd.com Wed Jul 27 14:30:18 2005 From: kevin.benton at amd.com (Benton, Kevin) Date: Wed, 27 Jul 2005 07:30:18 -0700 Subject: 2.20rc2 Release Delay Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4201AC3708@ssvlexmb2.amd.com> Release on Friday? That doesn't seem like a great idea as many aren't around to assist on the weekends... --- Kevin Benton Perl/Bugzilla Developer Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. -----Original Message----- From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Max Kanat-Alexander Sent: Wednesday, July 27, 2005 1:41 AM To: developers at bugzilla.org Subject: 2.20rc2 Release Delay I'm going to be too busy today to release Bugzilla 2.20rc2. Thus the release will be delayed about two days, most likely. -Max -- http://www.everythingsolved.com/ Everything Solved: Experts at Bugzilla... and everything else, too. - To view or change your list settings, click here: From Dennis.Melentyev at infopulse.com.ua Wed Jul 27 15:51:56 2005 From: Dennis.Melentyev at infopulse.com.ua (Dennis Melentyev) Date: Wed, 27 Jul 2005 18:51:56 +0300 Subject: Bugzilla t-shirt Message-ID: <0F18828098CF31459845A42C74B834E97DEF9F@exchange.home> But what's about "Let's put some bugs in prison?" (correct grammatics and spelling if/as needed :) ) > -----Original Message----- > From: developers-owner at bugzilla.org > [mailto:developers-owner at bugzilla.org] On Behalf Of Luis Villa > Sent: Tuesday, July 26, 2005 11:11 PM > To: developers at bugzilla.org > Subject: Re: Bugzilla t-shirt > > On 7/26/05, Mick Weiss wrote: > > Christopher Hicks wrote: > > > > > On Mon, 25 Jul 2005, Myk Melez wrote: > > > > > >> Marcia Knous wrote: > > >> > > >>> As far as the tag line, not sure if we could use "Got Bugs?" > > >>> because of the whole "Got Milk?" campaign. > > >> > > >> Got *, where * is something an organization is advertising, is > > >> commonly used these days, and there's no indication that the Got > > >> Milk campaign has had any problem with it. We shouldn't worry > > >> about such things without reason. > > > > > > > > > Parody is considered fair use so there shouldn't be any > legal issues. > > > > > Fair use still exists? Thats news to me here in America ;-) > > Sure it does. > > To paraphrase Lessig, fair use is mostly the right to hire a lawyer. > > Luis > > - > To view or change your list settings, click here: > nfopulse.com.ua> > From jake at bugzilla.org Wed Jul 27 17:12:31 2005 From: jake at bugzilla.org (Jake) Date: Wed, 27 Jul 2005 13:12:31 -0400 Subject: Bugzilla t-shirt In-Reply-To: <42E572CE.8030207@mozilla.org> References: <42E192B0.7070905@mozilla.org> <1122148601.3345.1.camel@localhost.localdomain> <42E572CE.8030207@mozilla.org> Message-ID: <42E7C07F.6000304@bugzilla.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcia Knous wrote: > Max: First, the min order for a polo is much more than 21 shirts. Since > the Mozilla store would have to take on this initial order and it would > be sold on the store site, there would have to be a lot more interest in > a polo before we would take that step. I'll add my vote to the polo shirt. I'd probably buy a T-Shirt, too, but am a fan of the polos :). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC58BrPFshtZHeR6kRAtjqAKCCAUGDnGLTSMFl6aO+5jhMm67kQACdHKuP 1Vh/XdUceUnVKZb+N9YpK4E= =yrfx -----END PGP SIGNATURE----- From justdave at bugzilla.org Wed Jul 27 20:22:20 2005 From: justdave at bugzilla.org (David Miller) Date: Wed, 27 Jul 2005 16:22:20 -0400 Subject: 2.20rc2 Release Delay In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A4201AC3708@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4201AC3708@ssvlexmb2.amd.com> Message-ID: <42E7ECFC.5060209@bugzilla.org> Benton, Kevin wrote: > Release on Friday? That doesn't seem like a great idea as many aren't > around to assist on the weekends... On the other hand, there are others (like me) who are better able to assist on weekends :) -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Foundation http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From jpyeron at pdinc.us Wed Jul 27 20:47:19 2005 From: jpyeron at pdinc.us (Jason Pyeron) Date: Wed, 27 Jul 2005 16:47:19 -0400 (EDT) Subject: 2.20rc2 Release Delay In-Reply-To: <42E7ECFC.5060209@bugzilla.org> References: <6F7DA19D05F3CF40B890C7CA2DB13A4201AC3708@ssvlexmb2.amd.com> <42E7ECFC.5060209@bugzilla.org> Message-ID: how about late Saturday night? it gives Sunday as a slack day to fix silly but obvoius issues. and monday for overflow.X On Wed, 27 Jul 2005, David Miller wrote: > Benton, Kevin wrote: >> Release on Friday? That doesn't seem like a great idea as many aren't >> around to assist on the weekends... > > On the other hand, there are others (like me) who are better able to assist > on weekends :) > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Partner & Sr. Manager 7 West 24th Street #100 - - +1 (443) 921-0381 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited. From dcalvert at AllianceBankNA.com Thu Jul 28 19:24:48 2005 From: dcalvert at AllianceBankNA.com (Calvert, Douglas) Date: Thu, 28 Jul 2005 15:24:48 -0400 Subject: Scalability Information Message-ID: Hello, I am presenting a proposal to use bugzilla internally tomorrow. I know some wise guy is going to ask how many users/bugs/queries/searches can it handle on a moderate machine. I also know that we are not ever going to test this limit but I want to have some statistics anyway. Does anyone have any good anecdotes about bugzilla's performance on moderate hardware? And or the stats on a couple huge installations like mozilla/kernel.org/redhat? Thanks a lot... From bugreport at peshkin.net Thu Jul 28 20:23:23 2005 From: bugreport at peshkin.net (Joel Peshkin) Date: Thu, 28 Jul 2005 13:23:23 -0700 Subject: Scalability Information In-Reply-To: References: Message-ID: <42E93EBB.1080408@peshkin.net> Calvert, Douglas wrote: >Hello, > I am presenting a proposal to use bugzilla internally tomorrow. I know >some wise guy is going to ask how many users/bugs/queries/searches can >it handle on a moderate machine. I also know that we are not ever going >to test this limit but I want to have some statistics anyway. Does >anyone have any good anecdotes about bugzilla's performance on moderate >hardware? And or the stats on a couple huge installations like >mozilla/kernel.org/redhat? Thanks a lot... > > >- >To view or change your list settings, click here: > > > If you expect to have more than a few hundred users and more than about 10K bugs, I strongly suggest using a shadow database (via mysql replication). You can run everything on a moderate machine with no problem. If you want to geek it a bit, just add extra memory and dual CPU. Definitely dont skimp on the disk drives. I have 500 users and 20K bugs and 16GB attachments on a Sun Ultra/60. It can get a bit slow sometimes, but not bad. When I upgrade, I'll use a shadow database on the same hardware. From LpSolit at gmail.com Fri Jul 29 00:44:28 2005 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Fri, 29 Jul 2005 02:44:28 +0200 Subject: QA testing: 36 hours left till Bugzilla 2.20rc2 Message-ID: <42E97BEC.906@gmail.com> The 2.20 branch is now frozen for checkins till we release 2.20rc2. We expect to release it on Saturday, i.e. in ~ 36 hours starting from now. For those who want to help, even testing only a feature or two, feel free to join us in #qa-bugzilla. The QA team is tracking progress on landfill in the meta-bug: http://landfill.bugzilla.org/qa220rc2/show_bug.cgi?id=2643 This bug is restricted to the 'QA' group, so unless you ask us to add you in this group, you won't be able to see (and change) the bug. The goal is to avoid another release next week, and to catch regressions if there are some. Actually, we are only 4 to do some QA stuff and we certainly cannot test all possible combinations. But we expect to catch any major regression or bug. If you have upgraded to the latest 2.20 (pre-2.20rc2) and if you observe something wrong with this version, please open a bug on b.m.o or join us in #qa-bugzilla. If you haven't such an installation, feel free to do tests on http://landfill.bugzilla.org/qa220rc2/ (which is based on MySQL) and which will be the final 2.20rc2. Any help is welcome! :) Frederic (LpSolit) From myk at mozilla.org Fri Jul 29 01:37:23 2005 From: myk at mozilla.org (Myk Melez) Date: Thu, 28 Jul 2005 18:37:23 -0700 Subject: first UI hackathon tomorrow! Message-ID: <42E98853.2000001@mozilla.org> Just a reminder that first UI hackathon is tomorrow, Friday, July 29 from 10am-6pm PDT. We're focusing on the attachments interface and will be meeting for discussions in the #hackathon channel on irc.mozilla.org. -myk From myk at mozilla.org Sat Jul 30 02:53:56 2005 From: myk at mozilla.org (Myk Melez) Date: Fri, 29 Jul 2005 19:53:56 -0700 Subject: post-hackathon update and feedback request Message-ID: <42EAEBC4.6080406@mozilla.org> We had a great UI hackathon today, focusing on attachments usability and usefulness with half a dozen to a dozen developers and users. During the course of the day, we checked in ghendricks' BMP->PNG autoconverter and my tabs refactoring (a prerequisite to using tabs to improve the navigability of the attachment pages), hashed out how we can improve content type handling and implement large comment -> attachment conversion, and worked on a number of other issues. A rough list with some notes and links is available on the hackathon wiki scratchpad . I'd love to get feedback about the event to help me improve future ones. For those who attended: Was it helpful? What worked well? What could have worked better? For those who didn't, but might: Why not? I'm also trying to decide when the next (and subsequent) hackathons should be held, and what we should focus on. I can't please everybody, but knowing your schedules, availability, and interest will help figure out what makes the most sense. For those interested in participating: What day(s) of the week work best? How often can you attend? What would you like to work on? Should we stay focused on one area across several hackathons or jump to different areas each time? Thanks again to everyone who participated! I look forward to your feedback and the next hackathon! -myk -------------- next part -------------- An HTML attachment was scrubbed... URL: From micklweiss at gmx.net Sat Jul 30 06:06:53 2005 From: micklweiss at gmx.net (Mick Weiss) Date: Sat, 30 Jul 2005 02:06:53 -0400 Subject: post-hackathon update and feedback request In-Reply-To: <42EAEBC4.6080406@mozilla.org> References: <42EAEBC4.6080406@mozilla.org> Message-ID: <42EB18FD.5010708@gmx.net> Myk Melez wrote: > > We had a great UI hackathon today, focusing on attachments usability > and usefulness with half a dozen to a dozen developers and users. I rather enjoyed it myself. > .... > > A rough list with some notes and links is available on the hackathon > wiki scratchpad . > > I'd love to get feedback about the event to help me improve future > ones. For those who attended: > Was it helpful? Yes. Those brainstorming sessions are always great. > What worked well? The fact that we all collaborated in real time. Mailinglists are good, but there is a delay. The fact that we had a separate channel was also good. The fact that it was focused was also good IMO. > ... > I'm also trying to decide when the next (and subsequent) hackathons > should be held, and what we should focus on. I think that hackathons could be focused on various topics. If it is right before a release... then a hackathon on the blockers/critical bugs would be best. Otherwise, I think that we should move from topic to topic gradually. Once something is "pretty much covered" we can move to the next topic. Jumping around may not work for the people with mild A.D.D. ;-) > I can't please everybody, but knowing your schedules, availability, > and interest will help figure out what makes the most sense. I'm pretty flexable with this. > For those interested in participating: What day(s) of the week work > best? Friday nights EDT. I'm not working on work related stuff as much and I'm coding anyway. This is also good if we have a hackathon on patches. This gives us the weekend to completely test code and have it perfect by Monday. > How often can you attend? hopefully 100% of the time and at least lurk around. > What would you like to work on? The UI. I think that there should be skins. In a /skins directory (not sure how this effects templates/ and css/). > Should we stay focused on one area across several hackathons or jump > to different areas each time? Focus is a plus. > > Thanks again to everyone who participated! I look forward to your > feedback and the next hackathon! Ditto. - Mick > > -myk > > From micklweiss at gmx.net Sat Jul 30 06:28:30 2005 From: micklweiss at gmx.net (Mick Weiss) Date: Sat, 30 Jul 2005 02:28:30 -0400 Subject: REMIND and LATER considered harmful [was Re: RESOLVED] In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A42018CE0B1@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A42018CE0B1@ssvlexmb2.amd.com> Message-ID: <42EB1E0E.2010200@gmx.net> Isn't that what comments are for? status: Pending comment: I need more info from... just my 2 cents, - Mick Benton, Kevin wrote: >>From a process monitoring perspective, "NEEDINFO" by itself isn't enough >from my point of view. There are other reasons a bug may be in a >PENDING state besides a need for additional information. > >--- >Kevin Benton >Perl/Bugzilla Developer >Advanced Micro Devices > >The opinions stated in this communication do not necessarily reflect the >view of Advanced Micro Devices and have not been reviewed by management. >This communication may contain sensitive and/or confidential and/or >proprietary information. Distribution of such information is strictly >prohibited without prior consent of Advanced Micro Devices. This >communication is for the intended recipient(s) only. If you have >received this communication in error, please notify the sender, then >destroy any remaining copies of this communication. > > > >-----Original Message----- >From: developers-owner at bugzilla.org >[mailto:developers-owner at bugzilla.org] On Behalf Of timeless >Sent: Thursday, July 14, 2005 12:12 PM >To: developers at bugzilla.org >Subject: Re: REMIND and LATER considered harmful [was Re: RESOLVED] > >Gregary Hendricks wrote: > > >>For this we, as well as a number of bugzillae, have implemented a >>NEEDINFO status. Along with it we have an added field of who we >> >> > > need information from (reporter, last commentor, or someone else > > entirely) who is then CC'd on the bug for the duration that the bug > > is in the NEEDINFO state. This places the responsibility of the bug > > squarely on the shoulders of the info provider until they come back > > with the additional information. This really helps in the processing > > of a bug as it is obvious by the status that no work can be > > completed until someone (usually the reporter) comes back with > > something more than was initially provided. > >i much prefer this (both ideally and having seen it) over all the other >forms suggested in this thread. > >- >To view or change your list settings, click here: > > > > >- >To view or change your list settings, click here: > > > > > From exie at linkageposted.longmusic.com Sun Jul 31 19:27:07 2005 From: exie at linkageposted.longmusic.com (Eddie Xie) Date: Sun, 31 Jul 2005 12:27:07 -0700 Subject: Recommendations for Bugzilla hardware Message-ID: <20050731192707.GA7562@sunni.localdomain> I maintain a customized version of Bugzilla for my organization. We are upgrading some of our equipment, and one of the things being considered for upgrade is our Bugzilla server. What sort of specs would be good for our new server? Bugzilla is used a lot in our organization. We have around 100 users and over 40,000 bugs in our database. More bugs get added all the time. We also seem to like generating graphs and reports. We don't want to invest too much in a Bugzilla server if we could put that money and hardware elsewhere. On the other hand, we don't want our users complaining that Bugzilla is slow, because it is used all the time. I welcome any recommendations for this. Thanks! -- Eddie Xie