Bug Scrub Schedule for WordPress 6.6

Following sessions are dedicated to move things forward and be ready in time according to 6.6 Release Schedule.

Everyone is welcome to join not only to triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets but also to look for tickets you can contribute by creating patches, making code review and testing.

Things to keep in mind:

  • All features and enhancements should be in the Trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. 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 and most bugs and all strings need to be there before RC1.
  • If you are working on a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing., plan your contribution to have enough time for other contributors to make suggestions, review and test.

Alpha Bug Scrubs

Focus: features, enhancements and then bugs with priority on tickets that are closer to resolution

Beta Bug Scrubs

Focus: rest of the bugs plus reported regressions

Release Candidaterelease 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). Bug Scrubs (if needed)

Focus: issues reported from the previous 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)..

  • TBD

Check this schedule often, as it will change to reflect the latest information.

Regular component scrubs and triage sessions

For your reference, here are some of the recurring sessions:

Have a regular component scrub or triage session?
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.” @nhrrob or @oglekler on 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/. to have it added to this page.

You can start your own triage sessions

  • Decide what you want to work on

6.6 triage session are our priority and moving forward tickets which already are scheduled for the release is most needed task. If you want to lead some of them, they can be added on this schedule.

But if you are interested in particular component or user focus, for example to take care about RTL-tickets, this will be most welcome too.

Especially interested can be the session to scrub old tickets. We are continuously closing new tickets with the same topic in favor of existing ones and because these tickets are looking complicated just because they’re age not, so many contributors are eager to work on them, but there are actual treasures hidden among very difficult or tricky topics.

  • Ping @oglekler or@nhrrob on Slack with the day and time you’re considering, as well as the report or tickets you want to scrub. Note that scrubs are happening in the main coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel and cannot clash with other meetings in this channel.

Useful reports and information

  • Report 5 provides a list of all open 6.6 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 6.6 tickets ordered by workflow.

Need a refresher on bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs? Checkout Leading Bug Scrubs in the core handbook.

#6-6, #bug-scrub, #core

Agenda, Dev Chat, Wednesday May 22, 2024

The next WordPress Developers Chat will take place on  Wednesday May 22, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.

Announcements

The scheduled date for WordPress 6.6 Beta 1 is June 4, which is less than 2 weeks away. From this point on, 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. will focus on testing and fixing bugs discovered during 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. testing. Begin writing Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and the About page (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/. archive, ZIP download).

@ellatrix recently announced that the last 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 to go into WP 6.6 will have an 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). next Friday, May 31.

Forthcoming releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.6

We are currently in the WordPress 6.6 release cycle. See the Roadmap Post for details about what is planned for this release.

Next maintenance release: 6.5.4

@jorbin requested that we discuss the potential of doing a 6.5.4 release to accommodate #61269.

Next Gutenberg release: 18.4

Gutenberg 18.4 is scheduled for release on May 22 and includes these issues.

Discussions

With the Beta 1 deadline quickly approaching, we’ll use the discussion time to check in on priority items for this release. Review the list of Editor Updates section of this agenda for a list of updates of several key features related to this release.

Highlighted posts

Editor updates

Props to @mikachan for putting together a list of editor related updates.

Get involved

Updates

Tickets for assistance

Tickets for 6.6 will be prioritized.

Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting if there are any questions or you will be async.

@vcanales mentioned the following issues in the WordPress 6.6 Editor Tasks board that are up for grabs for developers:

@dmsnell requested that we highlight the following issues:

  • #61009 allows storing the proposed “Bits” syntax, making it possible for experimentation inside Gutenberg.
  • #61052 allows storing custom data attributes containing dashes, which is what the Interactivity APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. relies on.

Open floor

Items for this can be shared in the comments.

Props to @jeffpaul for reviewing.

#agenda, #core, #dev-chat

Performance Chat Agenda: 21 May 2024

