Good news, everyone! WordPress 5.1 is on schedule, and progressing nicely. At the time of writing this post, we have 123 open tickets milestoned for WordPress 5.1, down from nearly 500 a week ago. Thank you to everyone who’s helped triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. these tickets! 💖
To keep things running smoothly as we head towards the Release 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). and WordPress 5.1, I have some intermediate targets that I’d like us to aim for.
Beta 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. 2: January 21, 2019
There’s still a moderate amount of ticket Created for both bug reports and feature development on the bug tracker. triage to do, including working through the 87 tickets reported against
trunk that haven’t been milestoned. Many of these are reported against the wrong version, but they do need to be triaged prior to beta 2.
After beta 2 is released, any bug 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. reports against versions prior to 5.1 will be move to the 5.2 or Future Release milestones.
Beta 3: January 29, 2019
This is the soft string freeze release. All string changes (except for the About page) will be moved to the 5.2 milestone.
Release Candidate 1: February 7, 2019
There should be no open tickets in the 5.1 milestone by RC1, apart from release-related tasks.
5.1 will be branched with RC1, and work can begin in
trunk on WordPress 5.2. As we’re back to standard commit review practice, any WordPress 5.1 fixes will need to be reviewed by two committers before porting to the
5.1 branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
WordPress 5.1: February 21, 2019