On Tuesday, February 27, 2024 at 04:30 PM GMT+5:30, <test-chat> started in #core-test facilitated by @webtechpooja Agenda can be found here.
1. Attendance and Looking for Volunteer
Attendees: @oglekler, @bph, @shiponkarmakar, @huzaifaalmesbah, @sumitbagthariya16, @hasanuzzamanshamim, @webtechpooja, @nazmul111, @ankit-k-gupta, @devmuhib, @narolainfotech, @lumiblog, @tapan29bd, @hage, @krupajnanda, @rcreators, @ironprogrammer, @freewebmentor
Note-taker and facilitator for the next meeting:
Facilitator – Looking for volunteer (@webtechpooja will be traveling during the next meeting to attend WCAsia.)
Note taker – @freewebmentor
Looking for Volunteer
We are looking for a volunteer to work on user calls for testing (for more detail, check out the guide: How to facilitate a Call for Testing).
@webtechpooja asked for more insight from @bph. She added that the recent outreach program restart revealed positive feedback, highlighting the effectiveness of this approach in engaging non-coders. Test Team seeks collaborators for the regular creation of no-code user testing calls, catering to site builders and owners. Join us at WordCamp Asia Contributor Day for discussions, or connect asynchronously to plan and schedule Hallway Hangouts.
2. Announcements 📣
- WordPress 6.5 Beta 2, released on February 20, 2024, extends thanks for your contributions. Asked to join the upcoming WordPress 6.5 Beta 3 release party in the #core channel.
- Exciting update: WordPress 6.5 introduces AVIF support, a cutting-edge image format delivering superior quality and compression, up to 50% smaller than JPEGs. Explore and test this feature in the latest release!
- WordPress developer live stream: testing WordPress 6.5 If you want to know what is upcoming in WP 6.5. @psykro is hosting an online workshop. Do join the workshop.
3. Test Team Announcements
- 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.
4. Focal Group Updates
@ankit-k-gupta is extending the opportunity to host the Test Team Triage biweekly meeting. If anyone is interested, please express your willingness.
@hage asked, Is there additional AVIF information beyond Specifically, I’m curious if existing JPEGs can be converted to AVIF without using a plugin.
@ironprogrammer replied, The update introduces support for new AVIF uploads and auto-conversion upon upload via the ‘image_editor_output_format‘ filter, but it doesn’t alter existing images. @hage suggests that to modify existing images to AVIF in bulk, installing a corresponding plugin may be necessary.
@oglekler has a proposal that she would love to see working groups between developers and testers. @bph replied they just created Github group WordPress/Outreach that developers can ping for feedback and testing. She also drafted the announcement on Google Doc.
@oglekler replied – @bph, I’m not just suggesting casual pings; I’m advocating for close collaboration from project inception. Testers can contribute valuable insights on project architecture right from the start, applicable not only to the Editor but across WordPress. @bph replied – Yes, of course, the ping is the first step for the developer when they are ready to connect.
@hage added – The background to my question: I would like to test this in more detail. @webtechpooja replied – you’re on the right track! @oglekler and other Test Release leads are crafting a post set to release this week. It will contain comprehensive details and testing instructions, so stay tuned for updates.
5. Call for testers/visibility
- WordPress 6.5 going to be released on March 26, 2024; please help test.
- Early Opportunities to Test WordPress 6.5 , Check out these features.
- Bug scrub schedule for WordPress 6.5 if you want to help with Trac tickets. Check out this Bug scrub schedule.
- Gutenberg 17.8 release is planned for Feb 28, 2024. Please help test.
6. Open Floor
@rcreators think we should create high priority testing tags for features that need more testing. Or we can have quite a separate list for testing for this part.
@bph asked – why in the list of things to testing issues from Gutenberg repo are not listed. Just want to know the history of the decision. @ironprogrammer is seeking clarification on areas where we might have overlooked pointing out issues related to GB (Gutenberg).
@bph replied I only noticed it on This week of Test where new tickets are listed under Reproduction tests. They seems to be all trac tickets. @ironprogrammer mentioned the omission of highlighting Gutenberg issues in WiT posts wasn’t intentional. Challenges arose due to labeling inconsistencies and filtering issues, making it difficult to categorize “small/medium/large” ticket types accurately. The dilemma lies in triage/labeling, and the suggestion is to explore using the “Needs Testing” label for potential solutions.
@rcreators added – Also, if we can add something like a deadline for testing task that would be great. @webtechpooja replied – In our open-source, volunteer-driven project, imposing deadlines is not feasible.
@krupajnanda requested to change the weekly meeting time. But rest of the people are happy with the current time and suggested her to join asynchronously.
7. Next Meeting 🗓
Next meeting will be on Tuesday, March 12, 2024 at 04:30 PM GMT+5:30, held on #core-test! </test-chat>
If anyone wants to facilitate the next meeting, please feel free to comment in this thread.
Thank you, @webtechpooja, for the peer review and for helping me write this post.