This week in 4.3: Jul 27 – Aug 2

This is the jump-start post for the twelfth week of the WordPress 4.3 release cycle.

We’re in the final stages of the release, by Wednesday we want to be able to present our Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). to the community. A release candidate (RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).) is a 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. version with potential to be a final product, which is ready to release unless significant bugs emerge. In this stage all product features have been designed, coded, and tested through a few beta cycles with no known showstopper-class 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..

Priority Tickets this week:

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Meetings this week:

#4-3, #jump-starts