Tag Archives: core

SirLouen 12:37 pm on March 30, 2025
Tags: core   

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.

vgnavada 5:45 pm on March 17, 2025
Tags: core, ,   

Test Chat Summary: March 12, 2025

On Wednesday 12 March 2025 at 21:30 GMT+5:30, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance

@Krupajnanda, @oglekler, @sirlouen, @vgnavada, @kausaralm, @shiponkarmakar, @pavanpatil1, @narenin, @nikunj8866, @pmbaldha, @mukesh27

2. Looking for Volunteers

  • @vgnavada volunteered to take notes on this meeting.

3. Announcements

  • Call for testing post is out. Please help test WordPress 6.8
  • Beta 2 release of WordPress 6.8 is now available for testing.
  • The BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3 release of WordPress 6.8 is scheduled for next Tuesday, March 18th. Please check the detailed overview of the release schedule for WordPress 6.8.  Don’t miss the Release Party in #core to test and provide feedback! :dart:
  • 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.4 was released on Wednesday, March 5th. Check out the milestone for the issues that were part of the 0.4 release.

4. Test Team Updates

5. Focal Group Updates

  • We are in the 6.8 release cycle and only 2 weeks from our first RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. release.
  • Check out what to expect in the WordPress 6.8 release: Roadmap to 6.8

6. Questions/Blockers

@sirlouen questioned about the testing suggestions doc: https://docs.google.com/document/d/1Q7Kzs-78XvrAjnjG_MhBJR6bSBk80rvzwnV90iYTjhg/edit?tab=t.0

7. Call for testers/visibility

8. Open Floor

The discussion started with an invitation for participants to share thoughts or raise topics for discussion. New contributors were directed to the bookmarks folder in the channel for helpful resources.

Key Points Discussed:

  1. Addressing Ethical Practices in Testing:
    • @vgnavada: Highlighted the issue of copying someone else’s test case, including the exact screenshot and text copy, and presenting it as their own, pointing out the unethical nature of this practice.
    • @sirlouen: Stated that the other user likely reused the same steps to confirm the patch without taking the time to do the work again from scratch. He described this as poor testing practice, as it would have been better to try different approaches to expand the testing cases.
    • @oglekler: Acknowledged that such issues hadn’t been caught before but noted that it should be looked into now. While copying someone else’s work is demotivating, She reassured that it wouldn’t benefit the person doing it and advised not to worry too much about it.
    • @krupajnanda: Expressed understanding of the concern and emphasized that copying someone else’s work, especially when it involves significant effort, is not the right way to contribute. She suggested that more eyes should be on each ticket to offer different perspectives and solutions.

  2. Bridging the Gap: Improving Collaboration Between QA and Development Teams
    • Challenges Identified: @sirlouen mentioned the often it observed that patches get approved with minimal verification, which can lead to unexpected issues down the line. When tickets don’t clearly outline use cases, it can slow down testing and create confusion. We need a clear mechanism for this situation to be resolved.
    • Proposed Solutions: Introduce a needs-use-cases tag to ensure clear reporting and smoother testing to encourage detailed testing reports and context from committers.
    • Next Steps: @mukesh27 supported the ideas and suggested a blog post to drive awareness and change.

9. Next Meeting 

10. Closing Remarks

The meeting wrapped up with a reminder to participants that discussions and questions are always welcome in the Test Team channel. The community is encouraged to continue contributing and collaborating outside of scheduled meetings.

  • @krupajnanda thanked @sirlouen for their feedback and assured them that the team would work on resolving the gaps identified. She acknowledged the active participation of the team during the meeting and emphasized that team members can raise questions or start discussions anytime in the Test Team channel.

Takeaways

The main takeaway is that better teamwork, clear communication, and accountability between QA and development teams are key to success. When both sides work together with honesty, transparency, and shared responsibility, things run more smoothly and lead to better results.

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#core-test, #summaries

Ankit K Gupta 2:22 pm on March 4, 2025
Tags: core,   

How to Contribute to WP 6.8 Release Party

Welcome! Here’s a guide to help you join and participate in the Release Parties scheduled for WordPress 6.8. If you are new to attending a release party, this will help you get started.

Schedule:

Set a reminder for the upcoming release party:

How to Join:

  1. Download SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
  2. Sign in to the WordPress Slack Workspace:
    • Visit WordPress Slack to log in or create an account if you don’t already have one.
    • Join the #core Channel.
    • This is where the release party happens! Use this link to join: #core channel
  3. Arrive Early and Be Prepared:
    • Join the channel about 10 minutes before the scheduled time and make sure your test environment is ready to go.

Skip above steps if you already have WordPress Slack account and joined #core already.

Setting Up Your Test Environment:

