Bug scrub schedule for WordPress 6.5

This post will list bugbug 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 dedicated to move things forward towards 6.5. This post will be taken forward by the 6.5 release coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. leads once they are in place. This post is being published early to provide a place to list bug scrubs and raise greater awareness and time on tickets for future releases, some of which may be aimed at 6.5.

The full 6.5 Release Schedule will be populated as planning for the release progresses.

Everyone is welcome to join to help triage tickets, explore tickets to contribute to by creating patches, writing or conducting tests, providing code reviews, and more. Things to keep in mind:

  • all features and enhancements should be in the Trunktrunk 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 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. 1 and most bugs and all strings need to be there before 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). 1 (RC1)
  • If you are working on 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., it is helpful if you can please plan your contribution to give enough time for other contributors to make suggestions, review and test.

Alpha Bug Scrubs

Focus: features, enhancements and then bugs

Beta Bug Scrubs

Focus: rest of the bugs plus reported regressions

  • Dates will be added as the development cycle progresses

Release Candidate Bug Scrubs (if needed)

Focus: issues reported from the previous RCrelease 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)..

  • Dates will be added as the development cycle progresses

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?
PingPing 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.” @audrasjb@oglekler or @marybaum @webcommsat on Slack to have it added to this page.

You can start your own triage sessions

  • Decide what you want to work on

6.5 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 one of the 2023 core team reps @hellofromtonya or @webcommsat on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.
    Note: when the 6.5 core triage leads are confirmed, contacts in this section will be updated.

Useful reports and information

  • More will be added as the development cycle progresses

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the core handbook.

Thanks to @oglekler for helping to put together this agenda and peer review, and to previous contributors to this to release bug scrub posts for the information reused in this post.

#6-5, #bug-scrub, #core, #props