4.2 Enhancements Deadline is March 10th

In a typical release cycle, the 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. stages are known as the period where we ramp down and shift focus to testing and fixing bugs only. The testing stages in the 4.2 release cycle will not differ on this point. However, unlike in some previous releases, the shift to working on bugs and testing will be more pronounced in 4.2.

According to the release schedule, Beta 1 is set to begin on March 11th — just about 2 1/2 weeks from now. This means that on March 10th, any enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ticketticket Created for both bug reports and feature development on the bug tracker. that has one or more commits against it, and/or is owned by a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. will be converted to a blessed task.

Without exception, all enhancement tickets not converted to tasks on March 10th will be punted to a future release or closed.

So, if you’ve got a pet ticket you’d still like work on for 4.2, now is the time to start if you haven’t already.

If you’re looking for an enhancement to work on, there’s a whole report to choose from!

Next Steps:

Developer Feedback

If you have a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. that needs developer feedback, add the dev-feedback keyword to the ticket and leave a comment. I would also encourage you to mention the ticket in the comments of the Monday jump-start or Wednesday dev chat agenda posts on make/core. You could also mention the ticket number during the “Open Floor” time at the end of the weekly core dev chat on Wednesdays.

AccessibilityAccessibility 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)/Mobile/UIUI User interface Feedback

If your ticket has anything to do with administration or UI, jump into the #accessibility, #core-flow, or #design channels on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. to get accessibility, mobile, or design feedback.

Not Ready

If you feel like you just aren’t going to have time to work on your enhancement ticket between now and the March 10th deadline, no problem. Just leave a comment to that effect on the ticket and somebody will come along and mark it for Future Release.

#4-2, #deadlines, #tickets