Re: [Cooker] ignorance... (bugzilla mail on cooker)
On Fri, 2002-12-20 at 06:30, Warly wrote:
> Nelson Bartley <[EMAIL PROTECTED]> writes:
>
> > On Thu, 2002-12-19 at 19:39, Ben Reser wrote:
> >> On Thu, Dec 19, 2002 at 07:20:33PM +0100, Warly wrote:
> >> > If most of you think bugzilla mail on cooker are useless, I can remove
> >> > them and just shutdown bugzilla. The goal is not to annoy you, is to
> >> > make our job cleare and easier in debugging period.
> >
{...}
> Ok. I think I will try not to send any email that does not contains a
> comments. This is likely to remove all the status change only or think like
> that.
>
> But I may still send mail when the bug is marked as RESOLVED ?
That sounds just about right, sending an email to the list at first
saying there is a new bug, then having a mail on completion. That would
probably be a very good solution indeed.
--
Nelson Bartley <[EMAIL PROTECTED]>
Re: [Cooker] ignorance... (bugzilla mail on cooker)
Warly wrote: ~snip~ Ok. I think I will try not to send any email that does not contains a comments. This is likely to remove all the status change only or think like that. But I may still send mail when the bug is marked as RESOLVED ? hmm, isn't that a "status changed" only email ;) I think it would be good, so that everyone can see that it's no longer an issue. helps create a sense of getting closer to release.
Re: [Cooker] ignorance... (bugzilla mail on cooker)
Nelson Bartley <[EMAIL PROTECTED]> writes: > On Thu, 2002-12-19 at 19:39, Ben Reser wrote: >> On Thu, Dec 19, 2002 at 07:20:33PM +0100, Warly wrote: >> > If most of you think bugzilla mail on cooker are useless, I can remove >> > them and just shutdown bugzilla. The goal is not to annoy you, is to >> > make our job cleare and easier in debugging period. > > I agree completely with Ben about the bugzilla setup. I understand you > position warly on the use of bugzilla, I've had to use similar (though > far simpler) troublshooting tools during beta periods for our OC48 > Packet Over Sonet Cards we were designing at Nortel. The idea though was > to ensure that, as Ben said, the people who need the information get it. > If I'm troubleshooting a problem, which is largely unlikely as I'm no > expert, I only need to be concerned with the problem. If I'm ready to > solve a new one, I need to be able to see what's currently out there to > solve, and pick it up. [...] > The final note is this. You, Warly et Mandrakesoft, are in charge of > this list. Though I appreciate that our concerns (eg the community ) are > being listend to, in the end you make the policy, not us. If you choose > to leave bugzilla as it is, then we will all just have to accept it or > move on. Ok. I think I will try not to send any email that does not contains a comments. This is likely to remove all the status change only or think like that. But I may still send mail when the bug is marked as RESOLVED ? -- Warly
Re: [Cooker] ignorance... (bugzilla mail on cooker)
On Friday 20 December 2002 01:39, Ben Reser wrote: > On Thu, Dec 19, 2002 at 07:20:33PM +0100, Warly wrote: > > If most of you think bugzilla mail on cooker are useless, I can remove > > them and just shutdown bugzilla. The goal is not to annoy you, is to > > make our job cleare and easier in debugging period. > > I don't think the bugzilla mail is entirely useless. But I don't think > we're getting the most use out of bugzilla that we can. I still don't > think sending every single message to the list is a great idea. I > really don't care to see status change messages on some of these bug > reports, or a message for every single attachment that gets uploaded. > This sounds right to me and I think there is a possibility to subscribe to a given bug easily if I am interested ? As the one who reported the bug will get messages anyway I think > This applies to your developers as much as to us contributors. Part of > the point of bugzilla is to filter what bug reports they need to see. > Sending all of that mail to this list totally defeats that. As is since > some people still aren't reporting bugs via bugzilla, they have to read > this list anyway. Which means they are left filtering through bugzilla > emails. At best they can filter them... but I think you see my point. > > > Bugzilla accomplishes the same goal as cooker, that is to say fix > > upcoming mandrake release. However bugzilla keeps history of what > > happen in a far clearer way than grepping tens of megabytes of cooker > > mail folder. > > Agreed... > > > Moreover we, mandrake developers, cannot sustain the bugs posting rate > > in beta period. As a consequence we decided to send mail to cooker so > > that people that usually help a lot in reporting bug and finding > > solutions can help in the same way for bugzilla. > > And my proposal of only posting the new bug reports still allows this to > happen... Yes this would be good. just my 2 cents -- counter.li.org : #296567. machine: 181800 vdr-box : 87 Please dont CC me, since if I have replied I'll watch the tread. Both mails will be filtered to the ML-folder. Thanks
Re: [Cooker] ignorance... (bugzilla mail on cooker)
On Thu, 2002-12-19 at 19:39, Ben Reser wrote: > On Thu, Dec 19, 2002 at 07:20:33PM +0100, Warly wrote: > > If most of you think bugzilla mail on cooker are useless, I can remove > > them and just shutdown bugzilla. The goal is not to annoy you, is to > > make our job cleare and easier in debugging period. I agree completely with Ben about the bugzilla setup. I understand you position warly on the use of bugzilla, I've had to use similar (though far simpler) troublshooting tools during beta periods for our OC48 Packet Over Sonet Cards we were designing at Nortel. The idea though was to ensure that, as Ben said, the people who need the information get it. If I'm troubleshooting a problem, which is largely unlikely as I'm no expert, I only need to be concerned with the problem. If I'm ready to solve a new one, I need to be able to see what's currently out there to solve, and pick it up. The big thing is I don't need to see that someone made a bugzilla entry status change. If an individual is interested in following the various bugzilla issues then they should follow it at bugzilla and not through an email list. I don't want to see bugzilla go at this point, as apparently it is being used, however there must be a better atlernative then how it is currently being handled. The final note is this. You, Warly et Mandrakesoft, are in charge of this list. Though I appreciate that our concerns (eg the community ) are being listend to, in the end you make the policy, not us. If you choose to leave bugzilla as it is, then we will all just have to accept it or move on. (PS: I appologize for the bad spelling... I'm not feeling so well and my spell check is shot) -- Nelson Bartley <[EMAIL PROTECTED]>
Re: [Cooker] ignorance... (bugzilla mail on cooker)
On Thu, Dec 19, 2002 at 07:20:33PM +0100, Warly wrote: > If most of you think bugzilla mail on cooker are useless, I can remove > them and just shutdown bugzilla. The goal is not to annoy you, is to > make our job cleare and easier in debugging period. I don't think the bugzilla mail is entirely useless. But I don't think we're getting the most use out of bugzilla that we can. I still don't think sending every single message to the list is a great idea. I really don't care to see status change messages on some of these bug reports, or a message for every single attachment that gets uploaded. This applies to your developers as much as to us contributors. Part of the point of bugzilla is to filter what bug reports they need to see. Sending all of that mail to this list totally defeats that. As is since some people still aren't reporting bugs via bugzilla, they have to read this list anyway. Which means they are left filtering through bugzilla emails. At best they can filter them... but I think you see my point. > Bugzilla accomplishes the same goal as cooker, that is to say fix > upcoming mandrake release. However bugzilla keeps history of what > happen in a far clearer way than grepping tens of megabytes of cooker > mail folder. Agreed... > Moreover we, mandrake developers, cannot sustain the bugs posting rate > in beta period. As a consequence we decided to send mail to cooker so that > people that usually help a lot in reporting bug and finding solutions can > help in the same way for bugzilla. And my proposal of only posting the new bug reports still allows this to happen... -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org "If you're not making any mistakes, you're flat out not trying hard enough." - Jim Nichols
Re: [Cooker] ignorance... (bugzilla mail on cooker)
Nelson Bartley <[EMAIL PROTECTED]> writes: > Well lets put it this way, I have no reason to post to the list... heck > I can't even follow a thread now that this bugzilla crap is flooding the > list. > > I really like the cooker list, but this bugzilla stuff is useless on the > cooker list. If most of you think bugzilla mail on cooker are useless, I can remove them and just shutdown bugzilla. The goal is not to annoy you, is to make our job cleare and easier in debugging period. Bugzilla accomplishes the same goal as cooker, that is to say fix upcoming mandrake release. However bugzilla keeps history of what happen in a far clearer way than grepping tens of megabytes of cooker mail folder. Moreover we, mandrake developers, cannot sustain the bugs posting rate in beta period. As a consequence we decided to send mail to cooker so that people that usually help a lot in reporting bug and finding solutions can help in the same way for bugzilla. I try to set up a mail interface that make unecessary to go to the web site. If you need more functions to be able to answer or use bugzilla through mail, please ask. -- Warly
