A minor release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. of WordPress generally addresses between 20 and 35 issues, with a focus on those that arise from the new features and fixes in the current major release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope., which is 5.2.
Here’s the schedule the release team (@marybaum, @audrasjb @chanthaboune and @justinahinon) published a week ago.
The current schedule shows final release for 5.2.2 on Wednesday, June 12, 2019, 7:00 PM CDT.
Proposed agenda for this minor release cycle:
Already complete:
Going forward:
During devchat last week the active participants pointed out there are just twelve tickets milestoned for 5.2.2.
Meanwhile, almost 100 tickets for 5.3 already have patches and are a good fit for a minor release.
So let’s move 15-20 of those to 5.2.2 and take a little time to issue a more robust release. (There was a public discussion on this blog (versus network, site) as well.)
Here’s a new proposed schedule for this week:
We’ll use Monday to triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. those 5.3 tickets for the best candidates to move to this release. If you have favorites, let us (the release squad) know Saturday and Sunday, and we’ll see you Monday!
Then, based on the outcome of that scrub, we can use Wednesday’s devchat to finalize dates for RC2 and release.
#5-2-2
