Category Archives: Meetings

Ankit K Gupta 2:48 pm on February 17, 2026
Tags: , ,   

Test Scrub Schedule for WordPress 7.0

As you’re aware, WordPress 7.0 is slated to be the first major release of 2026, with the official release date set for April 9, 2026. As we gear up for this important milestone, our Test team will be shifting gears a bit. 

Starting from our upcoming weekly Patch Testing Session, we’ll be running a Test Scrub for WP 7.0 instead of the usual Future Milestone Tickets. These scrubs will focus specifically on tickets and issues related to the WordPress 7.0 milestone. It’s a great opportunity to contribute to this major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. and make a tangible impact on the final product. 

Where Will It Happen?

Each Test Scrub will take place in the #core-test channel on the Make WordPress 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/ at the same time as our regular weekly Test team meetings. If additional release‑focused scrubs are scheduled, they’ll also be announced in #core-test and added to the meetings calendar. 

What Tickets Will We Focus On?

We’ll primarily concentrate on tickets that are tagged Has Patch or/ Needs Testing for the 7.0 milestone. You can find these tickets in the 7.0 report on Trac. As the release moves through 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. and RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge., we’ll also highlight key features and regressions that need focused testing.

Interested in Leading a Test Scrub?

Did you know that anyone can lead a Test Scrub at any time? Yes, that means you can!

If you’re interested in leading a scrub, please reach out in the #core-test Slack channel with: 

  • The day and time you’re considering
  • The report or tickets you’d like to focus on (for example, a specific TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. report, a feature area, or a Beta/RC build)

If you’re planning a scrub that’s specifically focused on WordPress 7.0, that’s fantastic! We can add it to our schedule so the rest of the team knows to join in. Leading a scrub is a great way to contribute. 

Let’s Contribute Together

This is a perfect chance to get involved with the major release of WordPress 7.0, learn more about the release process, and help ensure the quality and stability of WordPress. Your contributions will make a difference, so join us for the Test Scrub sessions and be a part of this exciting release. 

Thank You ❤️

Thanks to everyone contributing time, testing, feedback, and expertise. Community testing plays a critical role in making each WordPress release successful.

Let’s work together to make WordPress 7.0 a smooth and high-quality release.

Props to @huzaifaalmesbah, @marybaum, and @nikunj8866 for pre-publish review.

#call-for-testing, #core

Nikunj Hatkar 11:17 am on January 14, 2026
Tags:   

Team Chat Agenda: 14th January, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, 14 January 2026, 02:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test

Moses Cursor Ssebunya 1:55 pm on December 22, 2025
Tags: , , , , ,   

Test Chat Summary: December 17th, 2025

On Wednesday, December 17th, 2025 at 04:00 PM GMT+2, started in#core-test facilitated by @mosescursor. The agenda can be found here.

1. Attendance

In attendance was:
@fakhriaz @nikunj8866 @huzaifaalmesbah  @noruzzaman  @sirlouen @oglekler @r1k0 @abduremon @Dhruvang21 @gautammkgarg @mebo

2. Volunteer

Meeting started by explaining Note takers and Facilitators so people can take up the roles.

  1. Note takers are simply people who summarize the happening of the Test Chat and they always publish a test Chat summary like this one here.
  2. Facilitators are simply people that chair or facilitate a test team chat.
    These follow the agenda that is proposed and ensure that every one gets a voice.
    A sample Meeting is like the one held here.

These 2 can be done by the same person in the same instant however we encourage multiple people to do it to increase on the proof reading and collaboration

3. Test Team Discussions

  1. Time to Review/Update the Get Set Up for Testing Page.
  2. Time to Comment Back/Update the Test Team Reps Page.
  3. Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via 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 by the repository owner. https://github.com/ issues.
    • @sirlouen got to a conclusion that currently we don’t have enough resources to have the wheel moving
      • all the areas mentioned above require a good thought and a suggestion to expand the team was brought up.
  4. Test Team Training Program & Restructuring Plans for 2026
    • @sirlouen is leading the program.
    • Previously, mentorship was insufficient so now a full training was advised. A program in the test team that will bring in Champions
      • A call for as many people as possible was made. People that will be committed to the program and see it through
    • @nikunj8866 sighted it as a great learning opportunity for anyone who wants to become a future Test Team representative.
      • @sirlouen added that it won’t only make team reps but also Power Members.
    • @sirlouen will pause current Handbook activity in preparation for the program in the next 2 weeks. Announcement made here highlighting the requirements to join and all the information about the program.

