Test Chat Meeting Recap Notes: 26 March 2025

1. Attendance

krupajnanda, nazmul111, pmbaldha, shanemuir, kausaralm, vgnavada, pavanpatil1, hage, oglekler, sirlouen, narenin

2. Looking for volunteers

  • Note Taker – Needs volunteer
  • Next meeting facilitator – Needs volunteer

3. Announcements

  • Call for testing post is out. Please help test WordPress 6.8
  • RC1 release of WordPress 6.8 is now available.
  • The RC2 release of WordPress 6.8 is scheduled for the 1st of April. Please check the detailed overview of the release schedule for WordPress 6.8. Join the Release Party 1st April @5PM CEST in #core to test and provide the feedback.
  • 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/ 20.5 was released on Thursday, March 20th. Checkout the milestone for the issues that were part of the 20.5 release.

4. Test Team Announcements

5. Focal Group Updates

6. Questions/Blockers

  • SirLouen first raised the recurring issue about the lack of a place for test team members to comment on improvement ideas and proposed a solution to use the following site to add ideas and comments for future meetings. You can see the topics without registering, but if you want to propose new topics, you can send a direct message to @SirLouen on the Slack server with an email address to add you.
  • Krupa proposed another additional approach to add ideas for next meetings: A thread will be opened 2 days before each meeting in the #core-test Slack channel, and you can add your ideas there.

7. Call for testers/visibility:

8. Open Floor

  • SirLouen first raised an issue about the testing workflow implementation gap, insufficient test reports, QA concerns and a lack of a stable testing team, and proposed a solution: Introducing an unofficial mentorship program to help new contributors get involved in testing more details here, with the primary goal of building a stable testing team that could be referenced similar to the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, editor team, or performance team.
  • OGlekler noted that testing is being promoted in Core Contributor meetings and suggested promoting testing in other places as well. We will do a brainstorming session to discuss this. Here is a thread to brainstorm the ideas. Also mentioned that the previous success with the Contributor Mentorship Program came from social media promotion, and pointed out the challenge with gaining volunteer motivation and commitment over time.
  • Krupa acknowledged the need for a structured testing workflow and a stable team, but volunteer participation can be a challenge and the suggested mentorship program had potential to be a stepping stone for new contributors to get involved in testing. More insights are needed to ensure proposed changes are both sustainable and practical.

9. Next Meeting

10. Meeting Wrap up

SirLouen will help to develop a roadmap for progressive improvements to the testing workflow, with a focus on building a reliable testing team as the first priority.

We encourage you to participate in any of the ways available, Slack #core-test channel, with a comment in this post, directly in the next meeting or adding up to the Shared Doc Notes commented in this post.

Props to krupajnanda for peer reviewing this meeting recap.