Make sure you have a local development environment or testing site ready to run the latest WordPress 6.8 version. 

(Please don’t test/update on any client site or any Production/Live Site)

Here are two methods to update to an RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge./BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. version:

  1. Using WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/: Ensure WP-CLI is installed on your environment.
    Run the following command to update:
    • wp core update --version=6.8-beta1
  • To verify the update with: 
    • wp core version
  1. Using the WordPress Beta Tester PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party:
  • Install and activate the WordPress Beta Tester plugin:
    • Go to Plugins > Add New, search for “WordPress Beta Tester,” install, and activate.
  • Configure the settings:
    • After activation, go to Tools > Beta Testing in your WordPress dashboard.
    • You’ll see options to select the type of updates you want:
      1. Bleeding Edge – Updates to the latest development version.
      2. Beta/RC Only – Updates only to Beta and RC versions.
    • For testing an upcoming release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge., choose Beta/RC Only.
  • Go to Dashboard > Updates and update to the RC version.

What to Test During a Release Party:

When testing a WordPress release candidate (RC), the goal is to catch any issues or inconsistencies that could impact the final release. Here’s a checklist of key areas to focus on during testing:  General Testing Checklist

You can also test anything you would like to ensure and provide your feedback. 

Where to Provide the Status of Your Testing:

Main Channel: Provide updates directly in the #core channel on the WordPress Slack.

Format for Updates: Use a brief format to keep your updates clear and easy to follow:

  • What You Tested: Mention the specific feature you tested like creating a page with a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.. 
  • Results: Share whether the test passed or failed, along with any notable observations. Please look at the below scrshot for reference.
    • If test Passed: add :white_check_mark:
    • If any issues happen,  add :red_circle:
  • Issue Details (if applicable): If you found a bug, provide a short description and any error messages, screenshots, or reproduction steps.

How to Update RC/Beta Via WP CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. – Demo Video 

For a step-by-step video guide on updating the RC version through WP CLI, watch this demo:

How to Update RC/Beta Via Beta Tester Plugin – Demo Video 

If you prefer using the Beta Tester plugin, here’s a video guide to walk you through the process:

Previous Release Parties 

If you looking to see what happens in Release Party, please checkout recent RC-2 Release Party here

Screenshot of Previous Release Party

Props @krupajnanda and @5um17 for proofreading and peer review.

#core-test

Patrick Lumumba 4:20 pm on September 25, 2024
Tags: core, ,   

Test Chat Summary: 24th September 2024

On Tuesday, September 24, 2024 at 02:00 PM GMT+3, <test-chat> started in #core-test facilitated by @webtechpooja. The agenda can be found here.

1. Attendance

@sumitbagthariya16, @mahbubmr500, @lumiblog, @oglekler, @webtechpooja, @narenin, @ankit-k-gupta, @zunaid321

2. Looking for Volunteer

  • September 24: Test Chat Meeting Recap Notes: @lumiblog 
  • October 1: Test Triage Facilitator : Volunteers Needed
  • October 8: Test Chat Meeting Facilitator: Volunteers Needed 
  • October 8: Test Chat Meeting Recap Notes: Volunteers Needed

3. Call for Nomination for the Test team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.

  • The call for Nomination for the Test team Rep is open for one more week. If you want to nominate yourself or anyone else, you can do so in the next one week here.

4. Announcements 📣

  • Next major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality.: 6.7
    • We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for Tuesday, October 1. The Road Map post can be found here.
  • Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.6.3
    • Following the recent WordPress 6.6.2 release, the next maintenance release (if needed) will be WordPress 6.6.3. There were no updates shared in the meeting.
  • Next 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/ release: 19.2
    • The next Gutenberg release will be 19.2, scheduled for September 11 (this release occurred after the meeting).
  • PDX + WCUS 2024: A Recap: WordCamp US (WCUS), North America’s largest WordPress event, hosted over 1,500 attendees from around the world at the Oregon Convention Center in Portland, from September 17 to 20.
  • We had a contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WCUS, where @ironprogrammer represented the Test Team. If any of you attended the contributor day and want to share something about that, please feel free to share here.

5. Test Team Updates

6. Focal Group Updates

No updates were reported by the members.

7. Questions/Blockers

No questions/blockers were reported by the members. 

8. Call for Testers/Visibility

9. Open Floor

@ankit-k-gupta mentioned that a Test Scrub is scheduled every alternate Tuesday in the #core-test channel. He added that if anyone is interested in speeding up progress on tickets related to the WordPress 6.7 release and wants to lead a test scrub, support and assistance would be provided.

10. Next Meeting 🗓

The next meeting will be on Tuesday, October 8, 2024 at 11.00 UTC, held on #core-test!

#core, #meeting-notes