4. Open Floor

  • We have introduced a bot that informs of new 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 coming for testing. This posts directly in the 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
    • @sirlouen recommended adding an emoji like this :white_check_mark:  if you are going to be doing the testing report.
    • This helps for quick assignment of tasks and getting them cleared quickly.
    • Here people get a chance to know the tests required and even do them without having to wait for a Patch-testing session.
      • Infact this could also end the patch testing sessions when the new training is implemented
        • With this new notifier, anyone could jump in

5. WordPress Ecosystem Announcements

6. Other Meetings

We usually have 2 meetings held every week. This is the last test-chat meeting for this year and Tomorrow’s patch testing session will be the last for this year.

  • Happy Festivities, See you again Next Year.
  • Happy new Year 2026

#core-test, #fse-outreach-program, #full-site-editing, #gutenberg, #make-wordpress-orgupdates, #web
Moses Cursor Ssebunya 1:06 pm on December 17, 2025
Tags: , , , ,   

Team Chat Agenda: 17th December, 2025

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, 3rd December 2025 at 16:00 GMT+2, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test, #full-site-editing, #gutenberg, #make-wordpress-orgupdates, #web

Moses Cursor Ssebunya 1:15 pm on December 3, 2025  

Team Chat Agenda: 3rd December, 2025

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, 3rd December 2025 at 16:00 GMT+2, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

Moses Cursor Ssebunya 6:53 am on November 22, 2025
Tags: , , , ,   

Test Chat Summary: November 19th, 2025

On Wednesday, November 19th, 2025 at 04:00 PM GMT+2, <test-chat> started in#core-test facilitated by @sirlouen. The agenda can be found here.

1. Attendance

In attendance was:
@sirlouen @huzaifaalmesbah @rithika3 @r1k0 @oglekler @sajib1223 @noruzzaman @dhruvang21 @fakhriaz @mosescursor @harshalkadu @muddassirnasim

2. Volunteer

This week’s facilitator was @sirlouen
This week’s Note-taker was @mosescursor

3. Test Team Discussions

  1. Time to Review/Update the Test Team Reps Page.
    •  A recent discussion brought up 2 things
      • New contributors badge requirements
      • Test Reps eligibility for next year
    • We have identified that to join the Test Team, people should get some experience running these sessions. Something that is not hard as someone needs to know how to make a test Chat Agenda and Follow that for the meetings.
      • @sirlouen proposed that if a person ran a Test Chat Meeting, they would then be eligible for a Test Contributor Badge. This year, many people were nominated without any experience, and this is not acceptable
      • He also added that Test Scrubs is another activity that future Test Reps should do and hence Test Scrubs is also promoted for eligibility. For example: 2 test scrubs + 2 meetings will be enough for eligibility for Test Rep position with my proposal
        • Test scrubs can be initiated from today, but meetings will be initiated starting January 2026, and we will have a list when people sign up for it.
        • @oglekler added that a Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. must be experienced with all team activities before applying to become a Team Rep. This will save both the applicant and team any surprises.
          • @mosescursor suggested that Team Reps should come from the Test Team members. A position a person gets after cycling through the Test Team processes.
            • @oglekler said that Team reps and Team members will have to support the contributors to get to that level. This also calls for contributors interest.
      • A simple Q&A
        • How can a Person sign up for running a meeting?
          After January, during each meeting, the current Team Reps will be asking if anyone wants to run the meeting and we will also post the current “list” in case more than one user has proposed. When they ask, you can raise your hand and they will contact you, put you in the list, and explain all the steps on how to run the meeting. We are starting on January because we need the current reps to get a little more experience before starting to add new members to this
        • How can I run a Test Scrub?
          You can run one of these whenever you want. You can just contact @sirlouen or any of the current test reps, and we will make sure you learn the basics on how to run a good test scrub
    • @sirlouen will then be drafting the new page for reps.
    • Remember that now Forum discussions are happening in GitHub, and the discussions will be kept for a week before a decision is made.
      Feel free to write there whenever you want, send a new proposal, etc (remember that every proposal has to go first through a meeting like this and then 1 week to discuss in 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 by the repository owner. https://github.com/)
  2. Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via GitHub issues.
    • No progress in this regard.
      • Again, feel free to comment in any of these three, or if you are brave, send a PR with your proposal for any of the 3.
  3. For anyone that could be interested in becoming a Test Rep, or Test Team Member(like @sirlouen), who is not a Test Team Rep, but a Test team member), it’s important to engage in these kinds of things and promote things in general. It’s impossible to join the team from a passive position

