Les, Charlie, devinfo list members,
Sorry for this continuing rant on policy.
---
From: Paul Miller [mailto:[EMAIL PROTECTED]]
And I thought it is the right/responsibility of the developer to
accept/reject/ignore any and all suggestions from the community with
priority given to
From: Paul Miller [mailto:[EMAIL PROTECTED]]
And I thought it is the right/responsibility of the developer to
accept/reject/ignore any and all suggestions from the community with
priority given to developing good code. Do you think Linus
incorporates every patch or even responds to all
From: Charlie Brady [EMAIL PROTECTED]
However, it seems to make good sense to cc devinfo with bug reports,
especially on something that is alpha.
On no account cc devinfo. If you do that, every followup on devinfo will
open a new ticket in our bug tracking system (as we've said
it would stop this
endless spam on devinfo ;-)
All the best,
Julian Luton
-Original Message-
From: Les Mikesell [mailto:[EMAIL PROTECTED]]
Sent: 13 August 2002 05:32
To: Charlie Brady; Greg J. Zartman
Cc: Devinfo
Subject: Re: [e-smith-devinfo] Reporting bugs (was Re: bug posting? [was
[5.6
. Zartman
Cc: Devinfo
Subject: Re: [e-smith-devinfo] Reporting bugs (was Re: bug posting? [was
[5.6] unable to login to)
From: Charlie Brady [EMAIL PROTECTED]
However, it seems to make good sense to cc devinfo with bug reports,
especially on something that is alpha
; Greg J. Zartman
Cc: Devinfo
Subject: Re: [e-smith-devinfo] Reporting bugs (was Re: bug posting? [was
[5.6] unable to login to)
From: Charlie Brady [EMAIL PROTECTED]
However, it seems to make good sense to cc devinfo with bug reports,
especially on something that is alpha.
On no account cc
How do all the other beta testers avoid wasting their time dealing with the
same bug if they aren't discussed publicly? I thought the point of open
source development was to share this sort of thing.
That was the point of my original post on this topic. Correct me if I'm
wrong here
From: Charlie Brady [EMAIL PROTECTED]
However, it seems to make good sense to cc devinfo with bug reports,
especially on something that is alpha.
On no account cc devinfo. If you do that, every followup on devinfo will
open a new ticket in our bug tracking system (as we've said here
