Dev Chat Plan

This week we wanted to declare betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.. But things are still being committed that are not just 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. fixes! And things with patches are still waiting for review! And half the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team is out of town today! What to do?!

  • Koop more or less wrapped up theme previewer last night.
  • Before we do another check on where our planned features stand, I’d like the queue of has-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. tickets to be cleared. Any/all commit-level developers in chat today should divvy up the tickets for the commit/puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) roll call until there are no more patches waiting in the 3.4 milestone. Tomorrow we can do a check in of the planned features and punt the things that just didn’t makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it in time despite valiant efforts. Maybe Friday we could call beta, or that could be Monday (not sure when Ryan gets back). Nacin is driving in dev chat today.

#3-4, #agenda, #dev-chat