Here is the agenda for this week’s performance team meeting scheduled for May 21, 2024 at 15:00 UTC.

  • Announcements
    • Welcome to our new members of #core-performance
    • Performance lab 3.1.0 released yesterday
    • Request for feedback on ideas to improve the Performance Team site. See this issue for discussion
    • Confirmation of the 3.2.0 release date moving to June 3 due to 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. Europe travel
  • Priority items
    • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
      • Current release (6.6)
      • Future release
    • Performance Lab 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 (and other performance plugins) including:
      • Auto-Sizes for Lazy-Loaded Images
      • Embed Optimizer
      • Fetchpriority
      • Image Placeholders
      • Modern Image Formats
      • Optimization Detective
      • Performant Translations
      • Speculative Loading
    • Active priority projects
      • Improve template loading
      • INP research opportunities
      • Improving the calculation of image size attributes
      • Optimized autoloaded options
  • Open floor
    • Frequency of a Performance Lab plugin focused bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub

If you have any topics you’d like to add to this agenda, please add them in the comments below.


This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Summary, Dev Chat, May 15, 2024

Start of the meeting in 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/., facilitated by @annezazu. 🔗 Agenda post.

Announcements

A reminder that the WordPress 6.6 roadmap has been published. Please also read and leave feedback on the Server to client data sharing for Script Modules proposal. Feel free to leave feedback either during Dev Chat or on the proposal post.

Forthcoming Releases

We’re currently in the WordPress 6.6 release cycle. You can find out more about the release squad in this post.

@annezazu noted that after a discussion in the public #6-6-release-leads channel, there is an update underway for the remaining roles yet to be filled. This has now been posted here.

For any folks who want to learn more about the release and help contribute back, I want to call attention to this post on Early opportunities to Test WordPress 6.6. Help the release and learn about it at the same time!

Discussion

Release Squad: A lengthy discussion ensued about the fact that 3 weeks from 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 that the full release squad has not been filled. There were questions about why this release has been so hard to fill and what we could do to improve this in the future. Some questioned the size of the release squad making it difficult to fill and others questioned the length of the cycle. Suggestions were made to try to recruit a release squad earlier in the cycle, or even at the end of the previous cycle.

Note: Since the meeting, the WordPress 6.6 release squad is ready.

Canonical 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. plugins proposal: There is an initial issue and discussion here, and a follow-up Gutenberg PR is currently in progress to create a time to read block. Have folks had a chance to catch up here? Any questions or concerns?

  • @jeffpaul questioned what problem this would solve compared with either shipping these blocks in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. or allow them to be maintained as community plugins.
  • @jorbin expressed support for the idea, but identified that there were some questions that need to be answered in addition to what @grantmkin shared in this GitHub comment.
  • @annezazu shared that the difference is useful in that some blocks haven’t been a great fit for Core, for a variety of reasons. This separation allows the base experience to remain the same while offering strong, supported blocks provided by Core that folks can add on.
  • This was a lengthy discussion. Everyone is encouraged to provide feedback on the related issue.

Proposal: Server to client data sharing for Script Modules: This proposal is still looking for feedback.

Open Floor

@kkmuffme requested guidance on several tickets that have stalled, that he is hoping will get picked up in time for the 6.6 release. Following the meeting, @jeffpaul scrubbed the list and pinged relevant core developers who might be able to review and provide feedback.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Props to @mikachan for proofreading.

#6-6, #core, #dev-chat, #summary

WordPress 6.6 release squad ready

This post is a follow-up to the WordPress 6.6 call for volunteers update.

I’m glad to announce the WordPress 6.6 release squad is ready and the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and Documentation lead roles have been filled:

Big thanks to everybody who volunteered to the release squad or to mentor and support!


Thanks to @chanthaboune for reviewing this post.

#6-6 #planning

Agenda, Dev Chat, Wednesday May 15, 2024

The next WordPress Developers Chat will take place on  Wednesday May 15, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.

Announcements

A reminder that the WordPress 6.6 roadmap has been published. Please also read and leave feedback on the Server to client data sharing for Script Modules proposal. Feel free to leave feedback either during Dev Chat or on the proposal post.

Forthcoming releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.6

We are currently in the WordPress 6.6 release cycle.

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: 18.4

Gutenberg 18.4 is scheduled for release on May 22 and includes these issues.

Discussions

This week, we will continue to discuss the Roadmap for the WordPress 6.6 release cycle, in case anyone has any questions or would like to chat about any of the proposed features, including:

