Scheduled 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 are completed 😊 Thanks to everyone!
Please continue testing 6.6 💪
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). Bug Scrubs will be conducted if needed.
Following sessions are dedicated to move things forward and be ready in time according to 6.6 Release Schedule.
Everyone is welcome to join not only to triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets but also to look for tickets you can contribute by creating patches, making code review and testing.
Things to keep in mind:
- All features and enhancements should be in the Trunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. before 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 and most bugs and all strings need to be there before RC1.
- If you are working on a patch 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., plan your contribution to have enough time for other contributors to make suggestions, review and test.
Alpha Bug Scrubs
Focus: features, enhancements and then bugs with priority on tickets that are closer to resolution
Beta Bug Scrubs
Focus: rest of the bugs plus reported regressions
Release Candidate Bug Scrubs (if needed)
Focus: issues reported from the previous RC 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)..
Check this schedule often, as it will change to reflect the latest information.
Regular component scrubs and triage sessions
For your reference, here are some of the recurring sessions:
Have a regular 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.” @nhrrob or @oglekler 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.
You can start your own triage sessions
- Decide what you want to work on
6.6 triage session are our priority and moving forward tickets which already are scheduled for the release is most needed task. If you want to lead some of them, they can be added on this schedule.
But if you are interested in particular component or user focus, for example to take care about RTL-tickets, this will be most welcome too.
Especially interested can be the session to scrub old tickets. We are continuously closing new tickets with the same topic in favor of existing ones and because these tickets are looking complicated just because they’re age not, so many contributors are eager to work on them, but there are actual treasures hidden among very difficult or tricky topics.
- Ping @oglekler or@nhrrob on Slack with the day and time you’re considering, as well as the report or tickets you want to scrub. Note that scrubs are happening in the main core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel and cannot clash with other meetings in this channel.
Useful reports and information
- Report 5 provides a list of all open 6.6 tickets:
- Use this list to focus on highest priority tickets first.
- Use this list to focus on tickets that haven’t received love in a while.
- Report 6 provides a list of open 6.6 tickets ordered by workflow.
Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the core handbook.
#6-6, #bug-scrub, #core