4. WordPress Ecosystem Announcements

5. Open Floor

  • @sirlouen is working on developing a 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/ testing protocol for the future. This is mainly driven by the many people struggling with testing in the previous scrubs. We have to understand that testing needs some technical skills, but many people have some skills but waste a lot of time trying to set up everything, and they never come back again after the setup.
    • @sirlouen is trying to lower the learning curve a little bit by introducing WordPress Playground Concepts. In these tests we will not be using wordpress-develop or wp-env anymore for testing, except for very complex tickets that need much more deep work.
      • These are going to first be tested in the 2 Testing Scrubs scheduled for Tomorrow.
        • Release Squad Testing scrub
        • and Regular testing scrub

6. Other Meetings

We usually have 2 meetings held every week and the times have been listed bellow for next week. an adjustment has been made to include the WordPress 6.9 Test Scrub and will soon be listed

Props to @nikunj8866, @sirlouen and @oglekler for helping review these notes and offering feedback.

#core-test, #full-site-editing, #gutenberg, #make-wordpress-orgupdates, #web

Nikunj Hatkar 4:12 am on November 19, 2025
Tags:   

Team Chat Agenda: 19th November 2025

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, 19 November 2025, 02:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test

Nikunj Hatkar 11:31 am on November 5, 2025
Tags:   

Team Chat Agenda: 05th November 2025

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, 05 November 2025, 02:00 PM UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test

Moses Cursor Ssebunya 7:10 am on October 21, 2025
Tags: , , , ,   

Team Chat Agenda: 22nd October 2025 

Here is the agenda for the upcoming Test Team Chat scheduled for Wednesday, October 22, 2025, 5:00 pm GMT+3 , which is held in the #core-test Slack channel. Well wishers are all welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test
Last Updated Wednesday, 22 October 2025 at 16:00 GMT+3

Props to @nikunj8866 for helping review this article and offering feedback

#core, #core-test, #fse-outreach-program, #make-wordpress-org-mobile, #make-wordpress-orgupdates

Manuel Camargo 2:21 pm on October 9, 2025
Tags:   

Test Chat Summary: October 8, 2025

On 8 October 2025 at 2PM GMT, <test-chat> started in #core-test facilitated by @sirlouen The agenda can be found here.

1. Attendance

@mosescursor @nikunj8866 @agulbra @dhavalkapadane @fakhriaz @muddassirnasim @passoniate (async) @dilip2615 (async)

2. Volunteer

This week’s note-taker was @sirlouen

3. WordPress Ecosystem Announcements

4. Test Team Announcements

5. Call for Testing

6. Test Team Discussion, Questions, and Blockers

1. Handbook Overhaul—Task Assignments

  • The meeting began with the launch of the Handbook Overhaul project, focusing on assigning tasks to contributors.
  • Each participant will be assigned at least one new page to create and two or three pages to review.
  • The objective is to ensure every single documentation page is properly replicated before the originals are deleted—anything not replicated will be lost.
  • Tasks for contributors fall into three categories:
    • Create: New pages to be created, primarily copied from the originals.
    • Review: Existing pages requiring review and verification.
    • Discuss: Pages to be discussed in any meeting, like the Archive section.
  • A second call-out will be made for more volunteers, who will then be assigned tickets.

2. Proposal: Archiving Old Sections

  • A proposal was presented to create an “Archive” section in the documentation for obsolete content.
  • The specific example raised was archiving the “FSE Outreach Experiment” page and similar sections not currently useful.

3. Section Review: “Crawl your test site for errors”

  • A specific section, “Crawl your test site for errors”, was discussed.
  • The group debated whether this section is still relevant to keep, with some members expressing doubts.
  • The decision was left open for further review and comments. Removal will be approached in the next meeting unless there are any arguments against it.

7. Closing and Open Floor

  • @fakhriaz commented about ongoing testing, such as a categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. dropdown not meeting 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) standards (#63531), and a problem with classic widgets.
  • Also, members were informed, that during testing (e.g., “Accordion 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.”), participants can report that no issues were found after comprehensive checks.
  • A proposed change in the meeting structure: start with discussions and open floor items, and save announcements for the end. This aims to capitalize on initial engagement and ensure action points aren’t overlooked.

8. Next Test Team Sessions

Props to @nikunj8866 and @mosescursor helping review these notes and offering feedback.

#core-test