Patrick Lumumba 8:50 am on August 14, 2024
Tags: core, ,   

Test Chat Summary: 13th August 2024

On Tuesday, August 13, 2024 at 02:00 PM GMT+3, <test-chat> started in #core-test facilitated by @webtechpooja. The agenda can be found here.

1. Attendance

@krupajnanda, @sumitbagthariya16, @webtechpooja, @narenin, @hitendra-chopda, @ankit-k-gupta, @mujuonly, @dhaval59, @hage, @mobarak (async), @lumiblog (async).

2. Looking for Volunteers

  • August 13: Test Chat Meeting Recap Notes: @lumiblog 
  • August 20: Test Triage Facilitator : Volunteer Needed
  • August 27: Test Chat Meeting Facilitator: Volunteer Needed 
  • August 27: Test Chat Meeting Recap Notes: Volunteer Needed

3. Announcements 📣

  • Release related update:
    • We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for Tuesday, October 1.
    • The next maintenance release will be 6.6.2 and will likely be released at the end of the month, likely August 26 with RC1 the week before.
    • 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/ 19.0 is scheduled for August 14. RC1 was released on August 7.
  • A volunteer is required to co-facilitate/assist on Contributor Day at WordCamp US with @ironprogrammer. If anyone is attending WordCamp US 2024 and available to help the test team, please leave your comment here in this thread and you can also contact either @webtechpooja or @ironprogrammer for further discussion.
  • Call for Nomination to select next term Test team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. who will serve for the next 12 months. If you know someone who can take this responsibility, please either comment on this post or reach out to @ankit-k-gupta or @webtechpooja.

4. Test Team Updates

5. Focal Group Updates

6. Questions/Blockers

No questions/blockers were reported by the members. 

7. Open Floor

Nothing from the members.

8. Next Meeting 🗓

The next meeting will be on Tuesday, August 27, 2024 at 11.00 UTC, held on #core-test!

#core, #meeting-notes

Pooja Derashri 6:52 am on June 18, 2024
Tags: core   

Team Chat Agenda: 18 June 2024

Here is the agenda for the upcoming Test Team Chat scheduled for 18 June 2024 at 11:00 UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

  • Attendance
  • Note-taker and facilitator selection for the next meeting
    • This week’s facilitator is – @webtechpooja
    • This week’s note-taker is – Tapan Kumer Das
    • 25 June Test Triage – Volunteer needed
  • Announcements
    • WCEU Summary
    • We are currently in the WordPress 6.6 release cycle. WordPress 6.6 Beta 2 was released on Tuesday, June 11. BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3 will be released today at 16:00 UTC in #core slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.
    • 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/ 18.6 is scheduled for June 19 and will include these issues. This version will NOT be included in the WordPress 6.6 release.
    • Highlights from WordCamp Europe 2024, it’s just concluded on June 13-15 in Torino,, Italy.
  • Badges Awarded
    • @mai21, @akinom500, @mathieulamiotwpmedia, @wilbertschaapmancom, @thabotswana, @thup90, @z1ang, @hugod, @JustTePi, @yahaly, @stefke89, @thabotswana, @martinkrcho, @hugod, @vrajadas
  • Test Team Announcements
  • Focal Group Updates
  • Questions/Blockers
  • Call for testers/visibility:
  • Open Floor
  • Got a topic? Add in comments below, or bring it up live during the chat.

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

Patrick Lumumba 1:21 pm on May 22, 2024
Tags: core, ,   

Test Chat Summary: 21 May 2024

On Tuesday, 21 May 2024 at 14:00 GMT +3, <test-chat> started in #core-test facilitated by @webtechpooja. The agenda can be found here.

Attendance: @webtechpooja, @hitendra-chopda, @oglekler, @lumiblog, @ankit-k-gupta, @hareesh-pillai, @lamarajan, @mukesh27, @sumitbagthariya16, @krupajnanda, @nhrrob, @sumitsingh, @rcreators, @freewebmentor, @kafleg, @huzaifaalmesbah, @hareesh-pillai

1. Looking for Volunteer

  • Triage Facilitator May 28 – needs volunteer
  • Chat meeting Facilitator June 4 – needs volunteer
  • Chat Meeting recap note taker June 4 – @ankit-k-gupta

2. Profile Badge Awards 🎉

Profile badge awarded to harshalkadu, harshalk, Hitendra Chopda, Ramon Ahnert, and Sumit Bagthariya.

3. WCEU 2024 Test Team Table Leads

@boniu91 and @martinkrcho will be our Test Table leads. @krupajnanda and @ankit-k-gupta will be online leads.  A post containing all the information about what and how contributors can help at the WCEU contributor table will be published soon.

The WCEU 2024 Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. will be on June 13 2024. Details can be found here. 

