During yesterday’s meeting we decided on a daily…

During yesterday’s meeting, we decided on a daily 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. scrub starting today (June 28) until July 10 (weekdays, and skipping July 4), at 19:00 UTC, an hour before our typical Wednesday meetings. This is a pilot; I hope to carry this idea through the dev cycle.

Additionally, there will be a meeting on Friday, June 29 at 20:00 UTC to discuss automated testing, with @maxcutler, Kurt Payne, and others.

We expect the dev chat on July 11 to be the session where we plan the features and scope for WordPress 3.5.

For the next two weeks, we’d like to put a focus on housekeeping — focusing on things that need early attention for 3.5, things that often get missed like triaging TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets, and acting on tickets with patches ready for review/commit/feedback. The daily bug scrubs will try to pull all of it together. Let’s see if we can bring down the size of the Awaiting Review report, start hammering on the 3.5 report, and sifting through Future Release.

#dev-chat, #summary