Subscribe to this blog and receive notifications of new posts by email.
Join 2,122 other subscribers
Trying to keep the commit candidates under control. Every time I look up the list gets bigger.
Peter Westwood and Denis de Bernardy are discussing. Toggle Comments
Yeah, I did some cleaning up and testing.
It would help if they got committed or rejected with feedback faster, btw.
trac wouldn’t be so overcluttered with tickets if commit candidates got looked into on the spot. and contributors would have more incentive to maintain their patches. as things are, a valid ticket can easily be ignored for a year from lack of traction, and that is quite discouraging for contributors.
some oss projects (pgsql) have a bug-to-feedback process of under 48 hours. that helps *a lot* to get the community involved. especially, as is the case of pgsql, when it usually means bug-to-fix.
We do try to respond as fast as possible. But responding is not a short task and good quality patch review takes time.
You have to make sure that the bug is being fixed in the correct way.
Often lack of detail in the ticket will make this take longer
← Standardizing and shortening the WP secu…
Deprecated wp_specialchars() in favor of… →