Test Chat Summary: April 23, 2024

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

Attendance

@sirlouen @krupajnanda @pavanpatil1 @zeelthakkar @oglekler @pratiklondhe (async) @muddassirnasim(async) @nikunj8866 (async) @narenin (async)

2. Volunteer

This week’s Note-taker and facilitator:

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

  • No updates

6. Questions/Blockers

  • No Questions/Blockers reported in this meeting

7. Call for Testers/Visibility

  • WordPress 6.8 is already out. If you come across any issues, please report them on Core Trac or GitHub.
  • The 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.7 is now available – https://wordpress.org/plugins/gutenberg/

8. Discussion

During the meeting, @sirlouen raised the issue of the Workflow Keywords, specifically around the keyword needs-testing-info, which has been causing confusion due to its similarity with needs-testing.
Two solutions were proposed, with the renaming of the keyword considered the most viable. Here, the objective is to enhance usability and maintain clarity in the keyword naming scheme. @joemcgill suggested the keyword needs-test-info, as it aligns better with the current format of existing workflow keywords.

A quick poll was conducted during the meeting, and the majority voted for the following naming convention:

  • needs-test-info
  • has-test-info

These changes will align testing-related keywords with the overall naming scheme used in the project.

@krupajnanda asked whether the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team would support implementing these changes once the updated keywords and their intended usage are shared. @joemcgill confirmed his willingness to assist with this.

@sirlouen mentioned that once @muddassirnasim completes the meeting notes, he will forward the information to @dd32 for inclusion in the official TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. documentation.

9. Open Floor

No items discussed

10. Next Meeting 🗓

April 30, 2025, at 21:30 GMT+5:30: <test-triage> #core-test

May 07, 2025, at 21:30 GMT+5:30: <test-chat>  #core-test!

#core-test, #meeting-notes