Bug Scrub Schedule for WordPress 6.7

It’s time to get WordPress 6.7 ready for release, and help is needed to ensure it’s smooth and 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.-free. Whether you’re an experienced contributor or joining in for the first time, everyone is welcome at our bug scrubs! 🎉

Schedule Overview

Regular bug scrubs are being held every week leading up to the WordPress 6.7 release, with some cases including two sessions a day to cover a broader time frame. As the release date approaches and activity ramps up, the number of scrubs may be increased if necessary. These efforts will help ensure everything is on track for a smooth launch. Participation is welcome at any of these sessions, so feel free to join. Bring questions, ideas, and let’s scrub some bugs together!

Continue reading

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

Bug Scrub Schedule for WordPress 6.6

Scheduled 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. scrubs are completed 😊 Thanks to everyone!
Please continue testing 6.6 💪

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). Bug Scrubs will be conducted if needed.

Continue reading

#6-6, #bug-scrub, #core

Initial Bug Scrub for 6.5.1

There is no specific target date for WordPress 6.5.1 yet. However, we can start ensuring that all the correct bugs are targeted for it and that work progresses towards fixing them.

To assist with preparation for 6.5.1, an initial scrub will be held at Thursday, April 4, 2024 at 18:00 UTC in the #core 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/. channel.

Thanks to @desrosj and @hellofromtonya for pre-publication review.

#6-5, #6-5-x, #bug-scrub

6.4.3 Maintenance Release Bug Scrub

There is no specific target date for WordPress 6.4.3 yet, but that doesn’t mean work can’t be done to ensure that all the correct bugs are targeted for it and that work progresses towards fixing them. To assist with this, some initial scrubs will be held at the following times:

All Scrubs will take place in the #core room in Slack. The first scrub will be going through tickets in awaiting review that may belong in the 6.4.3 milestone with the goal of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and the second scrub will focus on tickets in the 6.4.3 milestone.

Anyone else that wishes to host a scrub for 6.4.3 is welcome. Please comment here with the time you would like to hold one and I will edit the post to include it. As the documentation on leading bug scrubs states:

Leading a Bug Scrub is something any interested community member can do.

Thanks to @joemcgill for prepublication review

#6-4, #bug-scrub

Bug scrub schedule for WordPress 6.5

This post lists 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 the next major WordPress release, 6.5, slated for March 26, 2024.

The full 6.5 Release Schedule.

Everyone is welcome to join to help triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 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 (February 13, 2024) 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: general triage

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 Release Candidates.

  • 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

Below is a list of some of the recurring sessions which take place in the Make WordPress Slack.

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@chaion07, @rajinsharwar on Slack to have it added to this page.

Start your own triage sessions

Decide what you want to focus on first.

The 6.5 triage sessions and moving forward these tickets are the priority for the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team and the release. If you would like to lead sessions for these, they can be arranged and added to this schedule.

However, if you are interested in particular component or user focus, for example, to take care about RTL-tickets, this will be very welcome too.

Could you run a session to scrub old tickets? There are treasures which would benefit from scrubs and more contributors working on them in older tickets.

How to help?

  • In the core channel on Slack, ping @audrasjb, @chaion07, @rajinsharwar or one of the core team reps on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

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.

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

Bug Scrub Schedule for WordPress 6.4

Following sessions are dedicated to move things forward and be ready in time according to 6.4 Release Schedule.

Everyone is welcome to join not only to triagetriage 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. Keep in mind that 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 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., 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

Beta Bug Scrubs

Focus: rest of the bugs plus reported regressions

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). Bug Scrubs (if needed)

Focus: issues reported from the previous RC.

  • TBD

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 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 have it added to this page.

You can start your own triage sessions

  • Decide what you want to work on

6.4 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 @marybaum on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Useful reports and information

  • Report 5 provides a list of all open 6.4 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.4 tickets ordered by workflow.

Need a refresher on 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. scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Thanks to @audrasjb, @mukesh27 and @marybaum for helping to put together this agenda and peer review.

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

Bug Scrub Schedule for WordPress 6.3

It’s time to schedule the 6.3 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!
These 6.3 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Bug Scrubs

Beta Bug Scrubs
Focus: issues reported from the previous beta.

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). 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)..

  • TBD

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage 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:

Have a recurring 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, @chaion07, @oglekler, or @mukesh27 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 have it added to this page.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at any time? Yes, you can!

How? Ping @audrasjb, @chaion07, @oglekler, or @mukesh27 on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 6.3-focused? Awesome! It 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!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 6.3 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.3 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Thanks to @chaion07, @oglekler, or @mukesh27 for helping to put together the agenda.

#6-3, #bug-scrub, #core

Bug Scrub Schedule for 6.2

With 6.2 well underway, it’s time to schedule the 6.2 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. These 6.2 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Bug Scrubs

