Re: Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion:
| From: | Jani Taskinen | Date: | Fri, 08 Feb 2002 13:04:10 +0000 |
| Subject: | Re: Separating Bug report emails to own list.. Re: Re[3]: [PHP-DEV] Suggestion: | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-79706@lists.php.net to get a copy of this message | ||
Do you filter these? :)
I didn't do that before, but now that I am doing it, it makes
following php-dev@ a LOT easier.
--Jani
On Fri, 8 Feb 2002, Andi Gutmans wrote:
>-1 :) For the reasons mentioned every six months when this matter is raised.
>
>At 02:49 PM 2/8/2002 +0200, Zeev Suraski wrote:
>>+1
>>
>>At 04:06 AM 2/8/2002, Jani Taskinen wrote:
>>
>>> Just wanted to let you know that I'm doing exactly that.
>>> Filtering that annoying noise to other folder. :)
>>> Which I unfortunately don't have time to read atm.
>>>
>>> And I actually have turned my coat on this issue and I'm
>>> in favor for separating the bug emails to own list.
>>>
>>> Two good reasons:
>>> - People who don't want to read them filter them out anyway
>>> - It makes php-dev easier to follow
>>> - The php-dev@ archive (e.g. in web) becomes easier to browse
>>> and search for discussions
>>>
>>> The php-bugs@ list should be a read-only list where anyone
>>> with cvs account should be subscribed (by default).
>>> It being read-only forces any replies to be send to php-dev@
>>> where more intense discussion over the issues in the reports
>>> should take place anyway.
>>>
>>> --Jani
>>>
>>>
>>>On Thu, 7 Feb 2002, l0t3k wrote:
>>>
>>> >Daniel,
>>> > we've had that conversation before, and the consensus then (which makes
>>> >sense), is that part of the price of being a developer is ensuring that
>>> bugs
>>> >are resolved in a timely manner. to split the list would make it less
>>> likely
>>> >that a bug gets reviewed (after all its more sexy to create features
>>> than to
>>> >debug them). how that works in actual practice, i dont know. i review bug
>>> >reports periodically, but i suppose others can just as well filter them
>>> >out...
>>> >
>>> >Daniel Lorch <daniel@lorch.cc> wrote in message
>>> >news:1236522398.20020207182911@lorch.cc...
>>> >> Hi,
>>> >>
>>> >> Maybe a solution would be to split PHP-Dev into PHP-Bugs and keep
>>> >> PHP-Dev for *real* topics such as case sensitivity/PHP5 and other
>>> >> questions which are about PHP language design. This would keep the
>>> >> "noise" out of here. Comments?
>>> >>
>>> >> -- Daniel Lorch
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>>--
>>>PHP Development Mailing List <http://www.php.net/>
>>>To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>>--
>>PHP Development Mailing List <http://www.php.net/>
>>To unsubscribe, visit: http://www.php.net/unsub.php
>