On Thursday, July 16, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.
1. Attendance
@krupajnanda @oglekler @sirlouen @nikunj8866 @getsyash @ravigadhiyawp
2. Volunteer
This week’s Note-taker was @krupajnanda
3. Announcements
4. Test Team Updates
- Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered.
5. Calls for Testers/Visibility
6. Open Floor Discussion
@sirlouen gave an update on the WordPress 6.8.2 Maintenance Release, specifically noting that the final quality review is still in progress and additional reviewers are welcome. He acknowledged that the review is taking a bit longer than expected due to the volume of data being processed. When @krupajnanda asked about the scope of the quality review, he clarified that it involves analyzing detailed test results and tables he previously shared in an earlier round table(RT) meeting.
In support of this effort, SirLouen also referred to the “A Month in Core – June 2025” update, showcasing contribution data. He highlighted concerns between the efforts of the Test Team in core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contributions. This gap, backed by real data, will be further explored to help guide improvement and collaboration across teams.
@sirlouen also shared that he is planning to have zoom call with fellow contributors on the PHPStan proposal on this Friday, July 18 at 1 PM GMT / 3 PM CET / 6:30 PM IST. The goal of this call is to walk interested contributors through the current proposal, explore how they can get involved, and discuss some of the early feedback and ideas. This session will be conducted over a Zoom. @krupajnanda has requested to prepare the agenda and summary(after the meeting) post for the same.
During the discussion, we emphasized the importance of transparency and structure for any upcoming contributor focused calls. @krupajnanda suggested creating an agenda or call-out post similar to how team chats are managed. So contributors clearly understand the purpose, the topics to be covered, and who the call is aimed at (e.g., developers, QA, etc.). This would help set expectations, offer clarity, and encourage meaningful participation.
@krupajnanda mentioned that this approach would help us stay on track during meetings and @oglekler also acknowledged that if we doing anything within the community space then it should be done in community-friendly and transparent way.
7. Next Meetings
#core-test