Hosted by @costdev

Hosted by @mukesh27 (APAC-Friendly)

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. Bug Scrubs
Focus: issues reported from the previous beta.

Hosted by @costdev

Hosted by @mukesh27 (APAC-friendly)

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). 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)..

Hosted by @costdev

Hosted by @mukesh27 (APAC-Friendly)

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage 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:

Have a recurring 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.” @costdev or @mukesh27 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 have it added to this page.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at any time? Yes, you can!

How? Ping @costdev or @mukesh27 on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 6.2-focused? Awesome! It 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!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 6.2 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.2 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @costdev or @mukesh27 on Slack.

Props to @hellofromtonya for reviewing the post.

#6-2, #bug-scrub, #core

Bug Scrub Schedule for 6.1

With 6.1 well underway, here’s the initial schedule of 6.1 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. These 6.1-specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Scrubs:

Hosted by @audrasjb:

Hosted by @chaion07:

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. Scrubs:

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). Scrubs:

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

The above 6.1 scheduled bug scrubs are separate and in addition.

For your reference, here are some of the recurring sessions:

Have a recurring 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 or @chaion07 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 have it added to this page.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at anytime? Yes, you can!

How? Ping @audrasjb or @chaion07 on slack and let us know the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 6.1-focused? Awesome! It can be added to the schedule above. You’ll get well deserved props in the weekly Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 6.1 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.1 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @audrasjb or @chaion07 on slack.

#bug-scrub

Proposal: Editor Weekly Bug Scrubs

This post is a proposal to start weekly Editor Bug Scrubs in #core-editor the week of June 28th. The scrubs will have a singular focus on issues in the Gutenberg GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ repository. If you have feedback, please comment by June 24th, 2022.

Overview

New in the WordPress 6.0 release cycle, the role of Editor Triage Lead triages GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ issues in the release and, to that end, runs weekly 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. scrubs in #core-editor.

As the release progressed, it became clear just how valuable these weekly meetings were in moving issues forward. And as the launch drew near, George Mamadashvili (@mamaduka) suggested continuing the scrubs a weekly, regardless of the release schedule.

Gutenberg right now has more than 4,200 open issues, and the number grows faster by the month.

And that number, especially out of context, makes a fairly convenient data point for observers to cite as evidence the project is not production-ready. Now, the same records that show the issues also show that dozens of contributors regularly and actively triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. these issues.

But the process for working through any set of issues on GitHub or tickets on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. is informal — that is the nature of open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL.. Which also means, therefore, that the process utterly depends on the interests and skillsets of those contributors who show up and do the work.

The result is an ad-hoc process that has produced hundreds of stale issues. Many of those are no longer relevant, but they stay open because nobody formally closes them. And truly important issues are at a nontrivial risk of slipping through the cracks.

Weekly bug scrubs will not single-handedly solve these problems. But they will dedicate a solid hour every week when team members (including you, who are reading this now!) get together, review issues, and make concrete plans to resolve them.

And during release cycles, the structure will give Editor Triage Leads a ready structure and a team of contributors to get more done, and produce a better experience, with every new version of WordPress.

Proposal

  • What will happen? An Editor Weekly Bug Scrub meeting, in #core-editor 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/., every Tuesday at 1400 UTC.
  • When will they start? The week of June 28, 2022.
  • How will people know they’re happening? The scrubs will be on the Meetings Calendar.
  • What will they cover? Bug scrubs will follow the normal process in the Handbook — but address only Gutenberg issues on GitHub. 
  • Who will run these scrubs? Members of the Gutenberg Triage Team. Nick Diego (@ndiego) and George Mamadashvili (@mamaduka) will run the first several. Then other team members will get onboarded for future sessions. 
  • How will they work with the release cycle?
    • As soon as the release squad has a designated Editor Triage Lead, that person will lead the meetings and tailor triage efforts to he release in progress. 
    • At launch, meeting leadership will go back to the Gutenberg Triage Team. Ideally, Editor Triage Leads will have come from the Gutenberg Triage Team, so that transition should be seamless.

Next Steps

So what do you think?

Please share your comments by June 24th. If the community agrees Editor Bug Scrubs would be a good thing, the first scrub will be Tuesday, June 28, 2022, at 1400 UTC.

Props to George Mamadashvili (@mamaduka), Justin Tadlock (@greenshady), Héctor Prieto (@priethor), and Birgit Pauli-Haack (@bph) for their help in putting this proposal together.

(Ed. note: Also, did you know that anyone can lead a bug scrub, for any reason? That means you! And you can focus your scrub on any tickets you like, or any Gutenberg issues. (The difference: most of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. runs on Trac, which uses tickets and patches. The blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor runs on GitHub, which uses issues and pull requests. – @marybaum)

#bug-scrub, #editor, #gutenberg