If we have time, we can also discuss the canonical 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. plugins proposal. There is an initial issue and discussion here, and a follow-up Gutenberg PR is currently in progress.

Feel free to suggest additional topics in the comments.

Highlighted posts

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Updates

Props to @annezazu for putting together these updates.

Get involved:

Updates:

    Tickets for assistance

    Tickets for 6.6 will be prioritized.

    Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting if there are any questions or you will be async.

    Open floor

    Items for this can be shared in the comments.

    Props to @joemcgill for reviewing.

    #agenda, #core, #dev-chat

    Performance Chat Summary: 7 May 2024

    Meeting agenda here and the full chat log is available beginning here on Slack.

    Announcements

    • Welcome to our new members of #core-performance
    • Performance lab 3.1.0 release scheduled for May 20

    Priority Items

    Structure:

    • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
      • Current release (WP 6.6)
    • Performance Lab 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 (and other performance plugins)
    • Active priority projects
      • Improve template loading
      • INP research opportunities
      • Improving the calculation of image size attributes
      • Optimized autoloaded options

    WordPress Performance Trac Tickets

    • For WordPress 6.6:
      • @adamsilverstein only 14 tickets milestoned for 6.6 in the performance focus,  the bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs have been effective at keeping tickets moving
      • @spacedmonkey I would consider adding my ticketticket Created for both bug reports and feature development on the bug tracker. for loading multiple networknetwork (versus site, blog) options at once. I am hoping to get #61053 into this release.
        • @pbearne That would a good add, and we can it to the Dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.
      • @westonruter Happy to share that post embeds will now get lazy-loaded in 6.6 where previously they were excluded. This was committed yesterday https://core.trac.wordpress.org/changeset/58143

    Performance Lab Plugin (and other Performance Plugins)

    • Performance lab plugin and the following performance plugins:
      • Auto-sizes for Lazy-loaded Images
      • Embed Optimizer
      • Fetchpriority
      • Image Placeholders
      • Modern Image Formats
      • Optimization Detective (Developer Preview)
      • Performant Translations
      • Speculative Loading

    • Modern images: @adamsilverstein for modern images work has continued on adding AVIF support, that is very close to ready – https://github.com/WordPress/performance/pull/1176
    • @ashwinparthasarathi Worked on a couple of features and PRs are underway,
    • @benoitfouc AVIF is now mainly supported, i’m agree with this proposition
      • @adamsilverstein supported in all browsers, however only ~30% of WordPress sites have the server support they need to upload AVIFs (and generate srcset images)
      • @benoitfouc is there a way to control this support on the plugin? Using WebP by default when the server do not support AVIF
      • @westonruter Yes, that’s how it works. And there is a user option to decide which format when AVIF is available
    • @adamsilverstein that would be my preference. then, what happens if users are already outputting WebP, does that change automatically to AVIF when they upgrade the plugin, or do they need to go in and change the output setting?
      • One thing we are trying to decide on that PR is haw to handle the default settings – especially for users who upgrade from the current version
    • @westonruter Would anyone be explicitly wanting WebP instead of AVIF, I guess the question is. Adam suggested doing a major version bump from 1.x to 2 as a signal for this significant change. Might be sufficient as a way to alert users that their attention may be needed. Otherwise, I guess an adminadmin (and super admin) pointer could be added, but that seems noisy. Maybe add an Upgrade Notice in the readme as well?
      • Agreement reached:
      • Going back up to @ashwinparthasarathi PR https://github.com/WordPress/performance/pull/1208 to improve visibility of the features’ Settings screens, take a look at the last comment on the PR. How about adding a link to the settings in the activation notice? “Feature activated. Review settings.”
      • Where settings is a link to the relevant settings screen. A settings link also appears with each feature once activated, but the thinking is that the user may not notice this appear all of a sudden
    • @ashwinparthasarathi yes, it makes sense, and I will make the changes to include it in the Activation notice. I also thought that your earlier idea to make those settings links more visible is a good one. I think if we could make it stand out, it’ll work.
    • @westonruter for Speculative Loading: Whether we should go ahead and prevent speculative loading for logged-in users (and when PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher sessions are being used): https://github.com/WordPress/performance/pull/1178
      • After thinking about it some more, I wonder if it may be premature to add this as we haven’t had any reports in the wild of this being a problem. The one user who reported it did so as part of an overall set of suggestions.
      • Perhaps we sit on this awhile longer to bake
      • There could also be a new setting we could add for turning off speculative loading for logged-in users. But ideally we’d be able to make a decision and not add to the user’s set of tasks. Although there are currently pretty low-level settings for prefetch vs prerender already, so maybe this isn’t a big deal for a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. as we figure out what makes sense for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
      • Oh, I stand corrected, one user did report wanting to be able to disable speculative loading this in the support forumSupport Forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations.https://wordpress.org/support/topic/sl-lsc/#post-17699897

    Active Priority Projects

    Improve template loading

    • @thekt12 Last week I worked on feedback from #59595 and also worked on it’s unittest, just a few more checks and I should be able to give it for review today. I’ll resume back #57789

    INP research opportunities

    Improving the calculation of image size attributes

    Optimized autoloaded options

    • No updates this week

    Open Floor

    • @benoitfouc i want to know if somebody are interesting about working on this PR : https://github.com/WordPress/performance/issues/371 This PR make sens, and is on the same way that the new version of Modern Images Formats plugin
    • @clarkeemily I think last week one suggestion was made to have a bug scrub specifically for the Performance Lab plugin – wondered if folks were in favor of this in principle, then we can perhaps work to define the scheduling etc later

    Our next chat will be held on Tuesday, May 21, 2024 at 15:00 UTC in the #core-performance channel in Slack.

    #core-performance, #performance, #performance-chat, #summary

    Performance Chat Agenda: 14 May 2024

    Here is the agenda for this week’s performance team meeting scheduled for May 14, 2024 at 15:00 UTC.

    • Announcements
      • Welcome to our new members of #core-performance
      • Performance lab 3.1.0 release scheduled for May 20
    • Priority items
      • WordPress performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
        • Current release (6.6)
        • Future release
      • Performance Lab 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 (and other performance plugins)
      • Active priority projects
        • Improve template loading
        • INP research opportunities
        • Improving the calculation of image size attributes
        • Optimized autoloaded options
    • Open floor

    If you have any topics you’d like to add to this agenda, please add them in the comments below.


    This meeting happens in the #core-performance channel. To join the meeting, you’ll need an account on the Make WordPress Slack.

    #agenda, #meeting, #performance, #performance-chat

    Summary, Dev Chat, May 8, 2024

    Start of the meeting in 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/., facilitated by @joemcgill. 🔗 Agenda post.

    Announcements

    The WordPress 6.6 roadmap has been published.

    WordPress 6.5.3 was released on Tuesday, May 7. This 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. features 12 bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 9 bug fixes for the 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. editor. You can review a summary of the maintenance updates in this release by reading the Release Candidate announcement.

    Gutenberg 18.3 was released on Wednesday, May 8. The release highlights include a full page client-side navigation experiment, negative values for margin controls, and adding a publish flow to the editor.

    Forthcoming Releases

    We are currently in the WordPress 6.6 release cycle and 4 weeks away from 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. The latest update on the release squad is detailed in this post and there are a few TBD roles for Core triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and Docs leads. During the meeting, @OGlekler volunteered to be Core Triage Lead for 6.6. @priethor also followed up with a note to say:

    • Would the Core Triage role benefit from a second lead?
    • The Docs lead role is nearly ready too.

    @jorbin confirmed that 6.5.3 came out on May 7. Thank you to everyone who helped. We now need to consider whether we should plan a 6.5.4. As of now, there is one potential regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. that is being investigated, so @jorbin suggested that we give it one to two weeks before making a decision. The 6.5.4 milestone has already been added in tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

    @annezazu noted that the only other feedback is around this: https://github.com/WordPress/gutenberg/issues/59511: There’s been some feedback from an enterprise client as they can no longer change titles easily. The problem is there’s not an intermediate solution in the works and it will be resolved by 6.6 when the site editor pattern experience comes to classic themes. This will be discussed further in #6-5-release-leads.

    Discussion

    Here are a couple of follow-ups from previous meetings:

    • New slack channels: #core-interactivity-api was created to help folks working there better organize and collaborate.
    • 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/ commits: as a way to bring additional visibility to changes committed in the Gutenberg repo, we’ve started an experiment to show commits to the trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". (PR merges) in the #core channel.

    We dedicated a lot of discussion time to the 6.6 roadmap and any updates about the major efforts listed on the Roadmap.

    @afragen gave an update about Rollback Auto-Update: there have been zero reported issues with the PR. We’re currently just looking at making some of the comments a bit more descriptive. Hopefully Rollback Auto-Update will be committed in the next day or so.

    @johnbillion raised #61173: if anyone wants to help with that workflow that would be great.

    Open Floor

    @azaozz requested for “more eyes” and reviews on https://github.com/WordPress/wordpress-develop/pull/6407#issuecomment-2101275000. This is a PR that properly fixes the infinite loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. as reported on #60652 (the current patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. just hides it, that PR removes the possibility for a loop to happen). It also fixes the possibility for 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 to completely remove the new font_dir 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. which is a pretty nasty thing to do and would break all other plugins that are using that filter.

    @kkmuffme requested some final reviews on the following PRs:

    @grantmkin also noted: @vcanales and I have started exploring “canonical block plugins,” an idea to have more community developed blocks that are shipped as stand-alone block plugins, for blocks that aren’t a fit in the default block library shipped with Gutenberg/WordPress. The primary issue is at https://github.com/WordPress/gutenberg/issues/58773, in case you’d like to learn more about, follow, discuss, or contribute to the effort. There will likely be a follow-up on make/core to get more feedback.

    Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

    Props to @joemcgill for proofreading.

    #6-6, #core, #dev-chat, #summary

    Core Editor Improvement: Upgrade your designs

    These “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvement tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects. 

    Important design tools have shipped in the last few 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/ releases, with additional ways to take advantage of the creative flexibility already available with 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. themes. Here’s a closer look at what these tools unlock ahead of the next major WordPress release.

    Mix & match style variations

    Style variations bundled with block themes allow you to seamlessly transform your site’s look and feel fast, all while using the same theme. Now, you can mix and match the color and typography styles of each style variation—a powerful upgrade to the existing functionality. For example, take the Twenty Twenty-Four Theme, which launched with eight carefully curated, community-created style variations. These included six typography presets and eight color presets. With this recent PR available since Gutenberg 17.9, you now have 48 combinations to choose from. You can stick with the original options defined by the theme author or add your own typography choices through the Font Library. As a bonus, this option works for any existing block themes with style variations—no additional configuration needed!

    You can use this Playground instance to dive in and try it yourself. Going forward, there are some technical details to iron out, along with potentially evolving the experience to better support themes with a large set of variations. For a greater view of this general area, dive into the Colors and typeset presets from theme style variations overview issue and see the latest. 

    Create overlapping designs with negative margins

    Previously, you could only create overlapping designs with negative margins. As of Gutenberg 18.3, you can add negative margins right in the Site Editor for all blocks that support margin controls. The negative values need to be manually entered to balance some UXUX User experience considerations and add some guardrails, meaning they can’t be selected by dragging. 

    Want to share something you create with this new option in the next WordPress release? Share it in the Pattern Directory! For now, enjoy exploring.

    Embrace the Grid

    Grid is a new layout variation for the Group block stabilized in Gutenberg 17.8 that allows you to display the blocks within the group using CSSCSS Cascading Style Sheets. grid. Of note, any block can use this new grid layout thanks to the supports key in block.json. There are two options for the grid layout:

    • “Auto” generates the grid rows and columns automatically using a minimum width for each item. 
    • “Manual” lets you specify the exact number of columns.

    This is just the beginning. Efforts are underway to let you drag and drop, andresize blocks on the grid, providing a more visual and intuitive experience. Work is also in progress to improve how folks create layouts in general. If you want to follow how this feature evolves, check out this tracking issue, watch the recent demo, and join the dedicated #feature-grid 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. 

    Thanks to @richtabor and @laurlittle for help with editing this post.

    #core-editor, #core-editor-improvement, #gutenberg