4. Announcements 📣

5. Test Team Updates

6. Focal Group Updates

7. Questions/Blockers

No questions/blockers were reported by the members. 

8. Call for Testers/Visibility

9. Open Floor

@nhrrob mentioned there is a bug scrub happening today for WordPress 6.6 in the #core channel at 14:00 UTC on 21 May 2024. He encouraged beginners to join as it’s a good opportunity to learn about how tickets move forward and what keywords mean. 

@webtechpooja then said they are thinking of starting a test bug scrub for upcoming 6.6 version tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets in the #core-test channel, asking if anyone is interested.

@oglekler expressed interest, saying it would be great with the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 release in 2 weeks and some promising enhancements that need testing, stating “No tests – no go”.

@pbearne shared a trac link with a list of tests waiting to be committed that could be looked at.

@oglekler shared another trac link as a priority for the 2 weeks before beta 1.

@webtechpooja asked if anyone had day/time preferences for scheduling a bug scrub meeting. She also stated focus will be on as many tickets as possible with everyone’s support.

10. Next Meeting 🗓

Next meeting will be on Tuesday, June 4, 2024 at 04:30 PM GMT+5:30, held on #core-test! </test-chat>

If anyone wants to take notes in the next meeting, please feel free to comment in this thread.

#meeting-notes

Ankit K Gupta 3:11 pm on April 24, 2024
Tags: core, , ,   

Test Chat Summary: 23 April 2024

On Tuesday, 23 April 2024 at 16:30 GMT+5:30, <test-chat> started in #core-test facilitated by @sumitsingh. The agenda can be found here.

Attendees: @webtechpooja, @sumitsingh, @huzaifaalmeabah, @hitendra-chopda, @lumiblog, @sumitbagthariya16, @ankit-k-gupta, @krupajnanda, @pooja9712, @nhrrob, @voboghure, @freewebmentor, and @nikitasolanki1812

1. Looking for Volunteer

2. Announcements 📣

3. Test Team Updates

  • Weekly update: Test Team Update
  • Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered. Check out this post and pick any issue mentioned in it.

4. Focal Group Updates

5. Questions/Blockers

Nothing discussed.

6. Call for Testers/Visibility

  • There are currently 15 open tickets in the 6.5.3 release milestone. More information about this release is in this post, including the bug scrub schedule and how you can get involved.
  • 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/ 18.2 is scheduled for April 24 and will include these issues.

7. Open Floor

Nothing discussed.

Next Meeting 🗓

The next scheduled meeting is on Tuesday, April 30, 2024 at 04:30 PM GMT+5:30 for <test-triage> in #core-test.

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#meeting-notes

#core, #core-test, #fse-hallway-hangout, #meeting-notes

Krupa Nanda 6:53 am on April 12, 2024
Tags: core, , ,   

Test Chat Summary: 9 April 2024

On Tuesday, April 9, 2024 at 04:30 PM GMT+5:30, <test-chat> started in #core-test facilitated by @webtechpooja Agenda can be found here.

Attendees: @krupajnanda, @huzaifaalmesbah, @hage, @rahulharkhani, @ankit-k-gupta, @shiponkarmakar, @oglekler, @mujuonly, @semnaveen, @sumitsingh, @hitendra-chopda.

1. Looking for Volunteer

2. Announcements 📣

3. Test Team Updates

  • Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered. Check out this post and pick any issue mentioned in it.
  • Test Team Update: Metrics for overall team progress

4. Focal Group Updates

  • Test Team Profile Badge! – We have almost finalized the criteria for awarding badges. Thanks to @ironprogrammer and @oglekler for their valuable feedback. Thanks to @ankit-k-gupta for working on this.
  • Use a spider to crawl the test website. @nagpai worked on a draft of this at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia. He will be working on pending things during this week.

5. Questions/Blockers

Nothing discussed.

6. Call for testers/visibility

7. Open Floor

  • It was a Hindu New Year and people across India celebrated this day.

Next Meeting 🗓

The next scheduled meeting is on Tuesday, April 23, 2024 at 04:30 PM GMT+5:30 for <test-triage> in #core-test.

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#meeting-notes

Thank you, @webtechpooja, for the peer review and for helping me write this post. 

#core-test, #fse-hallway-hangout, #meeting-notes

Muhibul Haque 6:44 am on February 29, 2024
Tags: core, ,   

Test Chat Summary: 27 February 2024

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 WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Asia Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-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 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 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

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 pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.

@ironprogrammer replied, The update introduces support for new AVIF uploads and auto-conversion upon upload via the ‘image_editor_output_format‘ filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., 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 GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ group WordPress/Outreach that developers can pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” 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

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 (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/).

@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. 

#core-editor-improvement, #meeting-notes