Hello Jacob
Take a look at http://pinba.org/ . While this is probably not exactly (or
may be even not at all) the thing you asked for, it is definitely
interesting. It allows for some profiling *right on production. *There are
certain things that you only experience under heavy load, and this
Howdy dear Internals
For a while I have been just stalking the bugs database[1], and I
would love if we could some more focus on closing bugs. I'm not saying
the job we do (my self included) is not being done well enough, but
currently we have over 4.1k and a lot of those are old feature
Am 27.12.2014 um 16:01 schrieb Kalle Sommer Nielsen:
bugs going as far back as to PHP4.
Bug reports for PHP version that are not supported anymore [1]
should IMHO be bulk-closed. The message should ask to reopen if
the bug is reproducible with a supported version of PHP. IMHO :)
--
[1]
On 27 December 2014 15:06:42 GMT, Sebastian Bergmann sebast...@php.net wrote:
Am 27.12.2014 um 16:01 schrieb Kalle Sommer Nielsen:
bugs going as far back as to PHP4.
Bug reports for PHP version that are not supported anymore [1]
should IMHO be bulk-closed. The message should ask to reopen if
Hello,
yeah, I had very similiar idea (Symfony inspired me [1]). I also think
that 4252 open bugs is quite too much and this number doesn't really
reflect actual ammount of work to do. As you said, many bugs are
critically outdated, some of them are probably duplicates and so on...
I don't
Hey all,
On 27 Dec 2014, at 18:34, Rowan Collins rowan.coll...@gmail.com wrote:
On 27 December 2014 15:06:42 GMT, Sebastian Bergmann sebast...@php.net
wrote:
Am 27.12.2014 um 16:01 schrieb Kalle Sommer Nielsen:
bugs going as far back as to PHP4.
Bug reports for PHP version that are
Hi Andrea
2014-12-27 20:08 GMT+01:00 Andrea Faulds a...@ajf.me:
As Rowan says, this would be a problem. Rather than just closing all bugs
that are of a certain age, we should just go through all the open bugs one by
one. 4000 open bugs is a lot, sure, but with a few people working at it I
I for one are against just closing old bugs without at least a review
too. If we can have 5-10 developers (from any part of the community
with a @php.net account) to look over a few bugs a day, then we can
quickly bring that number down.
I'll gladly enlist here. I've gone through bugs in the
One of the biggest issues I have found with the PHP bug tracker is the
inability to filter on tickets and find the low hanging fruit based on a
label or a priority. I realise the advanced search allows you to find
based on package however this still is not enough. I am quite new to the
Hey Jacob,
On 28 Dec 2014, at 01:48, Jacob Bednarz jacob.bedn...@gmail.com wrote:
One of the biggest issues I have found with the PHP bug tracker is the
inability to filter on tickets and find the low hanging fruit based on a
label or a priority.
What do you mean by this? What’s a
What do you mean by this? What’s a priority? You can sort by votes, you
can filter by status, I’m not sure what you mean with “on a label”.
Could you please elaborate? Thanks.
Sure - A label can be anything that is used to allow finer searching of
issues. For example, I don't have a specific
Hey Jacob,
On 28 Dec 2014, at 03:09, Jacob Bednarz jacob.bedn...@gmail.com wrote:
What do you mean by this? What’s a priority? You can sort by votes, you can
filter by status, I’m not sure what you mean with “on a label”.
Could you please elaborate? Thanks.
Sure - A label can be
Well, there isn’t such a label because labels have to be created by
people going through and adding that label to bugs. So someone has to look
through 4000 bugs.
This definitely could be an issue for existing bugs but if it's available
when someone creates a bug they could fill it out at
Hi again,
On 28 Dec 2014, at 03:11, Andrea Faulds a...@ajf.me wrote:
On 28 Dec 2014, at 03:09, Jacob Bednarz jacob.bedn...@gmail.com wrote:
What do you mean by this? What’s a priority? You can sort by votes, you can
filter by status, I’m not sure what you mean with “on a label”.
Could
- Triaging bugs, issues and cleaning up bug reports
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Le 27/12/2014 16:06, Sebastian Bergmann a écrit :
Am 27.12.2014 um 16:01 schrieb Kalle Sommer Nielsen:
bugs going as far back as to PHP4.
Bug reports for PHP version that are not supported anymore [1]
should IMHO be bulk-closed. The message should ask to reopen if
the bug is reproducible
Hello guys,
the work is going, number of open bugs slowly decreases. Meanwhile, I
have sent a reminder[1] to all manual translations MLs, asking doc
contributors for closing pending bugs. In best scenario, this should
result in about next 40 bugs closed, as they are really easy to fix.
One
17 matches
Mail list logo
