PHP 6 Bug Database summary - http://bugs.php.net/
Num Status Summary (108 total -- which includes 47 feature requests)
===[Apache related]===
47061 Open User not logged under Apache
On Jan 25, 2010, at 1:30 AM, internals@lists.php.net wrote:
PHP 5 Bug Database summary - http://bugs.php.net/
Num Status Summary (1595 total -- which includes 1036 feature requests)
Curious, does anybody use or read these? These emails have probably outgrown
their use, so let's
I usually look at the count of issues and compare to the previous week.
Then after a quick eye-diff, I check which ones were fixed.
I think I'm the only one that does that... =)
Your changed would be very well accepted, specially by me.
Cheers,
On Mon, Jan 25, 2010 at 2:26 PM, Philip Olson
Hello,
Those are some good ideas, another thing I think might help get some bugs
closed is a way to detect which bugs have patches/diffs attached or
included. Honestly I stopped submitting patches when I noticed they rot for
months :)
-Chris
On Jan 25, 2010 9:37 AM, Guilherme Blanco
This isn't about server costs. It is about choosing the right tool for
the right part of the job. A Javascript library for the client-side
frontend, PHP for the server-side frontend, C/C++ for your middle-layer
and an appropriate datastore behind it all and you can build amazing
things with
