[wp-hackers] Fixing Bugs

jacobsantos at branson.com jacobsantos at branson.com
Mon Aug 27 20:00:44 GMT 2007

I like this idea, but I think it has more to do with users submitting 
patches for bugs. Which I think is what the bug hunts are all about, 
finding and submitting patches.

I also think that reasons should be given when closing as invalid or 
wontfix. It is good bug handling in my opinion and something that won't 
annoy those who submit bugs. Some bugs marked as won't fix or invalid 
mean that the bug is external to the application that can't be fixed 
easily. However, making it clear what the developers intention was would 
go a long way.

There will never be any release in any application where everything 
works. However, fixing what bugs we have now would be an awesome idea! 
Documenting the code should go along with this idea.

Jacob Santos

Geoffrey Sneddon wrote:
> The number in bugs in WP has grown steadily over several years, yet 
> the number of unfixed ones increasing quicker still. We need a release 
> that is stable. We need a release where everything _works_. Can we 
> have one release which includes _nothing_ but bug fixes. There are 409 
> open bugs according to trac (and I expect there are others marked as 
> wontfix/invalid without reason). There are some massively annoying 
> bugs for users, not least things like being unable to use IRIs in 
> sanitised content (#4570, target 2.4).
> - Geoffrey Sneddon
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list