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
Hello Les,
mardi 13 août 2002 à 15:32:18, you wrote :
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
Dear All,
Just a suggestion - how hard would it be to have your bug track system
send devinfo a daily or weekly digest of every new bug with 5.6 in the
subject line.
That way we could keep a track on what is causing you guys problems and
what isn't. We might even be able to help! At least it
Another suggestion. Perhaps a separate beta mailing list. This stuff
clearly does not fit the purpose of the devinfo mailing list, but much
of the audience is interested. [EMAIL PROTECTED] is likely to get
overwhelmed with non-bugs.
I have run many, many betas in my career and found a mailing
John
I tend to disagree.
Considering 5.6 is actually alpha/beta release, it is still under
development!
I can understand reporting a bug on a stable release to [EMAIL PROTECTED]
but this shouldn't be the case with betas. I don't even see how you can
call a problem on a development
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
