Release Candidate and Meeting Time Reminder

Schedule

Per the schedule, WordPress 4.5 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). will be released in the hours following Wednesday’s weekly dev meeting, which is at March 23, 2016 at 2100 UTC.

For those on Daylight Saving Time – If you’re on Daylight Saving Time, the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. dev meeting will continue to be an hour later for you this week, with meeting time changing to March 30, 2016 at 2000 UTC next week.

The above time link should give you the correct time and date for your local timezone.

Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.

There are currently 6 tickets in the milestone remaining. We hit the 25 ticketticket Created for both bug reports and feature development on the bug tracker. target before 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. 4! Thanks for all your help!

The report, minus the About Page (#36173) and tickets regarding tests, which can land at any time (#35857) must be clear before RC.

At RC, we’ll be issuing a soft string freeze, with all strings to be considered frozen minus the About Page, which should be frozen by a week before release at the latest.

As a reminder, after RC, every commit must be approved by two leads or permanent committers, and only regressions or blockers are addressed.

If you own ticket(s) on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. in the 4.5 milestone:

  • If your ticket is not going to be committed today, please 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.) it to Future Release.
  • Please commit, or add an update as to what is left as a comment on the ticket, and why it should remain in the milestone.

We’re almost to RC. Thanks to everyone for your help!