I’m inaugurating a new trac keyword, “…

I’m inaugurating a new tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. keyword, “bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.-hunt”, and the bug hunt report, in order to keep track of of tickets that get posted/could get posted in this blogblog (versus network, site)’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, i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. 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:

Open WP bugs, props Hakre

Thus, I’d like to revisit two of my last post’s tickets:

  1. #10779, on optimizing our unzip method. DD32 committed the fix, but marked it as still needing testing. Here’s how. Related ticketticket Created for both bug reports and feature development on the bug tracker. #10403 is still pending, but I feel it’s extremely minor compared to #10779.
  2. #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 patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., 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.

#bugs, #featured-bugs