As work begins on 6.1, it’s time to schedule some early 6.1 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. scrub sessions.
These scrubs will happen once a week, usually scheduled for Thursdays at 18:00 UTC, though there may be some adjustments to accommodate releases, as well as religious and national holidays.
Right now, this only includes Early Scrubs. A release schedule for Alpha, 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., and 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). scrubs will follow soon.
Focus: early tickets milestoned for 6.1, tickets that require more time or early testing.
Hosted by @costdev
Monday, 9 May 2022, 18:00 UTC Thursday, 19 May 2022, 18:00 UTC Cancelled due to 6.0 RC4 release. Thursday, 26 May 2022, 18:00 UTC Thursday, 2 June 2022, 18:00 UTC Thursday, 9 June 2022, 20:00 UTC Thursday, 16 June 2022, 20:00 UTC
Hosted by @audrasjb
Starting from Thursday, 23 June 2022, 20:00 UTC, @audrasjb will be hosting recurring 6.1 bug scrubs every Thursday at 20:00 UTC.
Hosted by @chaion07
Starting from Tuesday, 7 June 2022, 05:00 UTC, @chaion07 will be hosting recurring 6.1 bug scrubs every Tuesday at 05:00 UTC.
Check this schedule often, as it will change to reflect the latest information.
What about recurring component scrubs and triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?
For your reference, here are some of the recurring sessions:
- Accessibility Scrub: Every Friday, 15:00 UTC, in the #accessibility channel.
- Help/About & Quick / Bulk Edit Scrub: Every Monday, 19:00 UTC, in the #core channel.
- Editor Scrub: Every Tuesday, 14:00 UTC, in the #core-editor channel.
- Testing Scrub: Every Friday, 13:15 UTC, in the #core-test channel.
- Design Scrub: Every Tuesday, 16:00 UTC, in the #design channel.
Have a recurring component scrub or triage session?
Ping The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @costdev on Slack 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 have it added to this page.
Want to lead an Early Bug Scrub?
Did you know that anyone can lead a bug scrub at any time? Yes, you can!
How? Ping @costdev on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.
Your scrub can be added it to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!
Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.
Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @costdev on Slack.
Props to: @hellofromtonya for proof-reading.