Test Chat Summary: May 07, 2025

On Wednesday, May 07, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @pavanpatil1. The agenda can be found here.

1. Attendance

@krupajnanda @muddassirnasim @pavanpatil1 @oglekler @sirlouen @SJ @kausaralm @lumiblog(asnyc) @narenin(asnyc) @puja

2. Volunteer

This week’s Note-taker and facilitator:

• Facilitator  – @muddassirnasim
• Note-taker – @krupajnanda

3. Announcements

• For now, 6.8 is identified as the last major release of the year
• WordPress 6.8.1 Maintenance Release was released on April 30, 2025 
• At the moment while writing this post, there are 9 tickets in the 6.8.2 milestone on Trac. Bug fixes currently located in milestone 6.9 can probably start to be moved to 6.8.x milestones, but 6.8.2 will most probably still be focused on remaining issues/regressions found on 6.8.
• Gutenberg 20.8 RC1 is now available. The final is release will be out next week.
• There is no final update about 6.8.2 release. Please keep an eye on dev chat weekly summary and/or #core channel.

4. Test Team Updates

• Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered.
• Test Team Update: Metrics for overall team progress.

5. Focal Group Updates

• #core-editor team has shared this for the issues that needs testing. Please feel free to pick and contribute to any tickets and make sure to update the same in the #core-editor for the better visibility.
• @sirlouen shared an update to the team that the new keyword has already been updated. Reports containing the old keyword will not be automatically updated and will need to be revised manually. He also mentioned that if any old keywords will be encountered then he will handle that part.
• SirLouen requested @OGlekler to remove the -needs-testing-info keyword from the weekly reports.
• The new list of keywords to use is: needs-testing has-patch -dev-feedback -2nd-opinion -close -needs-refresh -needs-design -needs-design-feedback

6. Questions/Blockers

@sirlouen raised a concern that many test reports genuinely needing attention are being overlooked, while others are already tested number of times but are still being retested which indeed does not add any value. To address this, he proposed manually curating a list of reports that actually need testing and will share clear, straightforward testing instructions to help non-technical testers contribute effectively.

In response, @krupajnanda thanked @sirlouen for volunteering to curate the list and requested that the list be posted in the channel once ready, so it can be pinned and easily accessed by others. (The list has already been pinned)

7. Call for Testers/Visibility

• Help test Gutenberg 20.8 RC1.

8. Open Floor Discussion

In a recent discussion, @sirlouen proposed a new initiative to host public Patch Test Scrub sessions dedicated to testing patches. Participants will be able to:

• Join a scheduled session and test patches live alongside others.
• Ask questions and get real-time guidance especially for more complex patches.
• Learn from practical examples pulled from SirLouen’s Curated Testing List.

The very first Patch Test Scrub is scheduled for Monday, May 12th at 3PM GMT (5PM CEST / 8:30PM IST) and will be facilitated by @sirlouen. Future scrubs may adapt based on feedback and participation that we will receive.

9. Next Meeting

Wednesday, 14 May 2025 at 21:30 GMT+5:30:  <test-triage> in #core-test.

Wednesday, 21 May 2025 at 21:30 GMT+5:30:  <test-chat> in #core-test.

#core-test