Following the open call for tickets and the planning roundup, we are ready to kickoff the release cycle for WordPress 5.3!
After checking with the focus leads, the proposed timeline is confirmed, as follows:
- 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. 1: 23 September, 2019
- 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).: 15 October, 2019
- General Release: 12 November, 2019
The focus will be polishing current interactions and make the UIs more user friendly.
- Release Lead The community member ultimately responsible for the Release.: Matt (@matt)
- Release Coordinator: Francesca Marano (@francina)
- Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM: David Baumwald (@davidbaumwald)
- Editor Tech: Riad Benguella (@youknowriad)
- Editor Design: Mark Uraine (@mapk)
- Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech: Andrew Ozz (@azaozz)
- Docs Coordinator: Justin (@justinahinon)
- Marketing/Release Comms: Mike Reid (@miker)
- Media/Uploader: Mike Schroder (@mikeschroder)
- Accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility): JB Audras (@audrasjb)
- Default Theme Wrangler: Ian Belanger (@ianbelanger)
- Default Theme Designer: Anders Norèn (@anlino)
At the moment of writing, there are 327 tickets open in the milestone: https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&milestone=5.3&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority.
Weekly Bug Scrubs
We will work our way through them via weekly scrubs.
Proposed schedule will be discussed today, August 21st 2019, during the weekly Core chat. Ideally we will get assistance from component maintainers, that can help run specifically focused 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. scrubs.
Let’s do this, ad maiora!