On Sat, 28 Jun 2003, Andi Gutmans wrote:
>At 06:15 PM 28/6/2003 +0200, Sascha Schumann wrote:
>>On Sat, 28 Jun 2003, Andi Gutmans wrote:
>>
>> > It might be a good idea to assign responsibilities to people. For example,
>> > the XML extension author would only get his bug reports and so on.
>>
>>
On Sat, 28 Jun 2003 19:37:54 +0200
Andi Gutmans <[EMAIL PROTECTED]> wrote:
> We should force maintainers to subscribe to their sections :)
This is what I plan for bugs.pear :-)
pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
At 06:15 PM 28/6/2003 +0200, Sascha Schumann wrote:
On Sat, 28 Jun 2003, Andi Gutmans wrote:
> It might be a good idea to assign responsibilities to people. For example,
> the XML extension author would only get his bug reports and so on.
That's the idea behind bugs- mailing lists (also
ac
On Sat, 28 Jun 2003, Andi Gutmans wrote:
> It might be a good idea to assign responsibilities to people. For example,
> the XML extension author would only get his bug reports and so on.
That's the idea behind bugs- mailing lists (also
accessible through nntp). People who are interested
It might be a good idea to assign responsibilities to people. For example,
the XML extension author would only get his bug reports and so on.
Andi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Sat, 28 Jun 2003, Sascha Schumann wrote:
>> But if the summaries contain only screened (== verified) reports,
>> and sent one per category? Better ideas would be appreciated, of course.
>
>Well, I pretty much embrace the idea that reports ought to
>fall through the cracks, if th
> But if the summaries contain only screened (== verified) reports,
> and sent one per category? Better ideas would be appreciated, of course.
Well, I pretty much embrace the idea that reports ought to
fall through the cracks, if they don't bother developers
enough to address t
On Sat, 28 Jun 2003, Sascha Schumann wrote:
>> I think I get now what you're after and I already am thinking
>> of some ways to improve this. This mail has some nice ideas we could
>> adopt:
>
>These points are interesting from my pov as a lazy developer.
>
>(a) make bug report
> I think I get now what you're after and I already am thinking
> of some ways to improve this. This mail has some nice ideas we could
> adopt:
These points are interesting from my pov as a lazy developer.
(a) make bug reports automatically vanish after some time
(elim
On Sat, 28 Jun 2003, Sascha Schumann wrote:
>On Sat, 28 Jun 2003, Jani Taskinen wrote:
>
>>
>> And the point was..? AFAICT, our system works fine.
>> Seemed like the linux dudes are way behind. :)
>
>Count the developers who regularly access the bug db.
>Contrast that number to the
On Sat, 28 Jun 2003, Sascha Schumann wrote:
> On Sat, 28 Jun 2003, Jani Taskinen wrote:
>
> >
> > And the point was..? AFAICT, our system works fine.
> > Seemed like the linux dudes are way behind. :)
>
> Count the developers who regularly access the bug db.
> Contrast that number t
On Sat, 28 Jun 2003, Jani Taskinen wrote:
>
> And the point was..? AFAICT, our system works fine.
> Seemed like the linux dudes are way behind. :)
Count the developers who regularly access the bug db.
Contrast that number to the overall number of C developers.
Notice how the b
And the point was..? AFAICT, our system works fine.
Seemed like the linux dudes are way behind. :)
--Jani
On Sat, 28 Jun 2003, Sascha Schumann wrote:
>There is a thread on the netdev mailing list right now
>regarding bug databases. Lots of interesting points, some
There is a thread on the netdev mailing list right now
regarding bug databases. Lots of interesting points, some of
them apply to the PHP project as well.
Head of thread:
http://marc.theaimsgroup.com/?l=linux-netdev&m=105669326002116&w=2
- Sascha
-- Forwarded mes
14 matches
Mail list logo
