"Jon Stevens" <[EMAIL PROTECTED]> wrote:
> Here is another point: What if one of you goes on vacation and forgets to
> make the switch to assign it to someone else? The *only* thing that will
> notify the list of the bug is the weekly email. What if it is a security
> hole bug report and the weekly email isn't set to go out for another 6 days?
> I understand that you get a copy of all of the emails, but that is still a
> single point of failure if you get behind a couple days on your own emails
> (or don't read one of them closely enough).
Nope... Because I check the web...
>> How isn't it adequate? (Sometimes I wish not to do shit, like the scripts to
>> send automatic email about bugs, so that people will not start complaining)
>
> See above *.
>
> p.s. I would be interested to see over time after sending the emails to this
> list when they get submitted, if random developers volunteer to fix bugs
> that come in.
Ok, propose a vote, then...
> p.p.s. Paulo's suggestion still defeats the point I'm trying to get across.
> For example, I have always preferred CVS commit emails going to the -dev
> list because it causes more people to look at the commits and comment on
> them (peer review is one of our selling points, lets capitalize on that). If
> bugs go to their own list, then chances are most people aren't going to see
> them because they either don't know about the bugs list or are to lazy to
> subscribe.
And again, so many projects have a separate -cvs mailing list... Not all
project are "Jon-ized", if you want to change them, submit a request for
vote.
(on the bug issue, I don't give a damn about where those emails end up to, I
get notified anyhow)
Pier
