From mkanat at bugzilla.org Thu Feb 2 22:47:43 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 02 Feb 2006 14:47:43 -0800 Subject: Minutes for Bugzilla Meeting, 2006-02-02 Message-ID: <1138920463.3117.16.camel@localhost.localdomain> We had our first Bugzilla meeting, and it was very successful! If you were unable to attend, please read the log and give your feedback: Primarily, we went over and revised the roadmap, which is now more stable: http://wiki.mozilla.org/Bugzilla:Roadmap The primary obstacle to adding things to the roadmap is finding an assignee and a reviewer to work on them. If we have more assignees, more things can be done. Other Items Discussed --------------------- * Certain highly-invasive security fixes may not be backported to the 2.16 branch, unless Debian is interested (since they have to maintain as far back as 2.14 on their stable branches). justdave will contact Debian. * We are ready to release our next releases, once we fix all the blockers of bug 320306 are fixed: https://bugzilla.mozilla.org/showdependencytree.cgi?id=320306 * myk no longer has the time to dedicate to being the UI owner, the UI component is now owned by "ui at bugzilla.bugs" -- if you'd like to help out with UI, watch ui at bugzilla.bugs. * If we can get mod_perl, custom fields, and better skins, we will call Bugzilla 3.0. Next Meeting ------------ Our next meeting will be on Tuesday, February 14th at 19:00 GMT. Does this time work for you? Will you be there? Any feedback? Let us know! If there's something you'd like to discuss at the next meeting, add it to the agenda at: http://wiki.mozilla.org/Bugzilla:Meetings -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From LpSolit at gmail.com Thu Feb 2 23:44:27 2006 From: LpSolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Fri, 03 Feb 2006 00:44:27 +0100 Subject: Minutes for Bugzilla Meeting, 2006-02-02 In-Reply-To: <1138920463.3117.16.camel@localhost.localdomain> References: <1138920463.3117.16.camel@localhost.localdomain> Message-ID: <43E2995B.6040101@gmail.com> Wiki version available at: http://wiki.mozilla.org/Bugzilla:Meetings:2006-02-02 From priyabansal1 at hotmail.com Fri Feb 3 02:01:46 2006 From: priyabansal1 at hotmail.com (priya bansal) Date: Fri, 03 Feb 2006 02:01:46 +0000 Subject: Hello Fellow Developers Message-ID: Hello friends, An opportunity if anyone is looking for a change!! Contractor for Bugzilla enhancements. A large technology company who use Bugzilla for day-to- day work and record-keeping, need someone who is familiar with the Bugzilla code base (as well as being a good perl programmer) to enhance the product. Modifications to be under the GPL and contributed back to the Bugzilla project. Skills: (a) advanced perl programming skills, (b) experience building RPMs, and (c) experience with Bugzilla. You can mail to shruti at ists-inc.com for further details. thanks Priya From gerv at mozilla.org Fri Feb 3 08:51:10 2006 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 03 Feb 2006 08:51:10 +0000 Subject: Hello Fellow Developers In-Reply-To: References: Message-ID: <43E3197E.30009@mozilla.org> priya bansal wrote: > enhance the product. Modifications to be under the GPL and contributed > back to the Bugzilla project. They won't be much use to us if you GPL them :-) Hopefully you meant MPL, Bugzilla's licence. Gerv From mkanat at bugzilla.org Thu Feb 9 13:51:12 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 09 Feb 2006 05:51:12 -0800 Subject: Everything Solved Looking For Part-Time Bugzilla Coders Message-ID: <1139493073.3257.6.camel@localhost.localdomain> Work from home, your office, or school. Flexible hours. The company founded by one of the country's premier Bugzilla specialists is seeking a part-time REMOTE Bugzilla contractor, up to 20-30 hours a week for short-term work, with more short-term jobs after that if we like you. We will work with your schedule. It's casual Friday every day. Skills Required: + Expert perl abilities + Experience with perl's Template Toolkit Skills Strongly Desired: + Experience using and modifying Bugzilla (on a code level) + Understanding of Object-Oriented design + Professional programming experience Please submit a resume, and (optionally) a code sample to bugzilla-job at everythingsolved.com. Compensation varies between $15-$20/hr depending on skills and experience. The job starts now. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Tue Feb 14 22:15:02 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 14 Feb 2006 14:15:02 -0800 Subject: Minutes for Bugzilla Meeting, 2006-02-14 Message-ID: <1139955302.3257.40.camel@localhost.localdomain> We had our second Bugzilla Meeting today. Here's what we discussed: If you were unable to attend, please read the log and give your feedback: * We haven't released 2.22rc1 yet. I'd really appreciate having an Assistant Release Manager, if anybody's interested. :-) Anybody is qualified--I'll train you. :-) * Debian is going to keep patching 2.16 in their packages, but 2.16.11 will probably be our last official bugzilla.org release. If you file a security bug that affects 2.16, CC sukria on it so that he can fix it for Debian. * We need more reviewers. :-) If you'd like to be a Bugzilla reviewer, a good way to start is to find some really old review requests and do an informal review on them. * We need help triaging old review requests. Certain users no longer respond to reviews (Nick, Tobias, Jouni, Zach, Travis, Jake, and Erik, I believe--although if you're any of those people and you'd like to respond to reviews, just let me know) and any reviews to them should be either: o Set to the proper reviewer per http://www.bugzilla.org/docs/reviewer-list.html o Set to blank o Quickly reviewed to note that the patch no longer applies to CVS tip. Anybody is welcome to do this, we'd really appreciate the assistance! Also, any review requests that are very, very old should be similarly triaged even if they're assigned to an active developer. * We updated the Reviewer List showing who's responsible for what: http://www.bugzilla.org/docs/reviewer-list.html * We could use a reviewer with LDAP experience who'd like to review a few patches. They can be informal reviews; just test the code and look it over for sanity. An official reviewer can do everything else. * I'd like to have somebody be in charge of recruiting and welcoming new developers. Somebody who could make life as easy as possible for new Bugzilla developers and reviewers. If you're interested, contact me in #mozwebtools, email this list, or email me directly. * We need to organize a docs team again. Come one, come all, document Bugzilla! * We could use some tests for correct SQL. See bug 247560 and bug 282493. * Performance issues are high priority for 3.0. As we've known for a long time, the two big performance issues are mod_perl and making BugMail faster in process_bug.cgi. mod_perl comes first, as our highest priority for 3.0. We also need a ->new_from_list() method for Product.pm and friends, so that we only do one SQL call instead of 1800 if we're going to load 1800 Product objects. * summarize_time.cgi could use some improvements (see the log), but nobody in particular stepped up to maintain it. * For the most part, we aren't going to remove any backwards-compatibility code for Bugzilla 3.0. There's a slight chance we'll have a new checksetup.pl. We definitely don't want to break URLs. See bug 327193 if you'd like to discuss removing certain backwards-compatibility elements. Our next meeting is two weeks from today, same time! (19:00 GMT, Tuesday February 28th) -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From kevin.benton at amd.com Wed Feb 15 19:16:24 2006 From: kevin.benton at amd.com (Benton, Kevin) Date: Wed, 15 Feb 2006 11:16:24 -0800 Subject: Sub-bug issue revisited Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A420482D8C1@ssvlexmb2.amd.com> So everyone knows, I considered re-opening 141175, but elected to have an open discussion about this here first. A decision was made to make bug 141175 a dupe of bug 81642 some time ago. Bug 141175 asks for a "sub-bug" feature, and bug 81642 is resolved as fixed having created the bug cloning feature. That's no problem as it helps move us toward the goal, but what I'm seeing is a real need for "sub-issue" identification. I am aware of meta bugs as a method dealing with sub-issues, however, it doesn't really address the problem we're having. Say, we find that one issue exists across ten different languages, but each of those needs to be addressed separately. At this point, there really isn't an easy way to let users specify that updates to a dependent bug are also made in the parent. This is important because we're looking for a way to create a tracking bug giving us the ability to see what's happening with all the dependencies, but at the same time, find a way that will make it possible to enter an update that goes either at the "overall" scope or at the "individual issue" scope and be distributed properly. Here's what I see right now on the way of possible interactions: The parent bug needs to be updated when an update needs to go to everyone. The problem is, that doesn't update any descriptions of any children. An update goes into a child bug appropriately, but none of the other children need to be updated. Still, the parent does need to be updated. One potential solution I see for solving this is to have a new field that may be set when a bug is a parent of other bugs modifying the way the bugs are updated so children are seen as "sub-bugs." Normal updates happen no matter what the field's value is, but if the field is set properly, updates in longdescs are propagated according to additional rules (like above). Either that or something similar could be done with the dependencies table, creating a new sub_bug flag denoting whether or not a bug was a std. dependency or a "sub-bug" issue. I'm just "free-thinking" about this at the moment and would like any feedback you may want to offer. --- Kevin Benton Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator Personal Computing Systems Group Advanced Micro Devices The opinions stated in this communication do not necessarily reflect the view of Advanced Micro Devices and have not been reviewed by management. This communication may contain sensitive and/or confidential and/or proprietary information. Distribution of such information is strictly prohibited without prior consent of Advanced Micro Devices. This communication is for the intended recipient(s) only. If you have received this communication in error, please notify the sender, then destroy any remaining copies of this communication. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mdanjou at neterion.com Wed Feb 15 20:02:54 2006 From: mdanjou at neterion.com (Martin d'Anjou) Date: Wed, 15 Feb 2006 15:02:54 -0500 (EST) Subject: Sub-bug issue revisited In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A420482D8C1@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A420482D8C1@ssvlexmb2.amd.com> Message-ID: > I'm just "free-thinking" about this at the moment and would like any > feedback you may want to offer. Here is some experience with a user hack that implements more or less the idea of "sub-bugs". Regarding sub-bugs, I would be very happy to have a solution that works. I have hacked the source code in my installation to create "families of bugs", such that when a bug is opened, the user can effectively open a tree of bugs with all children blocking the parent bug from closing until the children bugs are closed. We use this to track bugs that need action across multiple components. Children bugs can then be assigned to different individuals and worked on at the same time. The alternative is to keep the bug open and reassign it around until we're done with all the fixes, but this is not very effective as someone will always slow down the chain somewhere. In my hack, I have not gotten around displaying parent and children statuses on the same page yet. Martin From mkanat at bugzilla.org Thu Feb 16 07:08:34 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 15 Feb 2006 23:08:34 -0800 Subject: Sub-bug issue revisited In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A420482D8C1@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A420482D8C1@ssvlexmb2.amd.com> Message-ID: <1140073714.9754.8.camel@localhost.localdomain> On Wed, 2006-02-15 at 11:16 -0800, Benton, Kevin wrote: > So everyone knows, I considered re-opening 141175, but elected to have > an open discussion about this here first. > [snip] I bet a lot of this could be accomplished with some cool enhancements to dependencies, particularly an optional way of displaying them on the parent (instead of how they're displayed now as links, perhaps display more information about them directly on the page). Also, it might be nice to have an easier way to file one bug that has a lot of blockers. I've certainly done that many times and it takes some time! -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From exie at linkageposted.longmusic.com Thu Feb 16 09:43:21 2006 From: exie at linkageposted.longmusic.com (Eddie Xie) Date: Thu, 16 Feb 2006 01:43:21 -0800 Subject: Which version to upgrade to for Bugzilla's MySQL server? Message-ID: My Bugzilla is using an old version of MySQL ("Ver 3.23.51 for pc-linux-gnu on i686"), so I am going to upgrade it. I see that MySQL 5.0 has been out for a few months now. What are people's experiences with it? Has it been field tested enough to be found reliable for use? Or should I go instead to the last release of in the MySQL 4 line? Thanks! -- Eddie Xie From bzorg-ml at rsz.jp Thu Feb 16 12:16:10 2006 From: bzorg-ml at rsz.jp (victory) Date: Thu, 16 Feb 2006 21:16:10 +0900 Subject: Which version to upgrade to for Bugzilla's MySQL server? In-Reply-To: References: Message-ID: <200602161216.k1GCGSAL028064@sheridan.syndicomm.com> On Thu, 16 Feb 2006 01:43:21 -0800 Eddie Xie wrote > My Bugzilla is using an old version of MySQL ("Ver 3.23.51 for > pc-linux-gnu on i686"), so I am going to upgrade it. > I see that MySQL 5.0 has been out for a few months now. What are > people's experiences with it? Has it been field tested enough to be > found reliable for use? Or should I go instead to the last release of > in the MySQL 4 line? AFAIK, prior to 2.20 of Bugzilla aren't tested very well using MySQL 5. 2.22 will be much well tested though. -- victory From bugreport at peshkin.net Thu Feb 16 15:38:26 2006 From: bugreport at peshkin.net (Joel Peshkin) Date: Thu, 16 Feb 2006 07:38:26 -0800 Subject: Sub-bug issue revisited In-Reply-To: <1140073714.9754.8.camel@localhost.localdomain> References: <6F7DA19D05F3CF40B890C7CA2DB13A420482D8C1@ssvlexmb2.amd.com> <1140073714.9754.8.camel@localhost.localdomain> Message-ID: <43F49C72.5040009@peshkin.net> First, I agree that the sub-bug issue is important, but I have not had a flash of insipration on how to best address it. > > Also, it might be nice to have an easier way to file one bug that has a > lot of blockers. I've certainly done that many times and it takes some > time! > > Would it be a good thing to enable the mass-change form to have some URLs that take the user directly to a new bug with a bunch of dependencies already filled in? This way, you query, click mass-change, select a bunch of bugs, then click on a (javascript-dependent) hyperlink that has the list of bugs in the blocking bugs list? This would be a shift of "mass-change" to "perform a mass operation" which I think we need to do anyway because of LpSolit's saved bug lists. (I really want to mass add/subtract bugs from those lists) From dcalvert at AllianceBankNA.com Thu Feb 16 20:23:01 2006 From: dcalvert at AllianceBankNA.com (Calvert, Douglas) Date: Thu, 16 Feb 2006 15:23:01 -0500 Subject: Sub-bug issue revisited Message-ID: It just occurred to me that the sub-bug and my multiple bugs at once ticket have a lot in common. What do you think about: https://bugzilla.mozilla.org/show_bug.cgi?id=327402 (Submit multiple bugs at once based on a predefined template.) > -----Original Message----- > From: developers-owner at bugzilla.org > [mailto:developers-owner at bugzilla.org] On Behalf Of Joel Peshkin > Sent: Thursday, February 16, 2006 10:38 AM > To: developers at bugzilla.org > Subject: Re: Sub-bug issue revisited > > First, I agree that the sub-bug issue is important, but I > have not had a > flash of insipration on how to best address it. > > > > Also, it might be nice to have an easier way to file > one bug that has a > > lot of blockers. I've certainly done that many times and it > takes some > > time! > > > > > Would it be a good thing to enable the mass-change form to have some > URLs that take the user directly to a new bug with a bunch of > dependencies already filled in? This way, you query, click > mass-change, > select a bunch of bugs, then click on a > (javascript-dependent) hyperlink > that has the list of bugs in the blocking bugs list? > > This would be a shift of "mass-change" to "perform a mass operation" > which I think we need to do anyway because of LpSolit's saved bug > lists. (I really want to mass add/subtract bugs from those lists) > > > - > To view or change your list settings, click here: > ankna.com> > From Nick.Barnes at pobox.com Fri Feb 17 14:06:57 2006 From: Nick.Barnes at pobox.com (Nick Barnes) Date: Fri, 17 Feb 2006 14:06:57 +0000 Subject: Minutes for Bugzilla Meeting, 2006-02-14 In-Reply-To: <1139955302.3257.40.camel@localhost.localdomain> from Max Kanat-Alexander of "Tue, 14 Feb 2006 14:15:02 -0800" Message-ID: <30444.1140185217@thrush.ravenbrook.com> At 2006-02-14 22:15:02+0000, Max Kanat-Alexander writes: > * We need help triaging old review requests. Certain users no longer > respond to reviews (Nick, Tobias, Jouni, Zach, Travis, Jake, and Erik, I > believe--although if you're any of those people and you'd like to > respond to reviews, just let me know) I'd love to be able to, but due to family health problems I've been unable to do much Bugzilla work for a while, and I'm not expecting to be able to do any for several more months. Nick B From kevin.benton at amd.com Fri Feb 17 16:49:36 2006 From: kevin.benton at amd.com (Benton, Kevin) Date: Fri, 17 Feb 2006 08:49:36 -0800 Subject: Which version to upgrade to for Bugzilla's MySQL server? Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A420482E179@ssvlexmb2.amd.com> > > My Bugzilla is using an old version of MySQL ("Ver 3.23.51 for > > pc-linux-gnu on i686"), so I am going to upgrade it. > > > I see that MySQL 5.0 has been out for a few months now. What are > > people's experiences with it? Has it been field tested enough to be > > found reliable for use? Or should I go instead to the last release of > > in the MySQL 4 line? > > AFAIK, prior to 2.20 of Bugzilla aren't tested very well using MySQL 5. > 2.22 will be much well tested though. You're right that Bugzilla flat-out doesn't work at all with MySQL 5.0.12 and higher prior to Bugzilla 2.20rc1. This is due to a significant change in query requirements from MySQL (making it more ANSI compliant). MySQL doesn't allow SELECT a, b FROM t1, t2 LEFT JOIN t3 ... because it's ambiguous (which table should MySQL join t3 to, t1, or t2?). In Bugzilla 2.20, code was updated to make it work with PgSQL and some of these issues were resolved without making specific attempts at becoming MySQL 5.x compliant. 2.20 was released prior to MySQL 5, so testing against MySQL 5 was not wise (it was still in development). There may be other reasons, but your best bet is to go with at least Bugzilla 2.20 (release). If you choose to wait for 2.22, we're expecting to enter the release candidate process for 2.22 soon. From justdave at bugzilla.org Tue Feb 21 09:23:52 2006 From: justdave at bugzilla.org (David Miller) Date: Tue, 21 Feb 2006 04:23:52 -0500 Subject: Heads up! Need help before opening the trunk Message-ID: <43FADC28.8090407@bugzilla.org> We've finally branched for 2.22! Yay! Before we completely open the trunk, I'd like to do a staged checkin of the 29 bugs that were already sitting in the approval queue waiting for us to branch. That's a lot of bugs, and conflicts and bitrot are not unlikely. This means over the next couple days, if one of those bugs is yours, you may be called upon to update the patch(es). These bugs in the existing queue will get priority since they've been sitting around. Once those are caught up, then we will officially open the trunk again and start some hard core development work. :) -- 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 Tue Feb 21 11:15:48 2006 From: justdave at bugzilla.org (David Miller) Date: Tue, 21 Feb 2006 06:15:48 -0500 Subject: Heads up! Need help before opening the trunk In-Reply-To: <43FADC28.8090407@bugzilla.org> References: <43FADC28.8090407@bugzilla.org> Message-ID: <43FAF664.2070401@bugzilla.org> David Miller wrote on 2/21/06 4:23 AM: > We've finally branched for 2.22! Yay! > > Before we completely open the trunk, I'd like to do a staged checkin of > the 29 bugs that were already sitting in the approval queue waiting for > us to branch. That's a lot of bugs, and conflicts and bitrot are not > unlikely. This means over the next couple days, if one of those bugs is > yours, you may be called upon to update the patch(es). These bugs in > the existing queue will get priority since they've been sitting around. > Once those are caught up, then we will officially open the trunk again > and start some hard core development work. :) And just in case approval flags change around, that list is: http://tinyurl.com/kkqwu That links specifically to those 29 bugs, not a list of bugs with approval? set. :) -- 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 kiko at async.com.br Tue Feb 21 21:55:54 2006 From: kiko at async.com.br (Christian Robottom Reis) Date: Tue, 21 Feb 2006 18:55:54 -0300 Subject: Sub-bug issue revisited In-Reply-To: <1140073714.9754.8.camel@localhost.localdomain> References: <6F7DA19D05F3CF40B890C7CA2DB13A420482D8C1@ssvlexmb2.amd.com> <1140073714.9754.8.camel@localhost.localdomain> Message-ID: <20060221215554.GC4716@anthem.async.com.br> On Wed, Feb 15, 2006 at 11:08:34PM -0800, Max Kanat-Alexander wrote: > On Wed, 2006-02-15 at 11:16 -0800, Benton, Kevin wrote: > > So everyone knows, I considered re-opening 141175, but elected to have > > an open discussion about this here first. > > [snip] > > I bet a lot of this could be accomplished with some cool enhancements > to dependencies, particularly an optional way of displaying them on the > parent (instead of how they're displayed now as links, perhaps display > more information about them directly on the page). We have done, at Async, a number of Bugzilla customizations that support this type of workflow: - Links to allow for easy creation of "child" bugs - Forms to allocate and summarize time invested in a certain bug subtree - Scripts that mass-create bugs attached to parents based on CSV files There may be more; I'd need to check. I think it would be easy to break the dependencytree template up and allow displaying dependencies of a bug in the same page; it would be a matter of deciding whether that is a good idea. We'd be happy to contribute or share these. -- Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125 From exie at linkageposted.longmusic.com Tue Feb 21 21:59:43 2006 From: exie at linkageposted.longmusic.com (Eddie Xie) Date: Tue, 21 Feb 2006 13:59:43 -0800 Subject: Which version to upgrade to for Bugzilla's MySQL server? In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A420482E179@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A420482E179@ssvlexmb2.amd.com> Message-ID: <9i4tq0slmtl57dg5kuq84m4eycs1jw0@mail.mailer-01.linkageposted.longmusic.com> On 2006 February 17 (Fri) 08:49:36am PST, "Benton, Kevin" wrote: > > > My Bugzilla is using an old version of MySQL ("Ver 3.23.51 for > > > pc-linux-gnu on i686"), so I am going to upgrade it. > > > > > I see that MySQL 5.0 has been out for a few months now. What are > > > people's experiences with it? Has it been field tested enough to be > > > found reliable for use? Or should I go instead to the last release of > > > in the MySQL 4 line? > > > > AFAIK, prior to 2.20 of Bugzilla aren't tested very well using MySQL 5. > > 2.22 will be much well tested though. > > You're right that Bugzilla flat-out doesn't work at all with MySQL > 5.0.12 and higher prior to Bugzilla 2.20rc1. This is due to a > significant change in query requirements from MySQL (making it more ANSI > compliant). MySQL doesn't allow SELECT a, b FROM t1, t2 LEFT JOIN t3 > ... because it's ambiguous (which table should MySQL join t3 to, t1, or > t2?). In Bugzilla 2.20, code was updated to make it work with PgSQL and > some of these issues were resolved without making specific attempts at > becoming MySQL 5.x compliant. 2.20 was released prior to MySQL 5, so > testing against MySQL 5 was not wise (it was still in development). > > There may be other reasons, but your best bet is to go with at least > Bugzilla 2.20 (release). If you choose to wait for 2.22, we're > expecting to enter the release candidate process for 2.22 soon. I didn't know that MySQL 5 changed the SELECT syntax. That's good to know. As it happens, my Bugzilla based on a much earlier version than 2.20. It's also has heavy modifications in it, so upgrading to Bugzilla to 2.22 or even 2.20 is not feasible. But it also turns out that modifying Bugzilla for this new syntax is pretty easy for me. (There's one place where I changed >>","<< to >>" JOIN"<<.) I guess some of the complications to this transition didn't get introduced until later. It looks like this new syntax is much better for me, since it allows me to make queries I would not have been able to make without scripting otherwise. Thence, I would prefer to upgrade to MySQL 5, assume that MySQL 5 has been found to be reliable in practice. Have people been using any versions of Bugzilla with MySQL 5? -- Eddie Xie From douglasfcalvert at gmail.com Tue Feb 21 23:27:45 2006 From: douglasfcalvert at gmail.com (Douglas F. Calvert) Date: Tue, 21 Feb 2006 18:27:45 -0500 Subject: Sub-bug issue revisited In-Reply-To: <20060221215554.GC4716@anthem.async.com.br> References: <6F7DA19D05F3CF40B890C7CA2DB13A420482D8C1@ssvlexmb2.amd.com> <1140073714.9754.8.camel@localhost.localdomain> <20060221215554.GC4716@anthem.async.com.br> Message-ID: <20ee876b0602211527j231ce721s95771d38bcc00f9f@mail.gmail.com> > - Scripts that mass-create bugs attached to parents based on CSV > files The new importxml script could be used to do this as well. The nice thing about the importxml method is that you could have a template that let the user create the xml file for importing... From mkanat at bugzilla.org Wed Feb 22 02:34:01 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 21 Feb 2006 18:34:01 -0800 Subject: New landfill home page Message-ID: <1140575642.6043.4.camel@localhost.localdomain> Hey hey. I re-worked the home page on landfill.bugzilla.org to be friendlier for people coming to try out Bugzilla. http://landfill.bugzilla.org/ Haven't tested it in IE yet. Let me know what you think! :-) -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From justdave at bugzilla.org Wed Feb 22 02:48:08 2006 From: justdave at bugzilla.org (David Miller) Date: Tue, 21 Feb 2006 21:48:08 -0500 Subject: New landfill home page In-Reply-To: <1140575642.6043.4.camel@localhost.localdomain> References: <1140575642.6043.4.camel@localhost.localdomain> Message-ID: <43FBD0E8.7010609@bugzilla.org> Max Kanat-Alexander wrote on 2/21/06 9:34 PM: > Hey hey. I re-worked the home page on landfill.bugzilla.org to be > friendlier for people coming to try out Bugzilla. > > http://landfill.bugzilla.org/ > > Haven't tested it in IE yet. > > Let me know what you think! :-) I've been meaning to do something quite similar to that for a year or two. Thank you much for doing it. :) Looks beautiful. -- 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 stu at asyn.com Wed Feb 22 04:07:37 2006 From: stu at asyn.com (Stuart Donaldson) Date: Tue, 21 Feb 2006 20:07:37 -0800 Subject: New landfill home page In-Reply-To: <43FBD0E8.7010609@bugzilla.org> References: <1140575642.6043.4.camel@localhost.localdomain> <43FBD0E8.7010609@bugzilla.org> Message-ID: <43FBE389.9040407@asyn.com> In trying the latest CVS build, the prefs are set wrong, and the cookies have a path of /bugzilla-2.22-branch/ rather than / /bugzilla-tip/ I'm guessing the prefs file was copied over. -Stuart- David Miller wrote: > Max Kanat-Alexander wrote on 2/21/06 9:34 PM: > >> Hey hey. I re-worked the home page on landfill.bugzilla.org to be >> friendlier for people coming to try out Bugzilla. >> >> http://landfill.bugzilla.org/ >> >> Haven't tested it in IE yet. >> >> Let me know what you think! :-) > > > I've been meaning to do something quite similar to that for a year or > two. Thank you much for doing it. :) > > Looks beautiful. > From klenin at gmail.com Wed Feb 22 04:33:02 2006 From: klenin at gmail.com (Alexander Klenin) Date: Wed, 22 Feb 2006 14:33:02 +1000 Subject: New landfill home page In-Reply-To: <43FBD0E8.7010609@bugzilla.org> References: <1140575642.6043.4.camel@localhost.localdomain> <43FBD0E8.7010609@bugzilla.org> Message-ID: There is a typo in url http://landfill.bugzilla.org/Bugzilla-2.22-branch/, should be small 'B'. Max Kanat-Alexander wrote on 2/21/06 9:34 PM: > Hey hey. I re-worked the home page on landfill.bugzilla.org to be > friendlier for people coming to try out Bugzilla. -- Alexander S. Klenin Insight Experts Ltd. From mkanat at bugzilla.org Wed Feb 22 07:18:00 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 21 Feb 2006 23:18:00 -0800 Subject: New landfill home page In-Reply-To: <43FBD0E8.7010609@bugzilla.org> References: <1140575642.6043.4.camel@localhost.localdomain> <43FBD0E8.7010609@bugzilla.org> Message-ID: <1140592680.9638.4.camel@localhost.localdomain> On Tue, 2006-02-21 at 21:48 -0500, David Miller wrote: > I've been meaning to do something quite similar to that for a year or > two. Thank you much for doing it. :) You're welcome! :-) Yeah, I'm happy with it, too. :-) I feel much better directing people to landfill when it looks nice. > Looks beautiful. Aww, thank you. :-) -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From mkanat at bugzilla.org Wed Feb 22 07:20:02 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 21 Feb 2006 23:20:02 -0800 Subject: New landfill home page In-Reply-To: <43FBE389.9040407@asyn.com> References: <1140575642.6043.4.camel@localhost.localdomain> <43FBD0E8.7010609@bugzilla.org> <43FBE389.9040407@asyn.com> Message-ID: <1140592802.9638.6.camel@localhost.localdomain> On Tue, 2006-02-21 at 20:07 -0800, Stuart Donaldson wrote: > In trying the latest CVS build, the prefs are set wrong, and the cookies > have a path of /bugzilla-2.22-branch/ rather than / > /bugzilla-tip/ > > I'm guessing the prefs file was copied over. Ahh, thanks. :-) Yeah, I just made the 2.22 installation yesterday, and I suppose when I went to edit the params, I edited the params for bugzilla-tip accidentally instead. :-) Fixed now. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From LpSolit at gmail.com Wed Feb 22 10:38:54 2006 From: LpSolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Wed, 22 Feb 2006 11:38:54 +0100 Subject: Heads up! Need help before opening the trunk In-Reply-To: <43FADC28.8090407@bugzilla.org> References: <43FADC28.8090407@bugzilla.org> Message-ID: <43FC3F3E.1070802@gmail.com> > Once those are caught up, then we will officially open the trunk again > and start some hard core development work. :) Checkins are all done, except the 3 patches assigned to wurblzap. But I guess he will commit them today anyway. So we can approve and check in new patches. LpSolit From wurblzap at gmail.com Wed Feb 22 12:26:25 2006 From: wurblzap at gmail.com (Marc Schumann) Date: Wed, 22 Feb 2006 13:26:25 +0100 Subject: Heads up! Need help before opening the trunk In-Reply-To: <43FC3F3E.1070802@gmail.com> References: <43FADC28.8090407@bugzilla.org> <43FC3F3E.1070802@gmail.com> Message-ID: Fr?d?ric, 2006/2/22, Fr?d?ric Buclin : > Checkins are all done, except the 3 patches assigned to wurblzap. But I > guess he will commit them today anyway. So we can approve and check in > new patches. would you be so kind and do the check-ins for me? I can't do them from where I am this week... Marc -- http://wurblzap.net/ Bugzilla hosting and professional support From LpSolit at gmail.com Wed Feb 22 12:39:48 2006 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Wed, 22 Feb 2006 13:39:48 +0100 Subject: Heads up! Need help before opening the trunk In-Reply-To: References: <43FADC28.8090407@bugzilla.org> <43FC3F3E.1070802@gmail.com> Message-ID: <43FC5B94.7010106@gmail.com> > would you be so kind and do the check-ins for me? I can't do them from > where I am this week... Oh... you mean *I* have to do all the "fix on checkin" myself? ;) From wurblzap at gmail.com Wed Feb 22 16:26:53 2006 From: wurblzap at gmail.com (Marc Schumann) Date: Wed, 22 Feb 2006 17:26:53 +0100 Subject: Heads up! Need help before opening the trunk In-Reply-To: <43FC5B94.7010106@gmail.com> References: <43FADC28.8090407@bugzilla.org> <43FC3F3E.1070802@gmail.com> <43FC5B94.7010106@gmail.com> Message-ID: 2006/2/22, Fr?d?ric Buclin : > Oh... you mean *I* have to do all the "fix on checkin" myself? ;) Heh, right... Well, if it's not urgent, let it sit where it is and I'll do then check-in as soon as possible. Marc -- http://wurblzap.net/ Bugzilla hosting and professional support From wurblzap at gmail.com Wed Feb 22 16:36:48 2006 From: wurblzap at gmail.com (Marc Schumann) Date: Wed, 22 Feb 2006 17:36:48 +0100 Subject: Heads up! Need help before opening the trunk In-Reply-To: References: <43FADC28.8090407@bugzilla.org> <43FC3F3E.1070802@gmail.com> <43FC5B94.7010106@gmail.com> Message-ID: 2006/2/22, Marc Schumann : > 2006/2/22, Fr?d?ric Buclin : > > Oh... you mean *I* have to do all the "fix on checkin" myself? ;) > > Heh, right... Well, if it's not urgent, let it sit where it is and > I'll do then check-in as soon as possible. I see you proceeded already, and it wasn't too easy either... Thank you, Fr?d?ric :) I owe you a quick review of bug 301020. Regards Marc -- http://wurblzap.net/ Bugzilla hosting and professional support From justdave at bugzilla.org Wed Feb 22 17:11:29 2006 From: justdave at bugzilla.org (David Miller) Date: Wed, 22 Feb 2006 12:11:29 -0500 Subject: Heads up! Need help before opening the trunk In-Reply-To: References: <43FADC28.8090407@bugzilla.org> <43FC3F3E.1070802@gmail.com> <43FC5B94.7010106@gmail.com> Message-ID: <43FC9B41.2060400@bugzilla.org> Marc Schumann wrote on 2/22/06 11:36 AM: > 2006/2/22, Marc Schumann : >> 2006/2/22, Fr?d?ric Buclin : >>> Oh... you mean *I* have to do all the "fix on checkin" myself? ;) >> Heh, right... Well, if it's not urgent, let it sit where it is and >> I'll do then check-in as soon as possible. > > I see you proceeded already, and it wasn't too easy either... Thank > you, Fr?d?ric :) > I owe you a quick review of bug 301020. And with that, the trunk is now officially open! :) (not that the procedures are a heck of a lot different) -- 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 myk at mozilla.org Wed Feb 22 23:24:12 2006 From: myk at mozilla.org (Myk Melez) Date: Wed, 22 Feb 2006 15:24:12 -0800 Subject: prioritizing custom fields development Message-ID: <43FCF29C.9080005@mozilla.org> My initial custom fields implementation has now been checked in and will be appearing in the 2.24 release. It supports adding plain-text custom fields which can be edited from the "edit bug" form and searched against from the "search" page. But the implementation needs more work to be truly useful, and since there are many valuable enhancements, it would be useful to prioritize them. Which custom field functionality is most important to you? For reference, here's a list of proposed enhancements linked to bug reports where available. But don't limit your feedback to just these items. Let me know what else you're looking for, and in what order. Potential Functionality: * product/component-specific custom fields; * administer custom fields via a web interface; * position custom fields at arbitrary locations in the "edit bug" form; * single-select custom fields; * type-constrained plain-text custom fields; * multi-select custom fields; * "Bugzilla user" custom fields; * "Bug ID" custom fields. -myk -------------- next part -------------- An HTML attachment was scrubbed... URL: From LpSolit at gmail.com Wed Feb 22 23:42:40 2006 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Thu, 23 Feb 2006 00:42:40 +0100 Subject: prioritizing custom fields development In-Reply-To: <43FCF29C.9080005@mozilla.org> References: <43FCF29C.9080005@mozilla.org> Message-ID: <43FCF6F0.6000301@gmail.com> > * administer custom fields via a web interface; This one is definitely what I would like to see asap. I hope 'administer' also means creating and removing fields. LpSolit From mkanat at bugzilla.org Thu Feb 23 00:11:22 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 22 Feb 2006 16:11:22 -0800 Subject: prioritizing custom fields development In-Reply-To: <43FCF29C.9080005@mozilla.org> References: <43FCF29C.9080005@mozilla.org> Message-ID: <1140653482.3438.14.camel@localhost.localdomain> On Wed, 2006-02-22 at 15:24 -0800, Myk Melez wrote: > My initial custom fields implementation has now been checked in and > will be appearing in the 2.24 release. It supports adding plain-text > custom fields which can be edited from the "edit bug" form and > searched against from the "search" page. But the implementation needs > more work to be truly useful, and since there are many valuable > enhancements, it would be useful to prioritize them. > [snip] Here's what I was thinking for development order: 1. Enhance the current functionality to make the field appear on all the various pages where it's needed: buglist.cgi, query.cgi, ?Change Several Bugs at Once?, the ?Long List? format of a bug list, and the ?Printable Version? of a bug. I think they already appear in the XML, yes? So we don't have to worry about that. 2. Make the field optionally appear on enter_bug.cgi. 3. A web interface for administering existing custom fields. 4. Type-constrained plain-text fields. I put those in the order that I think they'd be most useful to users, based on the type of fields I've been asked to add to Bugzilla for my clients. Beyond that, off the top of my head I'd say: 5. "Bugzilla user" fields 6. "Bug ID" fields 7. Multi-select fields 8. Ability to position fields at arbitrary positions. Also somewhere in there should be the "change certain existing fields into instances of the custom field". -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla Services. And Everything Else, too. From stu at asyn.com Thu Feb 23 05:15:11 2006 From: stu at asyn.com (Stuart Donaldson) Date: Wed, 22 Feb 2006 21:15:11 -0800 Subject: prioritizing custom fields development In-Reply-To: <43FCF6F0.6000301@gmail.com> References: <43FCF29C.9080005@mozilla.org> <43FCF6F0.6000301@gmail.com> Message-ID: <43FD44DF.6050500@asyn.com> Fr?d?ric Buclin wrote: >> * administer custom fields via a web interface; > > > This one is definitely what I would like to see asap. I hope > 'administer' also means creating and removing fields. I am curious about this one, because it really seems to me like one of the lowest priorities. Administration is a rarely done task, typically done at configuration time. And since it doesn't support per-project custom fields, you don't even do the administration on a per project basis. Perhaps I am wrong here, but it seems like the priority should be about functionality for the operation and use of custom fields. Heck, I don't mind making changes in a configuration file or simple perl code changes to administer custom fields. Is the issue that you are targeting a system where the bugzilla administrator does not have command line access? Cheers -Stuart- From bugreport at peshkin.net Thu Feb 23 05:30:18 2006 From: bugreport at peshkin.net (Joel Peshkin) Date: Wed, 22 Feb 2006 21:30:18 -0800 Subject: prioritizing custom fields development In-Reply-To: <43FCF29C.9080005@mozilla.org> References: <43FCF29C.9080005@mozilla.org> Message-ID: <43FD486A.9080702@peshkin.net> Myk Melez wrote: > > * product/component-specific custom fields; > Yes, but a field should be able to be common to a bunch of products and ignored for others > > * > > > * administer custom fields via a web interface; > * position custom fields at arbitrary locations in the "edit bug" > form; > Or "hook" the field to let a custom template handle certain custom fields while leaving other custom fields auto-positioned > > * > > > * single-select custom fields; > > * type-constrained plain-text custom fields; > > * multi-select custom fields; > > * "Bugzilla user" custom fields; > > * "Bug ID" custom fields. > > Multi-bug-id fields Date fields Fields with group restrictions From LpSolit at gmail.com Thu Feb 23 09:45:24 2006 From: LpSolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Thu, 23 Feb 2006 10:45:24 +0100 Subject: prioritizing custom fields development In-Reply-To: <43FD44DF.6050500@asyn.com> References: <43FCF29C.9080005@mozilla.org> <43FCF6F0.6000301@gmail.com> <43FD44DF.6050500@asyn.com> Message-ID: <43FD8434.30605@gmail.com> >>> * administer custom fields via a web interface; >> >> >> This one is definitely what I would like to see asap. I hope >> 'administer' also means creating and removing fields. > > > I am curious about this one, because it really seems to me like one of > the lowest priorities. Administration is a rarely done task, typically > done at configuration time. And since it doesn't support per-project > custom fields, you don't even do the administration on a per project basis. Oh, this was only my personal preference. I like managing things from a nice UI. But as other people, including yourself, consider this a low priority, I have no problem with that. I don't expect to use customised fields a lot anyway. LpSolit From kevin.benton at amd.com Thu Feb 23 18:06:07 2006 From: kevin.benton at amd.com (Benton, Kevin) Date: Thu, 23 Feb 2006 10:06:07 -0800 Subject: prioritizing custom fields development Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A420497A4A3@ssvlexmb2.amd.com> > Fr?d?ric Buclin wrote: > > >> * administer custom fields via a web interface; > > > > > > This one is definitely what I would like to see asap. I hope > > 'administer' also means creating and removing fields. > > > I am curious about this one, because it really seems to me like one of > the lowest priorities. Administration is a rarely done task, typically > done at configuration time. And since it doesn't support per-project > custom fields, you don't even do the administration on a per project > basis. > > Perhaps I am wrong here, but it seems like the priority should be about > functionality for the operation and use of custom fields. Heck, I don't > mind making changes in a configuration file or simple perl code changes > to administer custom fields. > > Is the issue that you are targeting a system where the bugzilla > administrator does not have command line access? In my mind, it's a usability issue. While it's true that we're technical enough to do this kind of thing as developers, I don't think it's fair to expect Bugzilla administrators to 1) have to manually edit configurations, and 2) know enough to be able to figure out how to fix it when they screwed up their installation due to syntax errors. A web-based UI helps prevent that kind of mistake, and greatly improves usability. Not to mention, doing that also makes it a lot easier for administrators of large / multiple installations to manage customizations (if done properly). Having a web-based UI also makes it a lot easier to train other users how to maintain their own custom fields. It's true that here, some of the users don't have access to the command prompt and are not able to modify configuration files. Frankly, I don't want to give someone the opportunity to cause critical problems with an installation they don't have ultimate operational responsibility for. So, having said all that, in my mind, doing this kind of update from a web-based UI isn't optional, it's a requirement. --- Kevin Benton Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator Personal Computing Systems Group 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 kevin.benton at amd.com Fri Feb 24 00:07:11 2006 From: kevin.benton at amd.com (Benton, Kevin) Date: Thu, 23 Feb 2006 16:07:11 -0800 Subject: Selenium is awesome as a browser-user simulator and it's free! Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A4204AB0DFF@ssvlexmb2.amd.com> For those that are not aware of Selenium, you can get it for free at http://www.openqa.org/. It's a fantastic Open Source tool for those of us who are system administrators and/or developers of web-based applications. Bugzilla fits perfectly into this category. Selenium-IDE is a browser plug-in that can (when the user tells it to) record clicks and keystrokes on web pages. When that set of user actions has been recorded, the user can play it back to reproduce certain activities. Bugzilla developers benefit from this by using a tool that will test application functionality with a single click to start it. Bugzilla administrators will benefit by being able to verify certain types of functionality after a parameter change in Bugzilla. Selenium can run in a server environment or on top of Internet Explorer, Firefox, Mozilla, Safari, OmniWeb, or Camino. It may run under Netscape Navigator, Opera, Konqueror, or Galeon. Feel free to stop on by http://www.openqa.org/ for more information. A demo is included there. To get the full effect, click on Selenium, then Demos (left hand side), then Passing Demo (opens new window). In the top right hand corner, click on All. Watch as Selenium runs three tests. After that, close the new window, and go to Failing Demo, select Walk, then All. Watch Selenium work as it walks a little more slowly through the tests, demonstrating how green means good and that funky red means bad things. The IDE works in pretty much the same way except that it really runs on your browser / system. A number of properly configured Selenium scripts can serve as entrance criteria for any updates you may write for Bugzilla. --- Kevin Benton Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator Personal Computing Systems Group 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 Benton, Kevin > Sent: Thursday, February 23, 2006 11:06 AM > To: developers at bugzilla.org > Subject: Re: prioritizing custom fields development > > > Fr?d?ric Buclin wrote: > > > > >> * administer custom fields via a web interface; > > > > > > > > > This one is definitely what I would like to see asap. I hope > > > 'administer' also means creating and removing fields. > > > > > > I am curious about this one, because it really seems to me like one of > > the lowest priorities. Administration is a rarely done task, typically > > done at configuration time. And since it doesn't support per-project > > custom fields, you don't even do the administration on a per project > > basis. > > > > Perhaps I am wrong here, but it seems like the priority should be about > > functionality for the operation and use of custom fields. Heck, I don't > > mind making changes in a configuration file or simple perl code changes > > to administer custom fields. > > > > Is the issue that you are targeting a system where the bugzilla > > administrator does not have command line access? > > In my mind, it's a usability issue. While it's true that we're technical > enough to do this kind of thing as developers, I don't think it's fair to > expect Bugzilla administrators to 1) have to manually edit configurations, > and 2) know enough to be able to figure out how to fix it when they > screwed up their installation due to syntax errors. A web-based UI helps > prevent that kind of mistake, and greatly improves usability. Not to > mention, doing that also makes it a lot easier for administrators of large > / multiple installations to manage customizations (if done properly). > > Having a web-based UI also makes it a lot easier to train other users how > to maintain their own custom fields. It's true that here, some of the > users don't have access to the command prompt and are not able to modify > configuration files. Frankly, I don't want to give someone the > opportunity to cause critical problems with an installation they don't > have ultimate operational responsibility for. > > So, having said all that, in my mind, doing this kind of update from a > web-based UI isn't optional, it's a requirement. > > --- > Kevin Benton > Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator > Personal Computing Systems Group > 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. > > > - > To view or change your list settings, click here: > From justdave at bugzilla.org Fri Feb 24 03:17:22 2006 From: justdave at bugzilla.org (David Miller) Date: Thu, 23 Feb 2006 22:17:22 -0500 Subject: Selenium is awesome as a browser-user simulator and it's free! In-Reply-To: <6F7DA19D05F3CF40B890C7CA2DB13A4204AB0DFF@ssvlexmb2.amd.com> References: <6F7DA19D05F3CF40B890C7CA2DB13A4204AB0DFF@ssvlexmb2.amd.com> Message-ID: <43FE7AC2.3070109@bugzilla.org> Benton, Kevin wrote on 2/23/06 7:07 PM: > For those that are not aware of Selenium Yep, we have it installed on landfill and our QA guys use it extensively before we ship new versions these days. :) -- 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 CDaniell at realm.com Tue Feb 28 18:34:09 2006 From: CDaniell at realm.com (Casey Daniell) Date: Tue, 28 Feb 2006 12:34:09 -0600 Subject: Setting email Return-Path Message-ID: <251BDD141C490545813A304E835228760133B7@dalmail01.realpulse.com> Ok, I have bugzilla set up and running almost completely as needed however, emails the server generated have the Return-Path set as nobody@ How do I set this return path to be something valid? Casey B. Daniell Realm Business Solutions, Inc. 13727 Noel Rd. Suite 800 Dallas, TX 75240 cdaniell at realm.com > O:(469) 791-1065 H:(972) 980-4156 C:(512) 589-3667 REGISTER NOW for the FUSION User Conference June 12-14 in beautiful Miami, Florida. REGISTER NOW and SAVE! Early bird registration discounts are currently available. Visit www.realm.com/company/fusion.html NOTICE: This communication contains information which is confidential to Realm Business Solutions, Inc. or its subsidiary ("Realm"). If you are not the intended recipient of this communication, please delete and destroy all copies. If you are the intended recipient of this communication, you should not copy, disclose or distribute this communication without Realm's authority. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be Realm's views. Except as required by law, Realm does not represent, warrant or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, harmful code, interception or interference. -------------- next part -------------- An HTML attachment was scrubbed... URL: From CDaniell at realm.com Tue Feb 28 19:44:21 2006 From: CDaniell at realm.com (Casey Daniell) Date: Tue, 28 Feb 2006 13:44:21 -0600 Subject: Setting email Return-Path Message-ID: <251BDD141C490545813A304E835228760133B8@dalmail01.realpulse.com> Never mind, I finally figured it out. I had to hack, 1. Token.pm 2. globals.pl 3. processmail 4. whineatnews.pl And add a -f at the end of the sendmail call. Sorry about the spam. Casey ________________________________ From: developers-owner at bugzilla.org [mailto:developers-owner at bugzilla.org] On Behalf Of Casey Daniell Sent: Tuesday, February 28, 2006 12:34 PM To: 'developers at bugzilla.org' Subject: Setting email Return-Path Ok, I have bugzilla set up and running almost completely as needed however, emails the server generated have the Return-Path set as nobody@ How do I set this return path to be something valid? Casey B. Daniell Realm Business Solutions, Inc. 13727 Noel Rd. Suite 800 Dallas, TX 75240 cdaniell at realm.com > O:(469) 791-1065 H:(972) 980-4156 C:(512) 589-3667 REGISTER NOW for the FUSION User Conference June 12-14 in beautiful Miami, Florida. REGISTER NOW and SAVE! Early bird registration discounts are currently available. Visit www.realm.com/company/fusion.html NOTICE: This communication contains information which is confidential to Realm Business Solutions, Inc. or its subsidiary ("Realm"). If you are not the intended recipient of this communication, please delete and destroy all copies. If you are the intended recipient of this communication, you should not copy, disclose or distribute this communication without Realm's authority. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be Realm's views. Except as required by law, Realm does not represent, warrant or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, harmful code, interception or interference. REGISTER NOW for the FUSION User Conference June 12-14 in beautiful Miami, Florida. REGISTER NOW and SAVE! Early bird registration discounts are currently available. Visit www.realm.com/company/fusion.html NOTICE: This communication contains information which is confidential to Realm Business Solutions, Inc. or its subsidiary ("Realm"). If you are not the intended recipient of this communication, please delete and destroy all copies. If you are the intended recipient of this communication, you should not copy, disclose or distribute this communication without Realm's authority. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be Realm's views. Except as required by law, Realm does not represent, warrant or guarantee that the integrity of this communication has been maintained nor that the communication is free of errors, harmful code, interception or interference. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkanat at bugzilla.org Tue Feb 28 20:14:35 2006 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 28 Feb 2006 12:14:35 -0800 Subject: Setting email Return-Path In-Reply-To: <251BDD141C490545813A304E835228760133B7@dalmail01.realpulse.com> References: <251BDD141C490545813A304E835228760133B7@dalmail01.realpulse.com> Message-ID: <1141157676.3504.8.camel@es-lappy> On Tue, 2006-02-28 at 12:34 -0600, Casey Daniell wrote: > Ok, I have bugzilla set up and running almost completely as needed > however, emails the server generated have the Return-Path set as > nobody@ > > How do I set this return path to be something valid? Hey Casey. That's more of a support question. For support, see: http://www.bugzilla.org/support/ -Max -- http://www.everythingsolved.com/ Everything Solved: Competent, Friendly Bugzilla and Linux Services From myk at mozilla.org Tue Feb 28 20:58:32 2006 From: myk at mozilla.org (Myk Melez) Date: Tue, 28 Feb 2006 12:58:32 -0800 Subject: prioritizing custom fields development In-Reply-To: <43FCF29C.9080005@mozilla.org> References: <43FCF29C.9080005@mozilla.org> Message-ID: <4404B978.7060906@mozilla.org> Thanks all for your feedback. Based on what you've told me and my own sense of the project, I've roughly prioritized tasks into the following list, where the tasks appearing earlier are higher priority: 1. custom fields appearance on search, bug list, change multiple bugs, long list, and printable pages; 2. ability to list and delete custom fields via the command-line; 3. boolean fields; 4. web interface for managing custom fields; 5. ability to position fields at arbitrary places on the edit bug page; 6. type-constrained plain-text fields; 7. single-select fields; 8. user fields; 9. bug fields; 10. multi-select fields; 11. date fields; 12. ability to restrict fields to specific product/component combinations; 13. ability to restrict fields to specific user groups; 14. multi-user fields; 15. multi-bug fields. Note that this doesn't preclude anyone from implementing these features out-of-order. In fact, I encourage you to tackle any or all of these tasks, since on my own it'll take a long time to get all of this done, and Bugzilla will be better off if we get this work done sooner. -myk From gerv at mozilla.org Tue Feb 28 22:02:01 2006 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 28 Feb 2006 22:02:01 +0000 Subject: prioritizing custom fields development In-Reply-To: <4404B978.7060906@mozilla.org> References: <43FCF29C.9080005@mozilla.org> <4404B978.7060906@mozilla.org> Message-ID: <4404C859.6020007@mozilla.org> The following should be taken in the knowledge that I am unlikely to ever be able to contribute to this development. Myk Melez wrote: > 1. custom fields appearance on search, bug list, change multiple > bugs, long list, and printable pages; > 2. ability to list and delete custom fields via the command-line; > 3. boolean fields; > 4. web interface for managing custom fields; As others have said, this seems too high to me. Custom field management is a rare operation. Would a command-line client really be so troublesome? > 5. ability to position fields at arbitrary places on the edit > bug page; Presumably by this you mean "ability to add code to a template such that Bugzilla notices a custom field has been specifically placed and doesn't reproduce it in the generic area"? Gerv From myk at mozilla.org Tue Feb 28 22:33:31 2006 From: myk at mozilla.org (Myk Melez) Date: Tue, 28 Feb 2006 14:33:31 -0800 Subject: prioritizing custom fields development In-Reply-To: <4404C859.6020007@mozilla.org> References: <43FCF29C.9080005@mozilla.org> <4404B978.7060906@mozilla.org> <4404C859.6020007@mozilla.org> Message-ID: <4404CFBB.6060608@mozilla.org> Gervase Markham wrote: > Myk Melez wrote: > >> 4. web interface for managing custom fields; >> > > As others have said, this seems too high to me. Custom field management is a rare operation. Would a command-line client really be so troublesome? > Operations like adding, listing, and deleting custom fields are likely to be relatively easy to implement in a command-line tool (and hence are prioritized more highly), but a good UI for making modifications to existing fields seems relatively complicated to implement on the command line. This item might be better described as the prioritization of the ability to edit custom fields, for which a web interface is the path of least resistance to a usable interface. Of course, you might still consider this functionality to be prioritized too highly. >> 5. ability to position fields at arbitrary places on the edit >> bug page; >> > > Presumably by this you mean "ability to add code to a template such that Bugzilla notices a custom field has been specifically placed and doesn't reproduce it in the generic area"? > Most likely that's what I mean. Arbitrary positioning itself will certainly involve adding code to templates, and telling Bugzilla which fields are arbitrarily positioned, so that it doesn't reproduce them in the generic area, will probably also involve template code (perhaps the two can be integrated), although there are other possibilities (f.e. listing arbitrarily positioned fields in a site parameter), and I haven't thought through the problem yet in detail, so I can't say for sure. -myk -------------- next part -------------- An HTML attachment was scrubbed... URL: