I’m inaugurating a new trac keyword, “bug-hunt”, and the bug hunt report, in order to keep track of of tickets that get posted/could get posted in this blog’s “bug hunt” posts.
Updated: I’m inaugurating a new trac keyword, “featured”, and the featured bugs report, in order to keep track of of tickets that get posted/could get posted in this blog’s “featured bugs” posts.
I’ll be tagging more tickets in due course. You’re most welcome to mark additional tickets as such, if you feel they qualify.
For information, I try to stick to batches of tickets that loosely interfere or interact with one another. The batch of tickets should then meet the two or more of following criteria:
- It is annoying when you run into the issue
- It underscores an architectural problem
- Fixing it can lead to performance optimizations
Areas I plan to highlight in the future include: UUIDs, i18n post slugs, permalinks, rewrite rules, cache, private posts.
Btw, I’d like to stress that the point in these blog posts is try to reverse the WP bug trend:
Thus, I’d like to revisit two of my last post’s tickets:
- #10779, on optimizing our unzip method. DD32 committed the fix, but marked it as still needing testing. Here’s how. Related ticket #10403 is still pending, but I feel it’s extremely minor compared to #10779.
- #10913, on optimizing the upgrade process, is still a major niggler imo. #10611 will probably seem cosmetic if #10913 gets fixed. Two possible solutions are highlighted in the ticket’s comments. It still needs a patch, and of course testing once one is around.
We need your help on both, and on future tickets that will make it in these posts. Thanks for patching/testing.