Are there any plans to move away from Bugzilla for issue tracking? I have been lurking around https://bugzilla.lustre.org for several months now and I still find it very hard to use, do others have the same feeling? or is there a setting or a preferred filter to see all the new bugs in 1.8 series? TIA
On Wed, 2009-08-05 at 06:22 -0400, Mag Gam wrote:> Are there any plans to move away from Bugzilla for issue tracking?I am not aware of any plans in this regard. I personally have not been introduced to a bug tracker that is as complete as bugzilla for what we need to do and I am quite familiar with and involved in many open source projects and their related bug trackers.> I > have been lurking around https://bugzilla.lustre.org for several > months now and I still find it very hard to use, do others have the > same feeling?Not at all, on my part anyway. But I am very familiar with bugzilla. I find using other projects'' (i.e. gnome, freedesktop, etc.) bugzillas just as easy to use. It is a tool you have to learn to use effectively though.> or is there a setting or a preferred filter to see all > the new bugs in 1.8 series?Find and follow the release trackers. Release tracking bugs usually have an alias of the form tracking-xyz where x, y and z are the release digits. i.e. tracking-181. I believe this has been discussed more than once on this list though, so the archives might be useful here if you need any more info. b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20090805/7aab0e1e/attachment.bin
On Aug 05, 2009 09:51 -0400, Brian J. Murrell wrote:> On Wed, 2009-08-05 at 06:22 -0400, Mag Gam wrote: > > or is there a setting or a preferred filter to see all > > the new bugs in 1.8 series? > > Find and follow the release trackers. Release tracking bugs usually > have an alias of the form tracking-xyz where x, y and z are the release > digits. i.e. tracking-181. I believe this has been discussed more than > once on this list though, so the archives might be useful here if you > need any more info.What brian meant was "181-tracking" or "182-tracking", etc. These can be used in place of bug numbers in the "quick search" fields at the top/bottom of every bugzilla page. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc.
On Wed, 2009-08-05 at 13:16 -0600, Andreas Dilger wrote:> > What brian meant was "181-tracking" or "182-tracking", etc.Oops. Yes, indeed. A little lysdexic this morning I guess. Sorry for the mis-information. b. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20090805/8c9828ed/attachment.bin
Mag Gam wrote:> Are there any plans to move away from Bugzilla for issue tracking? I > have been lurking around https://*bugzilla.lustre.org for several > months now and I still find it very hard to use, do others have the > same feeling? or is there a setting or a preferred filter to see all > the new bugs in 1.8 series?I just want to voice for my support for Bugzilla. I think it has been really great to use. Here are LLNL, we have probably opened hundreds of Lustre "issues" (bugs, trackers, future-improvement requests, etc.), and bugzilla has been a pleasure to use. I have been forced to use some other issue tracking systems in the past that have made bugzilla seem a breath of fresh air in comparison. Chris
On Aug 5, 2009, at 2:53 PM, Christopher J. Morrone wrote:> Mag Gam wrote: >> Are there any plans to move away from Bugzilla for issue tracking? I >> have been lurking around https://*bugzilla.lustre.org for several >> months now and I still find it very hard to use, do others have the >> same feeling? or is there a setting or a preferred filter to see all >> the new bugs in 1.8 series? > > I just want to voice for my support for Bugzilla. I think it has been > really great to use. Here are LLNL, we have probably opened > hundreds of > Lustre "issues" (bugs, trackers, future-improvement requests, etc.), > and bugzilla has been a pleasure to use.I''ll second that. While we don''t submit bugs ourselves (we receive Lustre support through a third party), we do use it in other ways, and it''s been a fantastic resource. Whenever I''m researching a Lustre problem, the very first thing I do is search bugzilla - *not* Google! Plugging in the output from an LBUG into a Bugzilla search turns up a relevant bug more often than not. Additionally, some information on what other sites are doing - especially large sites such as LLNL and ORNL, and tools that they use, can be found by digging around in Bugzilla. See, for example, bz 20165, submitted by Jim Garlick @ LLNL, which has scripts for integrating heartbeat support into Lustre. While we''re not using the failover bits, I did pull out ldev from Jim''s patch, which is a fantastic tool that I wish I had taken the time to write myself months ago (thanks, Jim!) However, Bugzilla''s usefulness as a support tool for the Lustre community is somewhat hindered by the fact that some customers request that their support tickets be made private. They certainly have the right to do that, and I''m not knocking Sun or those customers for doing so. However, the data contained in those tickets can be rather useful to the community and it would be helpful to have as many tickets as possible be publicly-accessible. It''s very frustrating to run a Bugzilla search, find a matching bug, only to be presented with a "not authorized" message when clicking on the bug''s link. This happened when searching for bugs related to the corruption introduced into Lustre 1.6.7. I believe we were the second site to report the corruption. The bug from the first site was marked private, which was a bit frustrating when we were trying to analyze the problem before requesting support, especially on a weekend when support isn''t always available. Sun has assured us that they are working on technical and procedural improvements to ensure that public versions of private bugs containing relevant technical data are made available to everyone. Until that happens, I''m putting out a call to those of you who do submit private bugs to either make them public in the first place, or strip out any private information before submitting them to Sun. If there''s proprietary customer data contained in the bug you submit, that''s one thing. But if you''re embarrassed about pilot error, well, I''ll be the first to admit that I''ve committed some myself! Thanks, j> > > I have been forced to use some other issue tracking systems in the > past > that have made bugzilla seem a breath of fresh air in comparison. > > Chris > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss-- Jason Rappleye System Administrator NASA Advanced Supercomputing Division NASA Ames Research Center Moffett Field, CA 94035 jason.rappleye at nasa.gov