From justdave at bugzilla.org Thu Mar 1 12:53:45 2007 From: justdave at bugzilla.org (David Miller) Date: Thu, 01 Mar 2007 07:53:45 -0500 Subject: Downloading plugins (Was: Summer of Code Projects) In-Reply-To: <45E5BAF7.6000102@mozilla.org> References: <20070227083629.157F61828E@help.trusthosting.net> <45E446D0.1030406@gmail.com> <45E5BAF7.6000102@mozilla.org> Message-ID: <45E6CCD9.5050306@bugzilla.org> Gervase Markham wrote on 2/28/07 12:25 PM: > Bill Barry wrote: >> I think it is a big project, but: >> https://bugzilla.mozilla.org/show_bug.cgi?id=371333 > > Do we really want to encourage administrators to download and install > code on their servers without examining it first? Servers and client > machines (running Firefox) are fundamentally different here. > > I might give some non-malicious admin privileges on Bugzilla, but that > doesn't mean I want them entering URLs to automatically download and > install new code. They might do that even if they never considered using > the admin privileges to find a hole in the Bugzilla code, get a shell etc. I think the way wordpress does it works just fine, and would be a fine system to emulate. You still have to have shell (or ftp) access on the server to install a plugin. Once it's installed, you can enable or disable it from the web UI (and it's disabled by default at install time). -- 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 gerv at mozilla.org Thu Mar 1 13:40:30 2007 From: gerv at mozilla.org (Gervase Markham) Date: Thu, 01 Mar 2007 13:40:30 +0000 Subject: Downloading plugins (Was: Summer of Code Projects) In-Reply-To: <45E6CCD9.5050306@bugzilla.org> References: <20070227083629.157F61828E@help.trusthosting.net> <45E446D0.1030406@gmail.com> <45E5BAF7.6000102@mozilla.org> <45E6CCD9.5050306@bugzilla.org> Message-ID: <45E6D7CE.2070305@mozilla.org> David Miller wrote: > I think the way wordpress does it works just fine, and would be a fine > system to emulate. > > You still have to have shell (or ftp) access on the server to install a > plugin. Once it's installed, you can enable or disable it from the web > UI (and it's disabled by default at install time). That sounds fine to me. Gerv From gerv at mozilla.org Thu Mar 1 14:19:34 2007 From: gerv at mozilla.org (Gervase Markham) Date: Thu, 01 Mar 2007 14:19:34 +0000 Subject: Downloading plugins (Was: Summer of Code Projects) In-Reply-To: <45E5CF33.60908@gmail.com> References: <20070227083629.157F61828E@help.trusthosting.net> <45E446D0.1030406@gmail.com> <45E5BAF7.6000102@mozilla.org> <45E5CF33.60908@gmail.com> Message-ID: <45E6E0F6.1070505@mozilla.org> Bill Barry wrote: > I would suggest each plugin passes a whole bunch of "safety" tests (to > be determined some time in the future) and would then need to be signed > by official reviewers (note). This has big problems. a) Analysing code to make sure it's not malicious is really hard, and a lot of work even if you can't do it perfectly. b) This sort of close coupling basically makes the plugins a part of Bugzilla anyway. What's the massive advantage of a text box saying "install the plugin at this URL", as opposed to "$ install-bz-plugin http://www.some.url" which means that we have to do masses of extra work to permit it? Gerv From manmegh at yahoo.com Thu Mar 1 22:59:17 2007 From: manmegh at yahoo.com (megh man) Date: Thu, 1 Mar 2007 14:59:17 -0800 (PST) Subject: upgradation of the bugzilla from 2.16.3 to 2.20 Message-ID: <705590.81234.qm@web63113.mail.re1.yahoo.com> I want to upgrade bugzilla 2.16.3 to 2.20. Please let me know the steps to follow. I want to even config my DB too. --------------------------------- Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkanat at bugzilla.org Thu Mar 1 23:05:29 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 1 Mar 2007 15:05:29 -0800 Subject: upgradation of the bugzilla from 2.16.3 to 2.20 In-Reply-To: <705590.81234.qm@web63113.mail.re1.yahoo.com> References: <705590.81234.qm@web63113.mail.re1.yahoo.com> Message-ID: <20070301230529.A5FD81828E@help.trusthosting.net> On Thu, 1 Mar 2007 14:59:17 -0800 (PST) megh man wrote: > I want to upgrade bugzilla 2.16.3 to 2.20. > Please let me know the steps to follow. > I want to even config my DB too. Hi! Send your support questions to the support mailing list, described here: http://www.bugzilla.org/support/ This isn't the mailing list for support. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From kevin.benton at amd.com Thu Mar 1 23:02:54 2007 From: kevin.benton at amd.com (Benton, Kevin) Date: Thu, 1 Mar 2007 15:02:54 -0800 Subject: upgradation of the bugzilla from 2.16.3 to 2.20 In-Reply-To: <705590.81234.qm@web63113.mail.re1.yahoo.com> References: <705590.81234.qm@web63113.mail.re1.yahoo.com> Message-ID: > I want to upgrade bugzilla 2.16.3 to 2.20. > Please let me know the steps to follow. > I want to even config my DB too. ? This question belongs in the support list rather than the developers list. Having said that, there's a file included with Bugzilla called UPGRADING that includes instructions on how to upgrade your Bugzilla. Kevin Benton Senior Software Developer MSS Silicon Design Engineering 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 chicks at chicks.net Fri Mar 2 09:49:52 2007 From: chicks at chicks.net (Christopher Hicks) Date: Fri, 2 Mar 2007 04:49:52 -0500 Subject: Downloading plugins (Was: Summer of Code Projects) In-Reply-To: <45E6E0F6.1070505@mozilla.org> References: <20070227083629.157F61828E@help.trusthosting.net> <45E446D0.1030406@gmail.com> <45E5BAF7.6000102@mozilla.org> <45E5CF33.60908@gmail.com> <45E6E0F6.1070505@mozilla.org> Message-ID: <20070302094952.GC10833@chicks.net> On Thu, Mar 01, 2007 at 02:19:34PM +0000, Gervase Markham wrote: > Bill Barry wrote: > >I would suggest each plugin passes a whole bunch of "safety" tests (to > >be determined some time in the future) and would then need to be signed > >by official reviewers (note). > > This has big problems. a) Analysing code to make sure it's not malicious > is really hard, and a lot of work even if you can't do it perfectly. b) > This sort of close coupling basically makes the plugins a part of > Bugzilla anyway. Are we planning on having the plugins running inside Safe compartments? It might provide better isolation as well as a choke point for the security folks to fondle. -- The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts. - Bertrand Russell, philosopher, mathematician, author, Nobel laureate (1872-1970) From after.fallout at gmail.com Fri Mar 2 14:32:51 2007 From: after.fallout at gmail.com (Bill Barry) Date: Fri, 02 Mar 2007 09:32:51 -0500 Subject: Downloading plugins (Was: Summer of Code Projects) In-Reply-To: <45E6E0F6.1070505@mozilla.org> References: <20070227083629.157F61828E@help.trusthosting.net> <45E446D0.1030406@gmail.com> <45E5BAF7.6000102@mozilla.org> <45E5CF33.60908@gmail.com> <45E6E0F6.1070505@mozilla.org> Message-ID: <45E83593.3070708@gmail.com> Gervase Markham wrote: > Bill Barry wrote: >> I would suggest each plugin passes a whole bunch of "safety" tests >> (to be determined some time in the future) and would then need to be >> signed by official reviewers (note). > > This has big problems. a) Analysing code to make sure it's not > malicious is really hard, and a lot of work even if you can't do it > perfectly. We can't make certain that the code is not malicious (not perl anyways), but we certainly can make sure it conforms to coding standards associated with bugzilla (taint, warnings, passes included test suite, uses dbi, ...) . We can also make sure each plugin has contribution history to tell who did what (cvs blame and logs) to help deter people from intentionally writing malicious code. > b) This sort of close coupling basically makes the plugins a part of > Bugzilla anyway. > Is that a problem? I think it would help getting contributers to Bugzilla itself. From gerv at mozilla.org Fri Mar 2 14:57:23 2007 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 02 Mar 2007 14:57:23 +0000 Subject: Downloading plugins (Was: Summer of Code Projects) In-Reply-To: <45E83593.3070708@gmail.com> References: <20070227083629.157F61828E@help.trusthosting.net> <45E446D0.1030406@gmail.com> <45E5BAF7.6000102@mozilla.org> <45E5CF33.60908@gmail.com> <45E6E0F6.1070505@mozilla.org> <45E83593.3070708@gmail.com> Message-ID: <45E83B53.8080505@mozilla.org> Bill Barry wrote: > We can't make certain that the code is not malicious (not perl anyways), > but we certainly can make sure it conforms to coding standards > associated with bugzilla (taint, warnings, passes included test suite, > uses dbi, ...) . We can - but what does it buy us? We're just doing free QA for their project. And we can't exactly tell admins "don't install this - it doesn't have a 2-space indent". > We can also make sure each plugin has contribution > history to tell who did what (cvs blame and logs) to help deter people > from intentionally writing malicious code. "Don't install this - it doesn't have a public source repository"? >> b) This sort of close coupling basically makes the plugins a part of >> Bugzilla anyway. >> > Is that a problem? I think it would help getting contributers to > Bugzilla itself. It's a problem because it defeats the entire point of plugins. The point of plugins is that someone else does all the work, and we don't have to worry about it too much. So people can extend Bugzilla in the directions they like without taking core development team resources. Gerv From henry.story at bblfish.net Mon Mar 5 13:51:01 2007 From: henry.story at bblfish.net (Henry Story) Date: Mon, 5 Mar 2007 14:51:01 +0100 Subject: Baetle: Bug and Enhancement Tracking LanguagE Message-ID: <35B7DB3D-012C-4E30-A6E4-706AB23D91DC@bblfish.net> Hi, I am just starting to develop a Bug Ontology. http://blogs.sun.com/bblfish/entry/baetle_bug_and_enhancement_tracking This should enable different bug tracking systems to put up SPARQL endpoints making them easily queryable by all kinds of agents. Perhaps some people here would be interested in joining or listening in. I need to have something practical going quickly, so I am hoping to get there in a very iterative fashion. There is a nice library called D2RQ that makes it very easy to map an SQL database into SPARQL. So technically this should easily be able to be added onto the current bugzilla setup in due time. Henry [1] http://blogs.sun.com/bblfish/entry/sparqling_roller the endpoint is down right now but the pdf slides explain well what is happening Home page: http://bblfish.net/ Sun Blog: http://blogs.sun.com/bblfish/ Foaf name: http://bblfish.net/people/henry/card#me From mkanat at bugzilla.org Wed Mar 7 12:38:13 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 7 Mar 2007 04:38:13 -0800 Subject: Priority System for Enhancements (Implemented) In-Reply-To: <20070227214800.5002518291@help.trusthosting.net> References: <20070227214800.5002518291@help.trusthosting.net> Message-ID: <20070307123816.9AA081817C@help.trusthosting.net> On Tue, 27 Feb 2007 13:47:59 -0800 Max Kanat-Alexander wrote: > P1 = We definitely want this. It's a major feature, and it's > obvious that it would be useful to everybody. > > P2 = We want this, but it's not totally clear or extremely > important. So, I've gone through all the enhancements that were listed as P1 and P2, and triaged them so that P1 and P2 actually now *mean* the above. So you can now see the features that we most want (now or ever) by this URL: http://tinyurl.com/2bfu7n (That's a search for all open enhancements at P1 or P2 in the Bugzilla product.) There are 1500 open enhancements in Bugzilla, so I haven't triaged all of them yet. :-) If you think that there's a bug clearly missing from that list, feel free to email me and point out (in two or three sentences maximum) why you think your bug should be on that list. I'm sure there are some missing. (As I said--1500 enhancements. I haven't looked at more than 200 of them or so.) -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From henry.story at bblfish.net Wed Mar 7 12:43:32 2007 From: henry.story at bblfish.net (Henry Story) Date: Wed, 7 Mar 2007 13:43:32 +0100 Subject: Baetle: Bug and Enhancement Tracking LanguagE In-Reply-To: <35B7DB3D-012C-4E30-A6E4-706AB23D91DC@bblfish.net> References: <35B7DB3D-012C-4E30-A6E4-706AB23D91DC@bblfish.net> Message-ID: I have now started an Open Source Project on Google Code to develop this ontology http://code.google.com/p/baetle/ There is a wiki that explains some of this in a little more detail. Please feel welcome to participate. I am just an ontology designer, and need as much real field experience to help make this work well. Henry On 5 Mar 2007, at 14:51, Henry Story wrote: > Hi, > > I am just starting to develop a Bug Ontology. > http://blogs.sun.com/bblfish/entry/baetle_bug_and_enhancement_tracking > > This should enable different bug tracking systems to put up SPARQL > endpoints making them easily queryable by all kinds of agents. > > Perhaps some people here would be interested in joining or listening > in. I need to have something practical going quickly, so I am hoping > to get there in a very iterative fashion. > > There is a nice library called D2RQ that makes it very easy to map > an SQL database into SPARQL. So technically this should easily be able > to be added onto the current bugzilla setup in due time. > > Henry > > [1] http://blogs.sun.com/bblfish/entry/sparqling_roller > the endpoint is down right now but the pdf slides explain well > what is happening > > Home page: http://bblfish.net/ > Sun Blog: http://blogs.sun.com/bblfish/ > Foaf name: http://bblfish.net/people/henry/card#me > > > From lpsolit at gmail.com Wed Mar 7 15:10:27 2007 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Wed, 07 Mar 2007 16:10:27 +0100 Subject: Priority System for Enhancements (Implemented) In-Reply-To: <20070307123816.9AA081817C@help.trusthosting.net> References: <20070227214800.5002518291@help.trusthosting.net> <20070307123816.9AA081817C@help.trusthosting.net> Message-ID: <45EED5E3.6070307@gmail.com> > triaged all of them yet. :-) If you think that there's a bug clearly > missing from that list, feel free to email me and point out (in two or > three sentences maximum) why you think your bug should be on that list. Or set the priority yourself if you have editbugs privs. From mkanat at bugzilla.org Wed Mar 7 20:11:43 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 7 Mar 2007 12:11:43 -0800 Subject: Priority System for Enhancements (Implemented) In-Reply-To: <45EED5E3.6070307@gmail.com> References: <20070227214800.5002518291@help.trusthosting.net> <20070307123816.9AA081817C@help.trusthosting.net> <45EED5E3.6070307@gmail.com> Message-ID: <20070307201148.2DFC11817C@help.trusthosting.net> On Wed, 07 Mar 2007 16:10:27 +0100 Fr?d?ric Buclin wrote: > Or set the priority yourself if you have editbugs privs. Right, of course. :-) Although it may be adjusted by a reviewer at some point if the setter is not a reviewer. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From goobix at gmail.com Wed Mar 7 22:01:32 2007 From: goobix at gmail.com (Vlad Dascalu) Date: Thu, 8 Mar 2007 00:01:32 +0200 Subject: Priority System for Enhancements (Implemented) In-Reply-To: <20070307201148.2DFC11817C@help.trusthosting.net> References: <20070227214800.5002518291@help.trusthosting.net> <20070307123816.9AA081817C@help.trusthosting.net> <45EED5E3.6070307@gmail.com> <20070307201148.2DFC11817C@help.trusthosting.net> Message-ID: Right, of course. But you're not the only reviewer (as the first mail implied). On 3/7/07, Max Kanat-Alexander wrote: > > On Wed, 07 Mar 2007 16:10:27 +0100 Fr?d?ric Buclin > wrote: > > Or set the priority yourself if you have editbugs privs. > > Right, of course. :-) Although it may be adjusted by a reviewer > at some point if the setter is not a reviewer. > > -Max > -- > http://www.everythingsolved.com/ > Competent, Friendly Bugzilla Services. And Everything Else, too. > - > To view or change your list settings, click here: > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkanat at bugzilla.org Thu Mar 8 14:15:24 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 8 Mar 2007 06:15:24 -0800 Subject: Priority System for Enhancements (Implemented) In-Reply-To: <20070307201148.2DFC11817C@help.trusthosting.net> References: <20070227214800.5002518291@help.trusthosting.net> <20070307123816.9AA081817C@help.trusthosting.net> <45EED5E3.6070307@gmail.com> <20070307201148.2DFC11817C@help.trusthosting.net> Message-ID: <20070308141525.A15E11817C@help.trusthosting.net> On Wed, 7 Mar 2007 12:11:43 -0800 Max Kanat-Alexander wrote: > Right, of course. :-) Although it may be adjusted by a > reviewer at some point if the setter is not a reviewer. Oh, and of course, if two reviewers disagree on the priority that a bug should have, then they should talk about it until they come to some decision. :-) I figured that was fairly obvious, but I guess it doesn't hurt to say it, either. :-) -Max From mkanat at bugzilla.org Fri Mar 9 05:36:00 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 8 Mar 2007 21:36:00 -0800 Subject: InnoDB Message-ID: <20070309053605.478F91817C@help.trusthosting.net> All tables in Bugzilla now use InnoDB on MySQL, except the longdescs table (because it needs a fulltext index, and InnoDB doesn't support fulltext indexes). (We agreed to move to InnoDB many months ago, but to delay it until the beginning of the 3.2 development cycle, to give us enough testing time. We're now there, so I committed the change.) -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Fri Mar 9 22:20:50 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Fri, 9 Mar 2007 14:20:50 -0800 Subject: Welcome to Referential Integrity! Message-ID: <20070309222102.DFB1C8C800C@help.trusthosting.net> Hello, Bugzilla passengers! We have now landed at Referential Integrity Airport. :-) You can read a bit about it here: http://www.bugzilla.org/docs/tip/html/api/Bugzilla/DB/Schema.html#Referential_Integrity (Or at least, you'll be able to when the website updates itself.) What this means that's most important to remember is that you have to now insert things in the "right order." What's that mean? Well, example: if you want something to reference a row in the bugs table, you have to actually insert that row in the bugs table before you insert the row that references it. It does make sense. :-) Also, the reverse is true for deletion--if a row references the bugs table, you have to delete that row *before* you delete the bug. This will nicely prevent database corruption, even if people modify their databases manually. It will also eventually allow us to easily delete things from the database, or at least keep track of when we should be deleting something before we delete something else. :-) It's actually only implemented on profiles_activity right now, but it will eventually be showing up in every table in Bugzilla. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From justdave at bugzilla.org Sat Mar 10 00:54:52 2007 From: justdave at bugzilla.org (David Miller) Date: Fri, 09 Mar 2007 19:54:52 -0500 Subject: InnoDB In-Reply-To: <20070309053605.478F91817C@help.trusthosting.net> References: <20070309053605.478F91817C@help.trusthosting.net> Message-ID: <45F201DC.5090601@bugzilla.org> Max Kanat-Alexander wrote on 3/9/07 12:36 AM: > All tables in Bugzilla now use InnoDB on MySQL, except the > longdescs table (because it needs a fulltext index, and InnoDB doesn't > support fulltext indexes). > > (We agreed to move to InnoDB many months ago, but to delay it > until the beginning of the 3.2 development cycle, to give us enough > testing time. We're now there, so I committed the change.) If we mention mysqlhotcopy anywhere in our docs or examples, we need to get rid of it. -- 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 Sat Mar 10 22:26:51 2007 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Sat, 10 Mar 2007 23:26:51 +0100 Subject: Bugzilla 2.23.3, 2.23.4 and 3.0 RC1: Data is corrupted in data/mining/* Message-ID: <45F330AB.3060805@gmail.com> Hello, I just found a bug in collectstats.pl which corrupts data in installations running 2.23.3 and newer, see bug 373492. The good news is that this only affects old charts. The bad news is that you may have to regenerate all your data running ./collectstats.pl --regenerate, which may take a *very* long time on large installations. I expect to have this bug fixed in the coming hours. LpSolit From justdave at bugzilla.org Tue Mar 13 17:04:51 2007 From: justdave at bugzilla.org (David Miller) Date: Tue, 13 Mar 2007 13:04:51 -0400 Subject: [Fwd: [Justdave's Blog] Comment: "Bugzilla 3.0rc1 released"] Message-ID: <45F6D9B3.6070209@bugzilla.org> This comment was left on my blog. I'm not sure of a good answer so I figured I'd point it out in case anyone wants to reply to him. :) -------- Original Message -------- Subject: [Justdave's Blog] Comment: "Bugzilla 3.0rc1 released" Date: Mon, 12 Mar 2007 20:28:52 -0700 (PDT) From: Var New comment on your post #70 "Bugzilla 3.0rc1 released" Comment: I noticed that in RC1 bug details page come up with boxes around the header sections such as Details, People, Related actions. These are not aesthetically well aligned for good visual appeal so is there a way to revert the look and feel of bug detail page back to the 2.23.x for the layout positioning? -- Var You can see all comments on this post here: http://www.justdave.net/dave/2007/02/26/bugzilla-30rc1-released/#comments -- 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 Wed Mar 14 06:38:42 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 13 Mar 2007 23:38:42 -0700 Subject: [Fwd: [Justdave's Blog] Comment: "Bugzilla 3.0rc1 released"] In-Reply-To: <45F6D9B3.6070209@bugzilla.org> References: <45F6D9B3.6070209@bugzilla.org> Message-ID: <20070314063850.247BF8C8003@help.trusthosting.net> On Tue, 13 Mar 2007 13:04:51 -0400 David Miller wrote: > I noticed that in RC1 bug details page come up with boxes around the > header sections such as Details, People, Related actions. These are > not aesthetically well aligned for good visual appeal so is there a > way to revert the look and feel of bug detail page back to the 2.23.x > for the layout positioning? The answer is "no." :-) But we'll work on it for Bugzilla 3.2. I've already started. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From after.fallout at gmail.com Wed Mar 14 12:21:41 2007 From: after.fallout at gmail.com (Bill Barry) Date: Wed, 14 Mar 2007 08:21:41 -0400 Subject: [Fwd: [Justdave's Blog] Comment: "Bugzilla 3.0rc1 released"] In-Reply-To: <45F6D9B3.6070209@bugzilla.org> References: <45F6D9B3.6070209@bugzilla.org> Message-ID: <45F7E8D5.3080207@gmail.com> David Miller wrote: > I noticed that in RC1 bug details page come up with boxes around the > header sections such as Details, People, Related actions. These are not > aesthetically well aligned for good visual appeal so is there a way to > revert the look and feel of bug detail page back to the 2.23.x for the > layout positioning? You can turn off the borders and labels if you want with the following css: fieldset { border: 0; } fieldset legend { display: none; } From after.fallout at gmail.com Wed Mar 14 22:06:35 2007 From: after.fallout at gmail.com (Bill Barry) Date: Wed, 14 Mar 2007 18:06:35 -0400 Subject: Bugzilla HEAD not sending email? Message-ID: <45F871EB.3050806@gmail.com> I am having trouble with Bugzilla cvs HEAD not sending any emails. In process-bug it is always saying sent to = none (it should at least send to myself as I have all mail on). It was working before I did an update this morning (previous update was around 3/01). Does anyone know what could be causing this? mail delivery method: SMTP checksetup module report: Checking perl modules... Checking for CGI (v2.93) ok: found v3.25 Checking for TimeDate (v2.21) ok: found v2.22 Checking for DBI (v1.41) ok: found v1.52 Checking for PathTools (v0.84) ok: found v3.23 Checking for Template-Toolkit (v2.12) ok: found v2.15 Checking for Email-Send (v2.00) ok: found v2.171 Checking for Email-MIME-Modifier (any) ok: found v1.440 Checking available perl DBD modules... Checking for DBD-Pg (v1.45) not found Checking for DBD-mysql (v2.9003) ok: found v4.00 The following Perl modules are optional: Checking for GD (v1.20) ok: found v2.35 Checking for Template-GD (any) ok: found v1.56 Checking for Chart (v1.0) ok: found v2.3 Checking for GDGraph (any) ok: found v1.4308 Checking for GDTextUtil (any) ok: found v0.86 Checking for XML-Twig (any) ok: found v3.26 Checking for MIME-tools (v5.406) ok: found v5.420 Checking for libwww-perl (any) ok: found v2.033 Checking for PatchReader (v0.9.4) ok: found v0.9.5 Checking for PerlMagick (any) ok: found v6.2.9 Checking for perl-ldap (any) ok: found v0.33 Checking for SOAP-Lite (any) ok: found v0.69 Checking for HTML-Parser (v3.40) ok: found v3.55 Checking for HTML-Scrubber (any) ok: found v0.08 Checking for Email-MIME-Attachment-Stripper (any) ok: found v1.311 Checking for Email-Reply (any) ok: found v1.200 Checking for mod_perl (v1.999022) ok: found v2.000002 Checking for CGI (v3.11) ok: found v3.25 Checking for Apache-DBI (v0.96) ok: found v1.03 Reading ./localconfig... Checking for DBD-mysql (v2.9003) ok: found v4.00 Checking for MySQL (v4.1.2) ok: found v5.0.22 From mkanat at bugzilla.org Thu Mar 15 00:32:33 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 14 Mar 2007 17:32:33 -0700 Subject: Bugzilla HEAD not sending email? In-Reply-To: <45F871EB.3050806@gmail.com> References: <45F871EB.3050806@gmail.com> Message-ID: <20070315003242.68398182C7@help.trusthosting.net> On Wed, 14 Mar 2007 18:06:35 -0400 Bill Barry wrote: > I am having trouble with Bugzilla cvs HEAD not sending any emails. In > process-bug it is always saying sent to = none (it should at least > send to myself as I have all mail on). > It was working before I did an update this morning (previous update > was around 3/01). Does anyone know what could be causing this? Normally I'd say to ask the support-list instead of here, but I saw the same thing on my tip installation the other day--I'm not quite sure what's causing it. Could you file a bug, perhaps, if one hasn't already been filed? -Max From justdave at bugzilla.org Thu Mar 15 03:35:53 2007 From: justdave at bugzilla.org (David Miller) Date: Wed, 14 Mar 2007 23:35:53 -0400 Subject: Summer of Code Projects In-Reply-To: <20070227083629.157F61828E@help.trusthosting.net> References: <20070227083629.157F61828E@help.trusthosting.net> Message-ID: <45F8BF19.8090801@bugzilla.org> Max Kanat-Alexander wrote on 2/27/07 3:36 AM: > Hey, I was thinking that we should submit some applications for > Google's Summer of Code, for Bugzilla. Anybody have any ideas of some > projects that we could suggest that somebody work on? Just to follow up on this topic, Mozilla has decided to have us go in under their banner for this, and have given us two project slots. It's time to get the ideas added to http://wiki.mozilla.org/Community:SummerOfCode07:Brainstorming -- 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 Thu Mar 15 04:46:16 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 14 Mar 2007 21:46:16 -0700 Subject: Transactions! Message-ID: <20070315044628.8240E1818A@help.trusthosting.net> I just checked in full transaction support in the database layer, for Bugzilla. For anybody who doesn't know, a transaction is a way of doing a bunch of SQL commands, and only writing to the disk once they've all succeeded. Also, with transactions you get the same benefits of locking without having to lock the whole table. Let me explain that last part (about getting the advantages of locking) a bit more. When you do a transaction, this is what happens: 1) You start the transaction. ($dbh->bz_start_transaction()) 2) You run at least one SQL statement. 3) From that point on, every other statement sees the database as it was immediately before you ran that first SQL statement. That is, if the database gets modified somehow while you're in the middle of your transaction, it won't affect your transaction. This is a Good Thing, because it avoids race conditions. That's why we have locks in the first place, for the most part--to avoid race conditions. (For those who know about transactions, we use REPEATABLE READ. That could always change, though, if we decide READ COMMITTED or SERIALIZABLE are more appropriate.) 4) You commit the transaction. ($dbh->bz_commit_transaction()) 5) The database writes your changes to disk. Instead of committing, you can also rollback the transaction, which means that none of your changes will be written to disk. Only ThrowError and Bugzilla::_cleanup() need to do this, really. Don't depend on rollback() for the correctness of your code. It's there to handle critical cases, not to undo things that the code decides it shouldn't have done. In other words, don't use rollback in your code. (It should only be in the places where it is now.) You can see the POD docs for the transaction methods here: http://www.bugzilla.org/docs/tip/html/api/Bugzilla/DB.html#Transaction_Methods Note that you can call bz_start_transaction several times and "nest" transactions (but read the docs there on how it works). Generally, we'll be replacing every bz_lock_tables call with a call to bz_start_transaction. Under MySQL, however, the longdescs table isn't transactional. That is, every write to it happens immediately. So it still needs to be locked. If anybody has any questions about transactions, feel free to ask here or in #mozwebtools. I'll probably be doing most of the conversions from bz_lock_tables to bz_start_transaction myself, but if somebody wants to help, they're welcome to file bugs and write patches. The tracking bug is: https://bugzilla.mozilla.org/show_bug.cgi?id=121069 -Max From gerv at mozilla.org Thu Mar 15 10:21:19 2007 From: gerv at mozilla.org (Gervase Markham) Date: Thu, 15 Mar 2007 10:21:19 +0000 Subject: Summer of Code Projects In-Reply-To: <45F8BF19.8090801@bugzilla.org> References: <20070227083629.157F61828E@help.trusthosting.net> <45F8BF19.8090801@bugzilla.org> Message-ID: <45F91E1F.5080707@mozilla.org> David Miller wrote: > Just to follow up on this topic, Mozilla has decided to have us go in > under their banner for this, and have given us two project slots. To be absolutely clear, for the avoidance of disappointment: I discussed this with chofmann, and we are aiming for two. But if the Bugzilla proposals are of particularly high quality, it may be more; if other proposals are particularly good, it could be fewer. I did make the point to him, though, that it would be very rude to invite the Bugzilla team to join in on this and then give it no slots at all. Gerv From after.fallout at gmail.com Thu Mar 15 12:58:43 2007 From: after.fallout at gmail.com (Bill Barry) Date: Thu, 15 Mar 2007 08:58:43 -0400 Subject: Bugzilla HEAD not sending email? In-Reply-To: <20070315003242.68398182C7@help.trusthosting.net> References: <45F871EB.3050806@gmail.com> <20070315003242.68398182C7@help.trusthosting.net> Message-ID: <45F94303.2040608@gmail.com> Max Kanat-Alexander wrote: > Normally I'd say to ask the support-list instead of here, but I > saw the same thing on my tip installation the other day--I'm not quite > sure what's causing it. Could you file a bug, perhaps, if one hasn't > already been filed? > > -Max https://bugzilla.mozilla.org/show_bug.cgi?id=370705 From kevin.benton at amd.com Thu Mar 15 16:03:03 2007 From: kevin.benton at amd.com (Benton, Kevin) Date: Thu, 15 Mar 2007 09:03:03 -0700 Subject: Transactions! In-Reply-To: <20070315044628.8240E1818A@help.trusthosting.net> References: <20070315044628.8240E1818A@help.trusthosting.net> Message-ID: Hi Max, > Note that you can call bz_start_transaction several times and > "nest" transactions (but read the docs there on how it works). One of the things we went over in my MySQL DBA class was: starting a new transaction automatically commits a previous transaction. To quote MySQL 5.0 Certification Study Guide p. 418, "If you issue any of the following statements, InnoDB implicitly commits the preceding uncommitted statements of the current transaction and begins a new transaction: ALTER TABLE BEGIN CREATE INDEX DROP DATABASE DROP INDEX DROP TABLE RENAME TABLE TRUNCATE TABLE LOCK TABLES UNLOCK TABLES SET AUTOCOMMIT = 1 START TRANSACTION UNLOCK TABLES implicitly commits only if you have explicitly locked tables with LOCK TABLES. SET AUTOCOMMIT = 1 implicitly commits only if autocommit mode wasn't already enabled." I'm concerned that developers might get confused by this if they're used to the way that MySQL handles transactions. How does bz_start_transaction deal with this? It's good, however, that the transaction isolation level is settable at the global and session levels so that mod_perl clients. It seems that having the ability to set the isolation level dynamically makes sense as a parameter to bz_start_transaction, but sets it by default to repeatable read. Then, the isolation level would remain in effect only for that transaction. I think that would be a very good improvement to an already nice set of improvements to the Bugzilla DB. For those that are not familiar with MySQL transactions, the reason this is so critical with mod_perl clients is that starting a transaction doesn't just impact inserts and updates (writes) to the database. It also impacts selects (reads). So, as soon as a transaction is started, with repeatable read, the database essentially takes a snapshot of the data at that point in time and provides results accordingly. If that transaction is not closed out, that session will only get to see data from the point in time where the transaction was started. In other words, even though subsequent commits may have been done, that mod_perl session will not (can not) see those updates. That's why I'm concerned about bz_start_transaction implementing transaction nesting with repeatable read isolation. If you'd like to read more about InnoDB Isolation levels, multi-versioning, and concurrency, check out MySQL 5.0 Certification Study Guide p. 420-422. Kevin Benton Senior Software Developer MSS Silicon Design Engineering 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, March 14, 2007 10:46 PM > To: developers at bugzilla.org > Subject: Transactions! > > > I just checked in full transaction support in the database > layer, for Bugzilla. > > For anybody who doesn't know, a transaction is a way of doing a > bunch of SQL commands, and only writing to the disk once they've all > succeeded. > > Also, with transactions you get the same benefits of locking > without having to lock the whole table. > > Let me explain that last part (about getting the advantages of > locking) a bit more. When you do a transaction, this is what happens: > > 1) You start the transaction. ($dbh->bz_start_transaction()) > > 2) You run at least one SQL statement. > > 3) From that point on, every other statement sees the database > as it was immediately before you ran that first SQL statement. That is, > if the database gets modified somehow while you're in the middle of > your transaction, it won't affect your transaction. This is a Good > Thing, because it avoids race conditions. That's why we have locks in > the first place, for the most part--to avoid race conditions. (For > those who know about transactions, we use REPEATABLE READ. That could > always change, though, if we decide READ COMMITTED or SERIALIZABLE are > more appropriate.) > > 4) You commit the transaction. ($dbh->bz_commit_transaction()) > > 5) The database writes your changes to disk. > > Instead of committing, you can also rollback the transaction, > which means that none of your changes will be written to disk. Only > ThrowError and Bugzilla::_cleanup() need to do this, really. > > Don't depend on rollback() for the correctness of your code. > It's there to handle critical cases, not to undo things that the code > decides it shouldn't have done. In other words, don't use rollback in > your code. (It should only be in the places where it is now.) > > You can see the POD docs for the transaction methods here: > > http://www.bugzilla.org/docs/tip/html/api/Bugzilla/DB.html#Transacti > on_Methods > > Note that you can call bz_start_transaction several times and > "nest" transactions (but read the docs there on how it works). > > Generally, we'll be replacing every bz_lock_tables call with a > call to bz_start_transaction. > > Under MySQL, however, the longdescs table isn't transactional. > That is, every write to it happens immediately. So it still needs to be > locked. > > If anybody has any questions about transactions, feel free to > ask here or in #mozwebtools. > > I'll probably be doing most of the conversions from > bz_lock_tables to bz_start_transaction myself, but if somebody wants to > help, they're welcome to file bugs and write patches. The tracking bug > is: > > https://bugzilla.mozilla.org/show_bug.cgi?id=121069 > > -Max > - > To view or change your list settings, click here: > > From mkanat at bugzilla.org Thu Mar 15 22:39:32 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 15 Mar 2007 15:39:32 -0700 Subject: Transactions! In-Reply-To: References: <20070315044628.8240E1818A@help.trusthosting.net> Message-ID: <20070315223941.658C48C8001@help.trusthosting.net> On Thu, 15 Mar 2007 09:03:03 -0700 "Benton, Kevin" wrote: > One of the things we went over in my MySQL DBA class was: starting a > new transaction automatically commits a previous transaction. You need to read the cooooooode... :-) > If you'd like to read more about InnoDB Isolation levels, > multi-versioning, and concurrency, check out MySQL 5.0 Certification > Study Guide p. 420-422. Or just read the actual documentation which is free on the web... :-) http://dev.mysql.com/doc/refman/4.1/en/innodb-transaction-model.html -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From kevin.benton at amd.com Fri Mar 16 00:50:55 2007 From: kevin.benton at amd.com (Benton, Kevin) Date: Thu, 15 Mar 2007 17:50:55 -0700 Subject: Transactions! In-Reply-To: <20070315223941.658C48C8001@help.trusthosting.net> References: <20070315044628.8240E1818A@help.trusthosting.net> <20070315223941.658C48C8001@help.trusthosting.net> Message-ID: > On Thu, 15 Mar 2007 09:03:03 -0700 "Benton, Kevin" > wrote: > > One of the things we went over in my MySQL DBA class was: starting a > > new transaction automatically commits a previous transaction. > > You need to read the cooooooode... :-) Hi Max, I did read the code. As I said, this can be a source of confusion for developers who don't expect nested transactions (quoting you from bug 374012 - "Because transactions are nestable in Bugzilla"). I see problems as documented in the following: https://bugzilla.mozilla.org/show_bug.cgi?id=374012 https://bugzilla.mozilla.org/show_bug.cgi?id=374004 https://bugzilla.mozilla.org/show_bug.cgi?id=374093 To summarize: Since this code makes it possible for multiple calls to $dbh->bz_start_transaction, it introduces a weakness. Rollback rolls everything back to the real start of the transaction, not the nested starting point. So, here is one scenario that would demonstrate the weakness: Time 1: Routine A starts a transaction using $dbh->bz_start_transaction. Time 2: Routine A begins an update or insert. Time 3: Routine A calls routine B. Time 4: Routine B starts a transaction using $dbh->bz_start_transaction. Time 5: Routine B begins an update or insert. Time 6: Routine B discovers it must roll back. Time 7: Routine B calls $dbh->bz_rollback_transaction. This causes bz_rollback_transaction to actually roll back the entire transaction. Time 8: Routine B returns to routine A without returning an error or warning back to Routine A. Time 9: Routine A calls routine C. Time 10: Routine C starts a transaction using $dbh->bz_start_transaction. Time 11: bz_start_transaction does a new BEGIN to the DB. Time 12: Routine C updates or inserts into the DB. Time 13: Routine C calls $dbh->bz_commit_transaction. This causes bz_commit_transaction to actually commit the transaction to the DB because there were no "nested" transactions that were active. Routine C's updates have been committed to the database. Time 14: Routine C returns - no errors. Time 15: Routine A does a little more updating and/or inserting but does Not call $dbh->bz_commit_transaction again (why should it - it didn't know it had to). Time 16: Routine A calls $dbh->bz_commit_transaction. This causes RaiseError to be called because there is no active transaction. Note that because of the rollback from "second" transaction, this negatively impacted the first, and by implication, the "third". Each of these is really supposed to be a part of one real transaction, but they're technically separate because each calls $dbh->bz_start_transaction. Each caller currently has no way of knowing that another transaction is already active. You could argue that we don't have this condition today - you'd be right. The problem is, we do nothing to prevent it, nor do we have documentation to help developers & reviewers to avoid it. The only way to really prevent this from happening is to make sure that each CGI (or other form of main program) calls $dbh->bz_start_transaction as it starts (implicitly turning off autocommit), then calls $dbh->bz_commit_transaction as it completes. At the same time, make any call to $dbh->bz_rollback_transaction execute the rollback and then throw an error. That way, all processing is done within a "root" transaction. We would need to agree as reviewers to refuse to allow transactions to occur one after another in series. This would not work, however, for mod_perl sessions since they persist beyond one user's connection. Another method would need to be used in order to make that work. Because $dbh->bz_commit() causes RaiseError to be called (killing the CGI), it's difficult if not impossible to ask a CGI to clean up after itself given the code in place today. Kevin Benton Senior Software Developer MSS Silicon Design Engineering 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 mkanat at bugzilla.org Fri Mar 16 05:40:34 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 15 Mar 2007 22:40:34 -0700 Subject: Transactions! In-Reply-To: References: <20070315044628.8240E1818A@help.trusthosting.net> <20070315223941.658C48C8001@help.trusthosting.net> Message-ID: <20070316054044.84A328C8001@help.trusthosting.net> On Thu, 15 Mar 2007 17:50:55 -0700 "Benton, Kevin" wrote: > I did read the code. As I said, this can be a source of confusion for > developers who don't expect nested transactions Um, what? They ought to expect them--they're documented and I explained just now that they happen. > Time 6: Routine B discovers it must roll back. > > Time 7: Routine B calls $dbh->bz_rollback_transaction. This causes > bz_rollback_transaction to actually roll back the entire > transaction. This is correct. As I said, Bugzilla will not depend on rollback for correctness. The only time rollback will happen is during a fatal error. The situation you specify will never happen in Bugzilla code. Nobody will ever rollback and then return to another function. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Fri Mar 16 05:58:01 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 15 Mar 2007 22:58:01 -0700 Subject: Transactions! In-Reply-To: References: <20070315044628.8240E1818A@help.trusthosting.net> <20070315223941.658C48C8001@help.trusthosting.net> Message-ID: <20070316055811.833048C8001@help.trusthosting.net> On Thu, 15 Mar 2007 17:50:55 -0700 "Benton, Kevin" wrote: > You could argue that we don't have this condition today - you'd be > right. See http://www.bugzilla.org/docs/developer.html#general -- "...many programmers are constantly solving problems that nobody has ever experienced. Don't do that." > nor do we have > documentation to help developers & reviewers to avoid it. You can file a bug for "please add two sentences to the documentation of bz_rollback_transaction specifying that it should only be used in Bugzilla::_cleanup() and throw_error, and that developers must not rely on it for correctness." -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Fri Mar 16 06:01:34 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 15 Mar 2007 23:01:34 -0700 Subject: Transactions! In-Reply-To: References: <20070315044628.8240E1818A@help.trusthosting.net> <20070315223941.658C48C8001@help.trusthosting.net> Message-ID: <20070316060144.8EFFB8C8001@help.trusthosting.net> On Thu, 15 Mar 2007 17:50:55 -0700 "Benton, Kevin" wrote: > This would not work, however, for mod_perl sessions since they persist > beyond one user's connection. Also, just in case anybody is reading this list and is somehow worried by this statement: this isn't a problem. We handle this in the CleanupHandler, which should run even if a script dies. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Fri Mar 16 16:56:02 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Fri, 16 Mar 2007 09:56:02 -0700 Subject: Major Installation Work Coming Up Message-ID: <20070316165613.58C8418181@help.trusthosting.net> I'm going to start working on web-based installation today, so installation may be a bit unstable in the coming weeks. (It will require a lot of modifications of standard installation.) I'll do my best to keep everything stable, but I did just want to warn everybody that there are going to be lots of changes, and so if something is a bit broken now and again, don't be too surprised. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From justdave at bugzilla.org Sat Mar 17 07:49:36 2007 From: justdave at bugzilla.org (David Miller) Date: Sat, 17 Mar 2007 03:49:36 -0400 Subject: Project description for MySQLConf Message-ID: <45FB9D90.7020802@bugzilla.org> The Bugzilla project will be sending a few representatives to MySQLConf this year to take part in the DotOrg Pavilion. I need to come up with a short description of the Bugzilla project for use on http://www.mysqlconf.com/pub/w/54/dotorg.html We have a short description at the top of http://www.bugzilla.org/about/ but I'm not sure how appropriate that is. Anyone have suggestions for text to submit for that page? -- 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 Sat Mar 17 14:41:21 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 17 Mar 2007 07:41:21 -0700 Subject: Project description for MySQLConf In-Reply-To: <45FB9D90.7020802@bugzilla.org> References: <45FB9D90.7020802@bugzilla.org> Message-ID: <20070317144134.7CF4E8C8001@help.trusthosting.net> On Sat, 17 Mar 2007 03:49:36 -0400 David Miller wrote: > I need to come up with a short description of the Bugzilla project for > use on http://www.mysqlconf.com/pub/w/54/dotorg.html Here's what I submitted to LinuxWorld: Bugzilla is a popular open source bug-tracking system in use by thousands of businesses world-wide to track defects and planned enhancements in products and processes. Designed originally by Netscape in 1998, it has become the de facto standard in open-source bug tracking, and even major commercial products now market themselves by how they compare to Bugzilla. Bugzilla is a versatile web based system that can be used with a minimal footprint to provide powerful defect tracking for all manner of development projects. Bugzilla has been proven in the real world to support groups of any size, from a small open-source project to a multinational enterprise. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Sat Mar 17 23:38:27 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sat, 17 Mar 2007 16:38:27 -0700 Subject: Summer of Code Suggestions Posted Message-ID: <20070317233839.ADF958C8001@help.trusthosting.net> Hey all. I've posted some suggestions for the Summer of Code projects, here: http://wiki.mozilla.org/Community:SummerOfCode07:Brainstorming#Suggestion_List Two of them need mentors! Also, any other ideas are welcome. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From gerv at mozilla.org Tue Mar 20 17:31:18 2007 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 20 Mar 2007 17:31:18 +0000 Subject: Summer of Code status Message-ID: <46001A66.503@mozilla.org> Two Bugzilla projects are now on the official list for Summer of Code. mkanat has suggested a third one - "Duplicate Bug Detection" - but it hasn't moved across because no-one has volunteered to mentor it. For this, any of the core team would be acceptable, if someone wants to stick their name in the wiki. Also, interest is currently looking a little light, so there's opportunity for the Bugzilla project to get more than the two slots. If you have more ideas, get them in there (ideally with a mentor attached) :-) Gerv From mkanat at bugzilla.org Tue Mar 20 17:53:48 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 20 Mar 2007 10:53:48 -0700 Subject: Meeting Today Message-ID: <20070320175408.1670C8C8003@help.trusthosting.net> Hey all. Sorry for the late notice, but it looks like we have a meeting today, right about now. You can see the agenda here: http://wiki.mozilla.org/Bugzilla:Meetings -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Wed Mar 21 21:18:16 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 21 Mar 2007 14:18:16 -0700 Subject: Bugzilla: UI Design Message-ID: <20070321211849.661DB8C8003@help.trusthosting.net> I was having a few thoughts on UI Design, and then they sort of turned into a lot of thoughts, so I wrote something up on the Wiki: http://wiki.mozilla.org/Bugzilla:UI_Design That's a set of UI design guidelines, and things to keep in mind while you're doing UI design. Bugzilla doesn't really follow them now, although it does follow them in some places. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Wed Mar 21 22:50:34 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 21 Mar 2007 15:50:34 -0700 Subject: Bugzilla: Communicate Message-ID: <20070321225052.778C38C8003@help.trusthosting.net> This is part of the "make it easier to contribute to Bugzilla" project: http://wiki.mozilla.org/Bugzilla:Communicate Note that I've set up a CGI IRC gateway for people who can't easily get on IRC: http://landfill.bugzilla.org/irc/ You may also notice that I've started work here: http://wiki.mozilla.org/Bugzilla:Developers Once that's done, it'll be linked from http://www.bugzilla.org/contribute/ under the "code" section. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From after.fallout at gmail.com Wed Mar 21 23:07:16 2007 From: after.fallout at gmail.com (Bill Barry) Date: Wed, 21 Mar 2007 19:07:16 -0400 Subject: Bugzilla: Communicate In-Reply-To: <20070321225052.778C38C8003@help.trusthosting.net> References: <20070321225052.778C38C8003@help.trusthosting.net> Message-ID: <4601BAA4.1090005@gmail.com> Max Kanat-Alexander wrote: > This is part of the "make it easier to contribute to Bugzilla" > project: > > http://wiki.mozilla.org/Bugzilla:Communicate > > Note that I've set up a CGI IRC gateway for people who can't > easily get on IRC: > > http://landfill.bugzilla.org/irc/ > Thank you; irc.mozilla.org is blocked by our network due to a SLA agreement with a large client; but landfill.bugzilla.org never will be. From gerv at mozilla.org Tue Mar 27 12:21:17 2007 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 27 Mar 2007 13:21:17 +0100 Subject: SoC applications Message-ID: <46090C3D.4020302@mozilla.org> Sadly, no-one applied to do any of the Bugzilla-related SoC projects :-( Clearly we don't have many students in our user/potential developer base. Sorry :-( Gerv From amaurya at brickred.com Tue Mar 27 13:19:19 2007 From: amaurya at brickred.com (Ajay Maurya) Date: Tue, 27 Mar 2007 18:49:19 +0530 Subject: SoC applications In-Reply-To: <46090C3D.4020302@mozilla.org> References: <46090C3D.4020302@mozilla.org> Message-ID: <1175001559.2986.10.camel@localhost.localdomain> Can I get some idea about Soc projects -Ajay On Tue, 2007-03-27 at 13:21 +0100, Gervase Markham wrote: > Sadly, no-one applied to do any of the Bugzilla-related SoC projects :-( > Clearly we don't have many students in our user/potential developer base. > > Sorry :-( > > Gerv > - > To view or change your list settings, click here: > From gerv at mozilla.org Tue Mar 27 14:36:03 2007 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 27 Mar 2007 15:36:03 +0100 Subject: SoC applications In-Reply-To: <1175001559.2986.10.camel@localhost.localdomain> References: <46090C3D.4020302@mozilla.org> <1175001559.2986.10.camel@localhost.localdomain> Message-ID: <46092BD3.5030604@mozilla.org> Ajay Maurya wrote: > Can I get some idea about Soc projects I'm not sure what you mean. It's now too late to apply. The ideas that were available can be found here: http://wiki.mozilla.org/Community:SummerOfCode07#Bugzilla Gerv From mkanat at bugzilla.org Tue Mar 27 20:33:34 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 27 Mar 2007 13:33:34 -0700 Subject: SoC applications In-Reply-To: <46090C3D.4020302@mozilla.org> References: <46090C3D.4020302@mozilla.org> Message-ID: <20070327203400.9980D8C8003@help.trusthosting.net> On Tue, 27 Mar 2007 13:21:17 +0100 Gervase Markham wrote: > Sadly, no-one applied to do any of the Bugzilla-related SoC > projects :-( Clearly we don't have many students in our > user/potential developer base. Or we just didn't get the word out early enough, or people don't associate Bugzilla with the Mozilla Foundation. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From amaurya at brickred.com Tue Mar 27 13:19:33 2007 From: amaurya at brickred.com (Ajay Maurya) Date: Tue, 27 Mar 2007 18:49:33 +0530 Subject: SoC applications In-Reply-To: <46090C3D.4020302@mozilla.org> References: <46090C3D.4020302@mozilla.org> Message-ID: <1175001573.2986.12.camel@localhost.localdomain> Can I get some idea about Soc projects -Ajay On Tue, 2007-03-27 at 13:21 +0100, Gervase Markham wrote: > Sadly, no-one applied to do any of the Bugzilla-related SoC projects :-( > Clearly we don't have many students in our user/potential developer base. > > Sorry :-( > > Gerv > - > To view or change your list settings, click here: > From justdave at bugzilla.org Thu Mar 29 04:32:52 2007 From: justdave at bugzilla.org (David Miller) Date: Thu, 29 Mar 2007 00:32:52 -0400 Subject: Project description for MySQLConf In-Reply-To: <20070317144134.7CF4E8C8001@help.trusthosting.net> References: <45FB9D90.7020802@bugzilla.org> <20070317144134.7CF4E8C8001@help.trusthosting.net> Message-ID: <460B4174.2060504@bugzilla.org> Max Kanat-Alexander wrote on 3/17/07 10:41 AM: > On Sat, 17 Mar 2007 03:49:36 -0400 David Miller > wrote: >> I need to come up with a short description of the Bugzilla project for >> use on http://www.mysqlconf.com/pub/w/54/dotorg.html > > Here's what I submitted to LinuxWorld: > > Bugzilla is a popular open source bug-tracking system in use by > thousands of businesses world-wide to track defects and planned > enhancements in products and processes. > > Designed originally by Netscape in 1998, it has become the de facto > standard in open-source bug tracking, and even major commercial > products now market themselves by how they compare to Bugzilla. > Bugzilla is a versatile web based system that can be used with a > minimal footprint to provide powerful defect tracking for all manner of > development projects. > > Bugzilla has been proven in the real world to support groups of any > size, from a small open-source project to a multinational enterprise. OK, I submitted that (back on the 17th), and I got it back today saying it's too long, and could we please shorten it to 50 words or less. Any other bright ideas? I tried cutting that up myself, and couldn't get it under 56 words without making it sound stupid. :) -- 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 justdave at bugzilla.org Thu Mar 29 04:35:13 2007 From: justdave at bugzilla.org (David Miller) Date: Thu, 29 Mar 2007 00:35:13 -0400 Subject: SoC applications In-Reply-To: <20070327203400.9980D8C8003@help.trusthosting.net> References: <46090C3D.4020302@mozilla.org> <20070327203400.9980D8C8003@help.trusthosting.net> Message-ID: <460B4201.60309@bugzilla.org> Max Kanat-Alexander wrote on 3/27/07 4:33 PM: > On Tue, 27 Mar 2007 13:21:17 +0100 Gervase Markham > wrote: >> Sadly, no-one applied to do any of the Bugzilla-related SoC >> projects :-( Clearly we don't have many students in our >> user/potential developer base. > > Or we just didn't get the word out early enough, or people > don't associate Bugzilla with the Mozilla Foundation. In hindsight, we should have sent something to announce@ about it. FYI, we're rapidly approaching 3000 subscribers to the announce@ list (2966 as I type this, and we've generally been getting 5 or so new subscribers per day). -- 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 bugreport at peshkin.net Thu Mar 29 04:54:34 2007 From: bugreport at peshkin.net (Joel Peshkin) Date: Wed, 28 Mar 2007 21:54:34 -0700 Subject: Project description for MySQLConf In-Reply-To: <460B4174.2060504@bugzilla.org> References: <45FB9D90.7020802@bugzilla.org> <20070317144134.7CF4E8C8001@help.trusthosting.net> <460B4174.2060504@bugzilla.org> Message-ID: <460B468A.60907@peshkin.net> How stupid is too stupid?? (50 words assuming-hyphenated-words-are-a-single-word) Bugzilla is an open source bug-tracker used by thousands of businesses to track defects and enhancements. Bugzilla, the standard in open-source bug tracking, is a versatile and powerful web based system with a minimal footprint and is proven to support groups of any size from small projects to multinational enterprises. David Miller wrote: > > OK, I submitted that (back on the 17th), and I got it back today saying > it's too long, and could we please shorten it to 50 words or less. Any > other bright ideas? I tried cutting that up myself, and couldn't get it > under 56 words without making it sound stupid. :) > > From justdave at bugzilla.org Thu Mar 29 05:57:53 2007 From: justdave at bugzilla.org (David Miller) Date: Thu, 29 Mar 2007 01:57:53 -0400 Subject: Project description for MySQLConf In-Reply-To: <460B468A.60907@peshkin.net> References: <45FB9D90.7020802@bugzilla.org> <20070317144134.7CF4E8C8001@help.trusthosting.net> <460B4174.2060504@bugzilla.org> <460B468A.60907@peshkin.net> Message-ID: <460B5561.4090509@bugzilla.org> Hey, that's much better than what I had before, I think I'll run with that. Thanks! Joel Peshkin wrote on 3/29/07 12:54 AM: > > How stupid is too stupid?? (50 words > assuming-hyphenated-words-are-a-single-word) > > Bugzilla is an open source bug-tracker used by thousands of > businesses to track defects and enhancements. > Bugzilla, the standard in open-source bug tracking, is a versatile > and powerful web based system with a minimal footprint > and is proven to support groups of any size from small projects to > multinational enterprises. > > > > David Miller wrote: >> >> OK, I submitted that (back on the 17th), and I got it back today saying >> it's too long, and could we please shorten it to 50 words or less. Any >> other bright ideas? I tried cutting that up myself, and couldn't get it >> under 56 words without making it sound stupid. :) -- 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 Thu Mar 29 06:57:54 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 28 Mar 2007 23:57:54 -0700 Subject: announce@ subscribers (WAS Re: SoC applications) In-Reply-To: <460B4201.60309@bugzilla.org> References: <46090C3D.4020302@mozilla.org> <20070327203400.9980D8C8003@help.trusthosting.net> <460B4201.60309@bugzilla.org> Message-ID: <20070329065822.5D00211800B@help.trusthosting.net> On Thu, 29 Mar 2007 00:35:13 -0400 David Miller wrote: > FYI, we're rapidly approaching 3000 subscribers to the announce@ list > (2966 as I type this, and we've generally been getting 5 or so new > subscribers per day). _Whoa_. Is there any way to see a graph of subscriptions over time, or to get the data that one could use to generate a graph? -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From justdave at bugzilla.org Thu Mar 29 09:55:37 2007 From: justdave at bugzilla.org (David Miller) Date: Thu, 29 Mar 2007 05:55:37 -0400 Subject: announce@ subscribers (WAS Re: SoC applications) In-Reply-To: <20070329065822.5D00211800B@help.trusthosting.net> References: <46090C3D.4020302@mozilla.org> <20070327203400.9980D8C8003@help.trusthosting.net> <460B4201.60309@bugzilla.org> <20070329065822.5D00211800B@help.trusthosting.net> Message-ID: <460B8D19.5030109@bugzilla.org> Max Kanat-Alexander wrote on 3/29/07 2:57 AM: > On Thu, 29 Mar 2007 00:35:13 -0400 David Miller > wrote: >> FYI, we're rapidly approaching 3000 subscribers to the announce@ list >> (2966 as I type this, and we've generally been getting 5 or so new >> subscribers per day). > > _Whoa_. Is there any way to see a graph of subscriptions over > time, or to get the data that one could use to generate a graph? majordomo only appears to keep the logs going back about a month by the look of it, so probably not. -- 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 pabhishek at novell.com Thu Mar 29 12:18:41 2007 From: pabhishek at novell.com (Abhishek Parwal) Date: Thu, 29 Mar 2007 06:18:41 -0600 Subject: bugzilla backend tasks in evolution to manage bugs Message-ID: <460BFBF90200007E000075A2@lucius.provo.novell.com> Hi, I am writing bugzilla backend tasks in evolution to manage bugs as tasks. This will download all saved searches of a user from bugzilla and also fetch the buglist in each saved search query. The Saved Search query will be shown as tasklist and bugs as tasks. The details like summary,description,attachments(patches) will be shown appropriately. The data for all these will be stored in cache and on refresh intervals deltas of changed bugs will be fetched. For all this firstly we must be able to query the bugzilla for its version (as we are fetching buglist in iCal format whose support comes with bugzilla 2.22) then also query for authentication of user to bugzilla with username and password. Then we query to fetch saved searches and then query to fetch buglist in iCal and then probably to fetch the individual bug description,comments and attachments. Thus i need help for authentication, quering version, for fetching saved searches, buglist, attachments,description. Can you give me some pointers(help) to find all this.. Thanks in advance. -Abhishek From lpsolit at gmail.com Thu Mar 29 15:04:24 2007 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Thu, 29 Mar 2007 17:04:24 +0200 Subject: Project description for MySQLConf In-Reply-To: <460B5561.4090509@bugzilla.org> References: <45FB9D90.7020802@bugzilla.org> <20070317144134.7CF4E8C8001@help.trusthosting.net> <460B4174.2060504@bugzilla.org> <460B468A.60907@peshkin.net> <460B5561.4090509@bugzilla.org> Message-ID: <460BD578.4050004@gmail.com> David Miller a ?crit : > Hey, that's much better than what I had before, I think I'll run with > that. Thanks! Yes, thanks Joel, sounds great. From mkanat at bugzilla.org Thu Mar 29 22:36:16 2007 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 29 Mar 2007 15:36:16 -0700 Subject: bugzilla backend tasks in evolution to manage bugs In-Reply-To: <460BFBF90200007E000075A2@lucius.provo.novell.com> References: <460BFBF90200007E000075A2@lucius.provo.novell.com> Message-ID: <20070329223645.1CBC318008@help.trusthosting.net> On Thu, 29 Mar 2007 06:18:41 -0600 "Abhishek Parwal" wrote: > For all this firstly we must be able to query the bugzilla for its > version Use config.cgi. It has several formats. config.cgi&ctype=rdf is XML. > then also query for authentication of user to > bugzilla with username and password. In 3.0 you can do this in the XML-RPC Interface, User.login. Otherwise you'll have to do screen-scraping and figure out if your login succeeded. > fetching saved searches You'd have to screen-scrape for that--we don't export that data in any standard way, right now. >buglist, attachments,description. You might want to look at what my supybot plugin does, there. It's in bzr, so you can do: bzr checkout http://bzr.everythingsolved.com/supybot/Bugzilla And look at the _getBugs subroutine in plugin.py. (And the various subroutines it calls.) Also, the "query" subroutine shows how I do searches. Basically, I use the RDF format of the buglist, and the XML format of a bug. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too.