From kristis.makris at asu.edu Wed Nov 1 20:35:06 2006 From: kristis.makris at asu.edu (Kristis Makris) Date: Wed, 01 Nov 2006 13:35:06 -0700 Subject: Trunk In Soft Freeze In-Reply-To: <1162334979.2609.6.camel@max> References: <1162334979.2609.6.camel@max> Message-ID: <1162413306.2492.7.camel@syd.mkgnu.net> Hi Max, If I could ask, how do you "freeze" the CVS tree in Bugzilla ? Is there something you do to the CVS repository ? Do you somehow limit commit privileges to a few people ? I'm only asking to see if it would be beneficial to provide in Scmbug an integration policy that: - accepts commits only by a limited list of SCM users, - accepts commits only if against bugs that have been flagged by special keywords, e.g. "ACCEPT_WHILE_FROZEN_FOR_3.0rc1" - accepts commits if against a bug that currently has a patch awaiting review. Perhaps supply a deadline date for this. I would be *very* interested in your ideas. I don't have a clear understanding of what types of checks you might be interested in. Kristis On Tue, 2006-10-31 at 14:49 -0800, Max Kanat-Alexander wrote: > Hey hey. So the trunk is now "soft" frozen. > > This means that any enhancement that *currently* has a patch on it, > where that patch is awaiting review, can still be checked in, until > November 14. > > However, no new patches will be accepted for enhancements, unless those > enhancements are marked as blockers. > > On November 14, we freeze "hard," which means that we won't accept any > enhancements at all until after Bugzilla 3.0rc1. > > -Max From mkanat at bugzilla.org Wed Nov 1 20:43:11 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 01 Nov 2006 12:43:11 -0800 Subject: Trunk In Soft Freeze In-Reply-To: <1162413306.2492.7.camel@syd.mkgnu.net> References: <1162334979.2609.6.camel@max> <1162413306.2492.7.camel@syd.mkgnu.net> Message-ID: <1162413792.2589.6.camel@max> On Wed, 2006-11-01 at 13:35 -0700, Kristis Makris wrote: > If I could ask, how do you "freeze" the CVS tree in Bugzilla ? Is there > something you do to the CVS repository ? Do you somehow limit commit > privileges to a few people ? During a normal freeze, we don't do anything in particular. During a QA freeze, we limit the checkins to me, LpSolit, myk, and justdave, usually. That's when *nothing* should go in, because we're going through QA. We use Despot to do it, somehow. Justdave would know the specifics better than I. > I would be *very* interested in your ideas. I don't have a clear > understanding of what types of checks you might be interested in. Well, only for bugs that have certain flags set, such as blocking2.20+ -- that could be useful. -Max > On Tue, 2006-10-31 at 14:49 -0800, Max Kanat-Alexander wrote: > > Hey hey. So the trunk is now "soft" frozen. > > > > This means that any enhancement that *currently* has a patch on it, > > where that patch is awaiting review, can still be checked in, until > > November 14. > > > > However, no new patches will be accepted for enhancements, unless those > > enhancements are marked as blockers. > > > > On November 14, we freeze "hard," which means that we won't accept any > > enhancements at all until after Bugzilla 3.0rc1. > > > > -Max > > - > To view or change your list settings, click here: > -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From justdave at bugzilla.org Wed Nov 1 21:05:06 2006 From: justdave at bugzilla.org (David Miller) Date: Wed, 01 Nov 2006 16:05:06 -0500 Subject: Trunk In Soft Freeze In-Reply-To: <1162413306.2492.7.camel@syd.mkgnu.net> References: <1162334979.2609.6.camel@max> <1162413306.2492.7.camel@syd.mkgnu.net> Message-ID: <45490C02.5030603@bugzilla.org> Kristis Makris wrote on 11/1/06 3:35 PM: > If I could ask, how do you "freeze" the CVS tree in Bugzilla ? Is there > something you do to the CVS repository ? Do you somehow limit commit > privileges to a few people ? For the "soft freeze" it's mostly a social thing, where people are ridiculed in public if they commit when they're not supposed to. ;) For the hard freezes, we do lock down the branches using despot ( https://despot.mozilla.org/ - see also http://www.mozilla.org/owners.html for the access lists) -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From cheiny at synaptics.com Wed Nov 1 21:39:07 2006 From: cheiny at synaptics.com (Christopher Heiny) Date: Wed, 01 Nov 2006 13:39:07 -0800 Subject: OT: Despot? In-Reply-To: <45490C02.5030603@bugzilla.org> References: <1162334979.2609.6.camel@max> <1162413306.2492.7.camel@syd.mkgnu.net> <45490C02.5030603@bugzilla.org> Message-ID: <454913FB.9030109@synaptics.com> David Miller wrote: > For the hard freezes, we do lock down the branches using despot ( > https://despot.mozilla.org/ - see also > http://www.mozilla.org/owners.html for the access lists) Hmmmm. Despot sounds like something we could use around here. Is there a site with information about despot? Or is it not a publicly available thing? From gerv at mozilla.org Wed Nov 1 22:36:36 2006 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 01 Nov 2006 22:36:36 +0000 Subject: OT: Despot? In-Reply-To: <454913FB.9030109@synaptics.com> References: <1162334979.2609.6.camel@max> <1162413306.2492.7.camel@syd.mkgnu.net> <45490C02.5030603@bugzilla.org> <454913FB.9030109@synaptics.com> Message-ID: <45492174.8010307@mozilla.org> Christopher Heiny wrote: > Hmmmm. Despot sounds like something we could use around here. Is there > a site with information about despot? Or is it not a publicly available > thing? I believe the source code is in mozilla.org CVS (mozilla/webtools/despot) but it's not officially maintained and not well documented :-| Gerv From zach at zachlipton.com Wed Nov 1 22:58:04 2006 From: zach at zachlipton.com (Zach Lipton) Date: Wed, 1 Nov 2006 17:58:04 -0500 Subject: OT: Despot? In-Reply-To: <45492174.8010307@mozilla.org> References: <1162334979.2609.6.camel@max> <1162413306.2492.7.camel@syd.mkgnu.net> <45490C02.5030603@bugzilla.org> <454913FB.9030109@synaptics.com> <45492174.8010307@mozilla.org> Message-ID: On Nov 1, 2006, at 5:36 PM, Gervase Markham wrote: > Christopher Heiny wrote: >> Hmmmm. Despot sounds like something we could use around here. Is >> there a site with information about despot? Or is it not a >> publicly available thing? > > I believe the source code is in mozilla.org CVS (mozilla/webtools/ > despot) but it's not officially maintained and not well documented :-| > It's pretty Mozilla-specific, and I don't think there's anyone else using it. In reality, it's a pretty archaic system, works only with CVS, and you'd likely have to customize it to the point of a rewrite in order to make it useful for your purposes. If you just want to be able to lock down CVS access, setting unix group permissions on the server or tinkering with lock files (to block checkins entirely) is a lot simpler unless you have a large project. --zach From cheiny at synaptics.com Wed Nov 1 23:33:00 2006 From: cheiny at synaptics.com (Christopher Heiny) Date: Wed, 01 Nov 2006 15:33:00 -0800 Subject: OT: Despot? In-Reply-To: References: <1162334979.2609.6.camel@max> <1162413306.2492.7.camel@syd.mkgnu.net> <45490C02.5030603@bugzilla.org> <454913FB.9030109@synaptics.com> <45492174.8010307@mozilla.org> Message-ID: <45492EAC.9020201@synaptics.com> Zach Lipton wrote: > On Nov 1, 2006, at 5:36 PM, Gervase Markham wrote: > >> Christopher Heiny wrote: >> >>> Hmmmm. Despot sounds like something we could use around here. Is >>> there a site with information about despot? Or is it not a publicly >>> available thing? >> >> >> I believe the source code is in mozilla.org CVS (mozilla/webtools/ >> despot) but it's not officially maintained and not well documented :-| >> > It's pretty Mozilla-specific, and I don't think there's anyone else > using it. In reality, it's a pretty archaic system, works only with > CVS, and you'd likely have to customize it to the point of a rewrite in > order to make it useful for your purposes. If you just want to be able > to lock down CVS access, setting unix group permissions on the server > or tinkering with lock files (to block checkins entirely) is a lot > simpler unless you have a large project. Thanks for the fast followups. I was hoping it might provide a tidy way to lock specific branches in CVS - which it might, but it sounds like it's not something that can be just picked up. Thanks again, Chris From kristis.makris at asu.edu Thu Nov 2 01:16:29 2006 From: kristis.makris at asu.edu (Kristis Makris) Date: Wed, 01 Nov 2006 18:16:29 -0700 Subject: OT: Despot? In-Reply-To: <45492EAC.9020201@synaptics.com> References: <1162334979.2609.6.camel@max> <1162413306.2492.7.camel@syd.mkgnu.net> <45490C02.5030603@bugzilla.org> <454913FB.9030109@synaptics.com> <45492174.8010307@mozilla.org> <45492EAC.9020201@synaptics.com> Message-ID: <1162430189.2515.15.camel@syd.mkgnu.net> On Wed, 2006-11-01 at 15:33 -0800, Christopher Heiny wrote: > Zach Lipton wrote: > >> Christopher Heiny wrote: > >> > >>> Hmmmm. Despot sounds like something we could use around here. Is > >>> there a site with information about despot? Or is it not a publicly > >>> available thing? > > > I was hoping it might provide a tidy way to lock specific branches in > CVS - which it might, but it sounds like it's not something that can be > just picked up. Locking specific branches. That's an idea. Scmbug could be just picked up! It can detect the branch name in which a changeset is pushed. It should be trivial to implement a policy that locks specific branches. From bugreport at peshkin.net Thu Nov 2 02:36:32 2006 From: bugreport at peshkin.net (Joel Peshkin) Date: Wed, 01 Nov 2006 18:36:32 -0800 Subject: OT: Despot? In-Reply-To: <45492EAC.9020201@synaptics.com> References: <1162334979.2609.6.camel@max> <1162413306.2492.7.camel@syd.mkgnu.net> <45490C02.5030603@bugzilla.org> <454913FB.9030109@synaptics.com> <45492174.8010307@mozilla.org> <45492EAC.9020201@synaptics.com> Message-ID: <454959B0.8090208@peshkin.net> Christopher Heiny wrote: > Thanks for the fast followups. > > I was hoping it might provide a tidy way to lock specific branches in > CVS - which it might, but it sounds like it's not something that can > be just picked up. > > Thanks again, > Chris Try cvscop.sf.net From david.oshea at dspace.com.au Thu Nov 2 01:26:16 2006 From: david.oshea at dspace.com.au (David O'Shea) Date: Thu, 2 Nov 2006 11:56:16 +1030 Subject: [scmbug-users] Re: OT: Despot? Message-ID: Hi Kristis, Previously where I worked our SCM system had a per-branch state which was one of: 1. any commits allowed 2. commits allowed only if they specified a bug ID 3. commits allowed only if they specified a bug ID from a particular list (stored in a text file) 4. no commits allowed (which I guess is a special case of 3 with an empty list) I guess #3 is similar to where you only allow commits where the specified bug ID has a specified keyword set on it. However, based on my limited experience with Bugzilla (I know I'm being restrictive by only talking about Bugzilla here when scmbug supports other systems too, but I use Bugzilla), I think that user permissions either permit or deny a user from editing any and all keywords and I can't say that a particular user has access only to add keywords with a certain name. On the other hand, with a per-branch text file you can set permissions on each file to allow different users to edit that file in case you have different people managing different branches. Where I worked there was a web tool for requesting and granting approval for commits to particular branches which resulted in bug IDs being added to such text files. Associating a reason with the restriction is useful too - for #3 you might want any error produced by scmbug to include the text "upcoming release n.nn" and for #4 you might want to say "branch has been merged into trunk and is permanently closed". As I mentioned to you before, I would like to select between #1 and #2 on a per-directory or file basis too. Perhaps the mechanism can be made to allow these things to be set up on a per-branch, per-directory or per-group of files basis? Regards, David ---------------------------------------------- David O'Shea Engineer DSpace Pty Ltd david.oshea at dspace.com.au www.dspace.com.au T: +61 8 8260 8118 -----Original Message----- From: scmbug-users-bounces at lists.mkgnu.net [mailto:scmbug-users-bounces at lists.mkgnu.net]On Behalf Of Kristis Makris Sent: Thursday, 2 November 2006 11:46 To: developers at bugzilla.org Cc: scmbug-users at lists.mkgnu.net Subject: [scmbug-users] Re: OT: Despot? On Wed, 2006-11-01 at 15:33 -0800, Christopher Heiny wrote: > Zach Lipton wrote: > >> Christopher Heiny wrote: > >> > >>> Hmmmm. Despot sounds like something we could use around here. Is > >>> there a site with information about despot? Or is it not a publicly > >>> available thing? > > > I was hoping it might provide a tidy way to lock specific branches in > CVS - which it might, but it sounds like it's not something that can be > just picked up. Locking specific branches. That's an idea. Scmbug could be just picked up! It can detect the branch name in which a changeset is pushed. It should be trivial to implement a policy that locks specific branches. _______________________________________________ scmbug-users mailing list scmbug-users at lists.mkgnu.net http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users From lpsolit at gmail.com Thu Nov 9 14:00:41 2006 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Thu, 09 Nov 2006 15:00:41 +0100 Subject: Minutes of our last Bugzilla meetings Message-ID: <45533489.80002@gmail.com> Hello! I finally wrote the minutes for our last 2 Bugzilla meetings (October 17 and 31). I know, it's late. :) http://wiki.mozilla.org/Bugzilla:Meetings:2006-10-17 http://wiki.mozilla.org/Bugzilla:Meetings:2006-10-31 Also, do not forget that we have another meeting next Tuesday, November 14, at 19:00 GMT (11:00 PST, 20:00 CET). Our next meeting also means we will freeze the code to prepare Bugzilla 3.0 RC1. No new enhancement of any kind will be accepted for 3.0 past this date, unless explicitly marked as a blocker (for some very good reason only). We plan to release 2.22.2 and 2.23.4 later this month, first to fix a problem in editgroups.cgi for users running Template Toolkit 2.15 on Windows (they do changes which are not compatible with previous versions of TT... oh joy!), and secondly to get as much feedback as possible before we release 3.0 RC1. 2.23.4 will indeed be feature complete, and only bug fixes will be accepted after this release. More information on Tuesday, in the #bugzilla-meeting channel. ;) LpSolit From lpsolit at gmail.com Wed Nov 15 14:24:14 2006 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Wed, 15 Nov 2006 15:24:14 +0100 Subject: Minutes of the Bugzilla meeting Message-ID: <455B230E.1030402@gmail.com> Hi all. Here are the minutes of our last Bugzilla meeting we had yesterday: http://wiki.mozilla.org/Bugzilla:Meetings:2006-11-14 Have a look! There are many informations about 2.22.2 and the upcoming 3.0. ;) LpSolit From mkanat at bugzilla.org Sat Nov 18 16:00:43 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 18 Nov 2006 08:00:43 -0800 Subject: MySQL UTF-8 Conversion in Bugzilla Message-ID: <1163865644.3142.1.camel@max> Just to let you know, I've just checked in a patch that converts the MySQL database to UTF-8. However, if you have any non-UTF-8 data in your DB, manual intervention is required during checksetup or your data will be DELETED. checksetup.pl will warn you and give you 60 seconds to stop it, before it goes ahead and converts your database. You can press Ctrl-C when you see the message, and follow the instructions checksetup.pl gives you, to finish the upgrade. (And then re-run checksetup.pl, of course.) I just thought I'd warn anybody who's living on the tip. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Sat Nov 18 16:05:19 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 18 Nov 2006 08:05:19 -0800 Subject: MySQL 4.1 Required on Trunk Message-ID: <1163865919.3142.6.camel@max> Well, we now require MySQL 4.1 on the trunk. 4.1.8, to be exact. Obviously this isn't *too* useful to us right now, since we're frozen. :-) Here's the feature list that we now have access to: http://dev.mysql.com/doc/refman/4.1/en/nutshell-4-1-features.html The most important thing this gets us is subqueries (sub-selects). Go ahead and use sub-selects in any Bugzilla code that you want, but only if they make things clearer, faster, or simpler. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Sun Nov 19 00:13:33 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 18 Nov 2006 16:13:33 -0800 Subject: checksetup-pg Tinderbox Message-ID: <1163895213.3142.8.camel@max> There is now a Tinderbox that runs all of the checksetup upgrade tests against PostgreSQL, as well as MySQL. The PostgreSQL tinderbox is called checksetup-pg. This should help us keep PostgreSQL upgrades just as stable as MySQL upgrades. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From lpsolit at gmail.com Sun Nov 19 18:23:24 2006 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Sun, 19 Nov 2006 19:23:24 +0100 Subject: MySQL 4.1 Required on Trunk In-Reply-To: <1163865919.3142.6.camel@max> References: <1163865919.3142.6.camel@max> Message-ID: <4560A11C.3030707@gmail.com> > Well, we now require MySQL 4.1 on the trunk. 4.1.8, to be exact. You mean 4.1.2, right? LpSolit From justdave at bugzilla.org Mon Nov 20 01:51:55 2006 From: justdave at bugzilla.org (David Miller) Date: Sun, 19 Nov 2006 20:51:55 -0500 Subject: MySQL UTF-8 Conversion in Bugzilla In-Reply-To: <1163865644.3142.1.camel@max> References: <1163865644.3142.1.camel@max> Message-ID: <45610A3B.7080905@bugzilla.org> Max Kanat-Alexander wrote on 11/18/06 11:00 AM: > Just to let you know, I've just checked in a patch that converts the > MySQL database to UTF-8. However, if you have any non-UTF-8 data in your > DB, manual intervention is required during checksetup or your data will > be DELETED. Just as a point of contention... if it's going to cause dataloss, we should require input from the operator before continuing if it's going to delete things, instead of just giving them 60 seconds to abort. If we're running in non-interactive mode, just print an error and bail (unless the override is included in the passed answers file). > checksetup.pl will warn you and give you 60 seconds to stop it, before > it goes ahead and converts your database. You can press Ctrl-C when you > see the message, and follow the instructions checksetup.pl gives you, to > finish the upgrade. (And then re-run checksetup.pl, of course.) -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From mkanat at bugzilla.org Mon Nov 20 03:34:20 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sun, 19 Nov 2006 19:34:20 -0800 Subject: MySQL UTF-8 Conversion in Bugzilla In-Reply-To: <45610A3B.7080905@bugzilla.org> References: <1163865644.3142.1.camel@max> <45610A3B.7080905@bugzilla.org> Message-ID: <1163993660.1326.7.camel@max> On Sun, 2006-11-19 at 20:51 -0500, David Miller wrote: > Just as a point of contention... if it's going to cause dataloss, we > should require input from the operator before continuing if it's going > to delete things, instead of just giving them 60 seconds to abort. If > we're running in non-interactive mode, just print an error and bail > (unless the override is included in the passed answers file). I think that sounds pretty reasonable, actually. Could you (or somebody) file a bug so that I can change the behavior? -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Mon Nov 20 03:33:13 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sun, 19 Nov 2006 19:33:13 -0800 Subject: MySQL 4.1 Required on Trunk In-Reply-To: <4560A11C.3030707@gmail.com> References: <1163865919.3142.6.camel@max> <4560A11C.3030707@gmail.com> Message-ID: <1163993593.1326.4.camel@max> On Sun, 2006-11-19 at 19:23 +0100, Fr?d?ric Buclin wrote: > > Well, we now require MySQL 4.1 on the trunk. 4.1.8, to be exact. > > You mean 4.1.2, right? Ahh, yeah. :-) Whatever checksetup.pl says we require, that's what we require. 4.1.2 it is. :-) -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From justdave at bugzilla.org Mon Nov 20 06:18:25 2006 From: justdave at bugzilla.org (David Miller) Date: Mon, 20 Nov 2006 01:18:25 -0500 Subject: MySQL UTF-8 Conversion in Bugzilla In-Reply-To: <1163993660.1326.7.camel@max> References: <1163865644.3142.1.camel@max> <45610A3B.7080905@bugzilla.org> <1163993660.1326.7.camel@max> Message-ID: <456148B1.1040202@bugzilla.org> Max Kanat-Alexander wrote on 11/19/06 10:34 PM: > On Sun, 2006-11-19 at 20:51 -0500, David Miller wrote: >> Just as a point of contention... if it's going to cause dataloss, we >> should require input from the operator before continuing if it's going >> to delete things, instead of just giving them 60 seconds to abort. If >> we're running in non-interactive mode, just print an error and bail >> (unless the override is included in the passed answers file). > > I think that sounds pretty reasonable, actually. > > Could you (or somebody) file a bug so that I can change the behavior? Filed. https://bugzilla.mozilla.org/show_bug.cgi?id=361252 -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From lpsolit at gmail.com Sun Nov 19 18:20:37 2006 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Sun, 19 Nov 2006 19:20:37 +0100 Subject: MySQL UTF-8 Conversion in Bugzilla In-Reply-To: <1163865644.3142.1.camel@max> References: <1163865644.3142.1.camel@max> Message-ID: <4560A075.9050208@gmail.com> > checksetup.pl will warn you and give you 60 seconds to stop it, before > it goes ahead and converts your database. As dataloss is something really critical, wouldn't it be safer to request the admin to type some character (such as [Y]es) to confirm the DB conversion, and cancel it if the admin didn't do it within 60 seconds? Of course, checksetup.pl should be able to get this answer from the answer file too. I would feel much more confident doing it this way. LpSolit From justdave at bugzilla.org Thu Nov 23 05:59:09 2006 From: justdave at bugzilla.org (David Miller) Date: Thu, 23 Nov 2006 00:59:09 -0500 Subject: Keen to involved Message-ID: <456538AD.8080702@bugzilla.org> I've been too long cleaning the spam out of the moderator queue... the moderator token for this message expired on me, so I'm manually forwarding it back to the list. :) -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ -------------- next part -------------- An embedded message was scrubbed... From: "vincent ryan" Subject: Keen to involved Date: Mon, 13 Nov 2006 12:03:54 +0000 Size: 2412 URL: From lpsolit at gmail.com Thu Nov 23 16:09:02 2006 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Thu, 23 Nov 2006 17:09:02 +0100 Subject: Keen to involved In-Reply-To: <456538AD.8080702@bugzilla.org> References: <456538AD.8080702@bugzilla.org> Message-ID: <4565C79E.70704@gmail.com> > I was wondering if it is possible to get invovled in the Bugzilla > project as a QA? Vince, Of course it is possible! I would be very happy to have more QA testers in our QA team. :) If you have time to join us on IRC, please join the #qa-bugzilla channel on irc.mozilla.org. This way I will be able to give you more information and more easily than per email. If you cannot, well, I will write a longer email. See you on IRC, Fr?d?ric Buclin (a.k.a LpSolit on IRC) From ykarandikar at 2wire.com Mon Nov 27 22:22:53 2006 From: ykarandikar at 2wire.com (Yogesh Karandikar) Date: Mon, 27 Nov 2006 14:22:53 -0800 Subject: Feature addition to time tracking summary Message-ID: <46690B497E6EBB478E2B8401DCBFFE79F95123@sjcexch01.corp.2wire.com> Hi, We use bugzilla 2.22 in our organization. The time tracking feature in this version of bugzilla gives a report in terms of amount of time worked on selected bug(s). We think it would be better to have an option to see a report in terms of amount of time left for resolution of the bug(s). It would be nice if we take into account the time remaining on a bug, load factor of the developer to whom it's assigned to and weekly schedule of the developer to give an estimate in wall clock time. I am thinking of adding one more table that would store the load factor (a simple multiplier) and weekly schedule of developer. Providing access to that table via user prefs cgi to allow developer to enter the load factor and their weekly schedule. Providing an option to summarize_time.cgi to get summary in terms of amount of time left. Calculate the time left on a bug by making use of bugs.remaining_time, multiply it by load factor of developer working on it. Then give an estimated date of completion based on weekly schedule (devise an algorithm for it). It will have the same flow as current time tracking summary report. I would like to know if someone is already working on it. If not, can I add it in as a patch? suggestions are welcome... Thanks, Yogesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From fergus at yahoo-inc.com Tue Nov 28 02:01:28 2006 From: fergus at yahoo-inc.com (Fergus Sullivan) Date: Mon, 27 Nov 2006 18:01:28 -0800 Subject: MySQL UTF-8 Conversion in Bugzilla In-Reply-To: <4560A075.9050208@gmail.com> References: <1163865644.3142.1.camel@max> <4560A075.9050208@gmail.com> Message-ID: Hi guys. Long time listener here, first time caller... Our Bugzilla usage here at Yahoo may help illuminate the need for a broader approach to this problem. We've found that a simple conversion to UTF-8 may not be the answer. A more complex conversion process may be needed to avoid dataloss. As background, our Bugzilla instance is based on version 2.20 and has not had a default charset. We have bugs logged by internal users in many locales, including multi-byte locales. The text of these bugs can often be in an East Asian language. These display fine because mysql doesn't really care what charset its bytes are in. The browser default will ensure a consistent charset is used within each locale. Among the existing bugs, we have bugs that may fall into any of the following categories: == The simple bugs == - bug is entirely in ascii - bug is entirely in utf-8 - bug is in shift-jis, euc-jp, big5, gb2312 or any other 'native character set'. All of these can be converted from charset to charset relatively easily, especially if we can work out what the source charset is. There are libraries for this. == The tricky bugs == - bug is mostly in ascii or utf-8 or any other single charset, but includes characters from another valid charset. Why? A bug could be logged in English but includes pasted characters from Japanese. - bug is mostly in ascii or utf-8 or any other single charset, but includes garbage characters. Why? A bug report might refer to a Chinese product, but include pasted characters that indicate some kind of corruption took place prior to display time. == The Problem == We'd very much like to have our existing database start defaulting to UTF-8. The problem is how can we convert existing reports to UTF-8 and not lose information in existing bugs that shows problems relating to charsets? == Problematic Solution == We considered the following. - have bugzilla default to utf-8 for all NEW bugs. - set a unicode bit on all new bugs. - If at showbug a unicode bit is set: set this in the header's charset. Flaw: - What about contexts where we need to display both a unicode bug and a non-unicode bug in the same page? == Problems with email == We also need to enforce charset when bugs are submitted via the email gateway, and when notifications are sent. Also, let's not forget whinemails. Thoughts? /ferg -- fergus sullivan | yahoo bugzilla admin | fergus at yahoo-inc.com | o. 408.349.6807 | On Sun 19-Nov-06, at 10:20 a, Fr?d?ric Buclin wrote: >> checksetup.pl will warn you and give you 60 seconds to stop it, >> before >> it goes ahead and converts your database. > > > As dataloss is something really critical, wouldn't it be safer to > request the admin to type some character (such as [Y]es) to confirm > the > DB conversion, and cancel it if the admin didn't do it within 60 > seconds? Of course, checksetup.pl should be able to get this answer > from > the answer file too. I would feel much more confident doing it this > way. > > LpSolit > - > To view or change your list settings, click here: > From mkanat at bugzilla.org Tue Nov 28 06:42:00 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Mon, 27 Nov 2006 22:42:00 -0800 Subject: MySQL UTF-8 Conversion in Bugzilla In-Reply-To: References: <1163865644.3142.1.camel@max> <4560A075.9050208@gmail.com> Message-ID: <1164696120.7506.9.camel@max> On Mon, 2006-11-27 at 18:01 -0800, Fergus Sullivan wrote: > Our Bugzilla usage here at Yahoo may help illuminate the need for a > broader approach to this problem. > [snip] Hi Fergus. Have you actually run the checksetup.pl that's in CVS HEAD? The recode.pl that it tells you to run is designed to deal with extremely complicated situations, just like yours. It was made to convert bmo, which has a huge mass of different charsets. > Thoughts? This is absolutely and totally handled by recode.pl in CVS HEAD. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mbd at dbc.dk Tue Nov 28 11:17:19 2006 From: mbd at dbc.dk (Mads Bondo Dydensborg) Date: Tue, 28 Nov 2006 12:17:19 +0100 Subject: Announcement: First release of C# Bugzilla WebService client (version 0.1.0) Message-ID: <200611281217.19422.mbd@dbc.dk> Hi there First of, sorry if this is off-topic - please redirect me to a more appropiate forum for announcements, if it is. I have released the first version of a C# Bugzilla WebService client library, available under LGPL, with a homepage at http://oss.dbc.dk/bugzproxy/ (follow links to sourceforge project site for cvs/files). I understand that the Bugzilla community may wonder about the wisdom of using C# as a client language, but please consider that one of the aims of this library is to facilitate integration into the .NET based tool chains, such as Visual Studio, via .NET based plugins. As such, it may contribute to the general acceptance of Bugzilla, and possibly to further contributions to the WebService interface in the Bugzilla server. More information: Bugzproxy is a client library for the upcoming Bugzilla Bugtracker WebService interface (part of Bugzilla 3.0), written in C#, that provides an OO access to a Bugzilla server. This release is the first release of bugzproxy, and provides support for all of the WebService functionality currently included in the Bugzilla CVS HEAD, which will become part of the first Bugzilla 3.0 release candicate, expected in early december. The aim of Bugzproxy is to allow easy building of various clients, such as command line tools, and Visual Studio plugins, possibly MonoDevelop plugins, that facilitate the integration of a Bugzilla into the various C# tool chains. This first release has been built using Mono/Linux, but should easily build on Windows. (.exe and .dll files provided, as well as source). As the project's aim is to provide an efficient and intuitive OO API, the API probably will change in future revisions, but it is our feeling that the current API is a good start. It is well documented, and a number of example programs are provided. We solicit feedback on the future development of this program, and encourage C# developers using the Bugzilla bugtracker software, to give it a try. Regards, Mads -- Mads Bondo Dydensborg mads at dydensborg.dk http://www.madsdydensborg.dk/ I disapprove of what you say, but I will defend to the death your right to say it. - Beatrice Hall [pseudonym: S.G. Tallentyre], 1907 (many times wrongfully attributed to Voltaire) -- Med venlig hilsen/Regards Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34 ------------------------------------------------------- -- Med venlig hilsen/Regards Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34