Brian Alexander 7:44 pm on August 5, 2023
Tags: , , , ,   

Dev Chat Summary, August 2, 2023

The WordPress Developers Chat meeting took place on August 2, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Announcements

Highlighted Posts

Here’s an overview of updates in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between July 24 and July 31, 2023:

  • 21 commits
  • 40 contributors
  • 64 tickets created
  • 12 tickets reopened
  • 39 tickets closed
  • Synced Patterns: The Evolution of Reusable Blocks: New pattern functionality with WordPress 6.3.
  • Whose ticket is it, anyway?: Follow-up post to last week’s DevChat discussion about ticketticket Created for both bug reports and feature development on the bug tracker. ownership. Share your thoughts and opinions by September 1, 2023.
  • Proposal: improve the editor tech workflow for major releases: Ideas for improvements to ease the pain points of merging code from 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/ into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., particularly before 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. This proposal has already generated a lot of favorable consensus to experiment with this approach in the 6.4 cycle.
  • This proposal has been adopted: Proposal: Criteria for Removing “Beta Support” from Each PHP 8+ Version. Involved contributors are currently in the process of:
    • working through the action items list.
    • evaluating the list of incompatibilities for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.0 and 8.1 for WordPress 6.3.

Release Updates

WordPress 6.3

@hellofromtonya asked if Trac #58940 – site-health.php page Fatal error on version: 6.3-RC2 would require another RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). release. It was confirmed that the ticket was opened before RC 3, but not fixed in that release. @jeffpaul and @audrasjb agreed that another RC may be warranted, and would check other tickets that remain in the 6.3 milestone (or same query grouped by workflow).

WordPress 6.4

@hellofromtonya indicated that work was underway on 6.4 early tickets.

@chanthaboune noted that wishlist items were being gathered, and that 6.4 release coordinators would be able to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. these earlier than is typical, since the 6.4 release cycle is shorter than normal. Of particular note was consideration of items requiring additional dev, design, or a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) attention before committing them to the release.

Maintainers: Component Help Requests

@craigfrancis asked for attention on Trac #54042 – Extending wpdb::prepare() to support IN() operator, and consideration for 6.4 early designation. He asked for review and thoughts/suggestions on improving the existing patches.

Open Floor

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/. Core/Core-* Tables

@desrosj related questions he’d received regarding how Core tables are often spread out at Contributor Day, which can be confusing for both new and experienced Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. who wish to move between tables, especially for collaboration with other focus teams. @webcommsat agreed that it would be beneficial to locate them closely together, to avoid the issue of contributors getting confused and dropping out of the event.

@desrosj also asked if there were any volunteers from the #core-performance and #core-editor channels who would be willing to lead their respective tables at WCUS. @hellofromtonya suggested posing the question to each team’s Slack channel. @joemcgill raised his hand for helping at the Core Performance table.

PHP 8.3

@hellofromtonya shared that initial impressions concerning PHP 8.3 are that it would have a low impact to Core. PHP 8.3’s release date is scheduled for November 23, 2023.

Next Meeting

The next meeting will be on August 9, 2023 at 20:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel.

#6-3, #6-4, #dev-chat, #meeting, #summary