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

What’s new in Gutenberg 18.3? (8 May)

“What’s new in 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/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor.


Gutenberg 18.3 has been released and is available for download!

A special welcome to three new first time contributors!

The latest release includes 157 pull requests from 44 contributors, and generally focuses on polishing features, and addressing bugs. Significant activity has also been directed towards improving documentation and code quality.

In this issue:

Full page client-side navigation experiment

As part of continuing to bring a single page application experience to WP sites, this change enables an experimental setting for whole-DOM-replacement on the client navigating between different pages without the need for a full page refresh.  Previously this was only available for region-based replacement. (#59707)

Allow negative values for margin controls

Negative margin values can now be added directly in the editing experience, resolving a longstanding feature requestfeature request A feature request should generally begin the process in the ideas forum, on a mailing list, as a plugin, or brought to the attention of the core team, such as through scope meetings held for each major release. Unsolicited tickets of this variety are typically, therefore, discouraged. and matching the current theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. support. This expands the design options for users leveraging the Editor. (#60347)

Add defaultFontSizes option to theme.json (incrementing theme.json to v3)

A previous attempt at adding the ability to add a defaultFontSizes option to theme.json didn’t stick (#56661) and this change reintroduces that ability.  Because the default behavior of overriding font sizes has changed this has caused the version of theme.json to increment to version 3.  (See this comment for more details.) Now defaultFontSizes can be set to false in theme.json to disable showing the default font sizes supplied from Gutenberg. (#58409)

Add publish flow in site editor

This continues the work on unifying the publishing flow between post and site editors and adds to the site editor the publish/save button that is used in post editor. This means we have the same publishing flow between the two editors. (#61136)

Other Notable Highlights

  • The Zoom Out Mode got some love:
    • Insert patterns at the end of the root section (#60855)
    • Make the zoom out inserters work for sections inside the section root (#60909)
    • Don’t show appender at all inside sections on zoom-out mode (#60948)
    • Drop patterns and blocks between sections only in zoom out mode (#60828)
  • In the Post Editor we moved around word count, post status and last edited info in page summary (#61235)
  • Bumped the required WordPress version to 6.4 and tested up to to 6.5. (#60780)

Changelog

Full changelog Available

Enhancements

  • Output post classes in the editor. (60642)
  • Abstract keyboard shortcuts for heading to paragraph transform and vice-versa. (60606)
  • Capitalize more occurrences of Navigation MenuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site.. (60747)
  • Clean up top toolbar to use same metrics as 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. toolbar. (61126)
  • Update template and template parts labels. (61146)
  • Update the template preview menu item text in the Template option. (57802)
  • Upgrade ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. to v18.3. (61202)

Site Editor

  • Add PluginDocumentSettingPanel in template inspector controls. (60961)
  • Add publish flow in site editor. (61136)
  • Classic Theme: Expose new Patterns page and remove Template Parts submenu. (61080)
  • Consolidate editor/canvas resize handles. (60712)
  • Patterns data view: Remove icons in favor of dedicated sync status field. (60833)
  • Patterns: Remove “Manage all parts” page & link. (60689)
  • Tweak Template/Template Parts/Page creation modal. (61005)
  • Drop patterns and blocks between sections only in zoom out mode. (60828)
  • Insert patterns at the end of the root section. (60855)
  • Typography Panel: Use simple labels. (60886)
  • Font Library: Convert heading text to heading elements and group fonts as a list. (58834)

Block Editor

  • Add new TextAlignmentControl component. (60841)
  • Editor: Sort style overrides by block client ids. (61039)
  • Inserter: Bail early when a user has no permission to upload media. (60983)
  • List View: Use ‘isMatch’ for unselect the shortcut. (61223)
  • Move search into inserter tabs. (61108)
  • Polish Autocomplete popover. (60131)

Global Styles

  • Add scoping of feature level selectors for custom block style variations. (61033)
  • Allow negative values for margin controls. (60347)
  • Allow opt out of certain sets of styles in the editor. (61035)
  • 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. out color and typography variations. (60220)
  • Update utils for scoping CSSCSS Cascading Style Sheets. selectors. (61026)
  • Add defaultFontSizes theme.json (theme.json v3). (58409)

Block Library

  • Group: Remove hardcoded Group block example styles. (61027)
  • Remove Button component from social link block, replace with button element. (61270)
  • List View: Unify shortcut handlers. (61130)
  • Update list view spacing. (60713)

Post Editor

  • Editor: Move around word count, post status and last edited info in page summary. (61235)
  • Editor: Update post excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. panel with new designs. (60894)
  • Add duplicate post action. (60637)
  • Make duplicate post action available only on the 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 for now. (61192)

Data Views

  • Unbox items in grid layout. (61159)
  • Update alignment of preview contents in Patterns and Templates data views. (61190)

Components

  • ComboboxControl: Simplify string normalization. (60893)
  • Update help text alignment in CheckboxControl. (60787)
  • RangeControl: Remove deprecated reducedMotion util. (61119)
  • components – inputStyleNeutral: Remove deprecated reducedMotion util. (61122)

Bug Fixes

  • Editor: Do not show scrollbars when closing sidebars. (60889)
  • Fix block tab spacing when few available blocks. (61296)
  • Fix pattern preview focus styles. (60881)
  • Fix styles panel headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes.. (61319)
  • Fix typo in clear customizations text. (61089)
  • Fix: Missing format, categories, and tags on the duplicate post action. (61194)
  • Fix: Post actions in post card panel is not checking for eligibility. (60994)
  • Notices: Fix snackbar placement. (60912)
  • Setup Node action – Set arch for key value. (61010)
  • docgen: Fix qualified types with type parameters. (61097)
  • Background image: Tools panel shouldn’t show reset button for inherited values. (61304)
  • Fix template files query by post-type. (61244)
  • Remove unnecessary period in template block selection notice. (61087)
  • Fix issue where pattern override values reset when saving. (61023)
  • Blocks: Merge variations bootstrapped from a server with the client definitions. (60832)
  • Bump minimum required WordPress version to 6.4. (60780)

Site Editor

  • DocumentBar: Account for when top toolbar is open. (61118)
  • Don’t show appender at all inside sections on zoom-out mode. (60948)
  • Editor: Avoid triggering the start page modal on unsaved pages. (61082)
  • Fix zoom out mode background color on Safari. (60873)
  • Fix: Pattern details page backpath. (61174)
  • Make the zoom out inserters work for sections inside the section root. (60909)
  • Select last section if parent section doesn’t exist. (61002)

Components

  • Box Control: Fix issue with negative values. (60984)
  • Fix usages of uSES with missing getServerSnapshot. (60943)

Block Library

  • Avoid unnecessary heading level and paragraph transform via keyboard shortcuts. (60955)
  • Navigation: Remove unnecessary __experimentalStyle. (60965)

AccessibilityAccessibility 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)

  • Add aria-haspopup=”dialog” to Enable/Disable overrides button. (61309)
  • Fix unlabeled PostURL Copy button. (61195)
  • [Data Views] User patterns: Use excerpt as description. (60549)

Performance

  • Block lib: columns: Remove store subs on mount. (61123)
  • Block: Remove outline related store selecting. (61139)
  • Rich text: Combine all ref effects. (60936)
  • Template lock: Batch block disabling. (60934)
  • useBlockSync: Avoid replacing blocks twice on mount. (60967)
  • useMatchMedia: Cache queries. (61000)
  • ListViewBlock: Combine ‘useSelect’ hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., part two. (61054)
  • Remove showFixedToolbar from useShowBlockTools. (60717)
  • Editor: Optimize some of the post-support panels. (61003)
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. data: getEditedEntityRecord: Do not return empty object. (60988)
  • Drop zone: Avoid media query on mount. (60546)
  • Nav link: Use rich text value. (60503)

Experiments

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.

  • Add full page client-side navigation experiment setting. (59707)

Documentation

  • Add AutosaveMonitor component JSDoc enhancements. (60905)
  • Add Documentation for CharacterCount component. (60906)
  • Add EditorSnackbars component documentation. (61110)
  • Add documentation for DocumentOutline and DocumentOutlineCheck components. (61129)
  • Add documentation for EditorHistoryRedo and EditorHistoryUndo. (60932)
  • Add documentation for EditorKeyboardShortcuts and EditorKeyboardShortcutsRegister. (60933)
  • Add documentation for PostAuthor, PostAuthorCheck, PostAuthorPanel components. (61090)
  • Added doc for components PageAttributesCheck, PageAttributesPanel, PageAttributesOrder, PageAttributesParent. (60977)
  • Change the name of the Interactivity API quick start guide markdown file. (61198)
  • Docs: Fix import statement of PluginMoreMenuItem. (60931)
  • Docs: Handle “oneOf” in theme.json schema doc generation. (61024)
  • Fix import in block editor’s readme example. (61218)
  • Fix use local version of theme.json schema in bundled files. (61312)
  • FontSizerPicker: Improve documentation for default units. (60996)
  • InputControl: Added password visibility story. (60898)
  • Move iAPI documentation from package to reference guides. (61143)
  • Refresh the folder structure documentation page. (60953)
  • Small-typo-change. (61178)
  • Theme JSON: Backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher annotations from Core. (61301)
  • Update an anchor link in block-in-the-editor.md. (59527)
  • Update block-deprecation.md. (60768)
  • Update documentation for theme.json version 3. (61221)
  • Update main readme file with relevant current information. (60942)

Code Quality

  • DataViews: Enable types. (61185)
  • Editor: Cleanup edit-post classnames and documentation. (61240)
  • Editor: Consistently deprecate edit-post and edit-site slots. (61134)
  • Editor: Unify the BlockContextualToolbar component between post and site editors. (61104)
  • Editor: Unify the more menu. (60910)
  • Editor: Unify the region navigation keyboard shortcuts. (60907)
  • Fix: Actions moved to the editor package still reference edit-site on their ids. (60899)
  • Remove unnecessary usesContext from paragraph block. (61008)
  • Removed Extra Space Before Since. (60918)
  • ToolsMoreMenuGroup: Remove form post editor. (61132)
  • Unify placeholders. (59275)
  • Use math.div for scss division. (61285)
  • useBlockProps: Remove dead code. (61133)
  • useBlockSync: Just testing without isControlled effect. (61114)
  • Add eslint autofix commit to ignored git commits. (61253)
  • Rephrasing for accuracy and link to Core TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker.. (61284)
  • Blocks: Add a warning when registering variation without a name. (61037)
  • DataViews: Cleanup unused type property. (61197)
  • DataViews: More dataviews types. (61193)
  • Quality: Fix php warning error. (61321)
  • UseLocation instead of window.location.href. (61230)
  • Use contentOnly locking for pattern block. (61227)
  • Editor: No need to memorize callback in ‘SwapTemplateButton’. (61049)
  • Improve data-wp-context debugging by validating it as a stringified JSON Object. (61045)
  • Theme JSON: Extract util to get valid block style variations. (61030)
  • Elements: Deprecate old block support filter callbacks. (59538)

Components

  • AlignmentMatrixControl: Remove deprecated reducedMotion util. (61113)
  • FocalPointPicker: Remove deprecated reducedMotion util. (61116)
  • Navigation: Remove deprecated reducedMotion util. (61117)
  • Remove “experimental” designation for CustomSelectControlV2. (61078)
  • ToggleGroupControl: Remove deprecated reducedMotion util. (61120)
  • View: Fix TypeScript types. (60919)
  • components/elevation: Remove deprecated reducedMotion util. (61115)

Block Editor

  • Convert Media Inserter to Tabs Pattern. (60970)
  • Obviate mousetrap around Navigation Link popover. (61050)
  • editPost: Deprecate __experimentalPluginPostExcerpt. (61188)
  • editPost: __experimentalPluginPostExcerpt return <PluginPostExcerpt />. (61238)
  • useBlockRefs: Use more efficient lookup map, use uSES. (60945)
  • withBlockTree: Simplify code that replaces/removes controlled blocks. (61234)

Tools

  • ESLint Plugin: Handle multi-line translator comments. (61096)

Testing

  • Components: Fix snapshot tests of ToggleGroupControl. (61228)
  • Fix ESLint warning in Performance test files. (61311)
  • Hotfix: Fixed failing snapshot test. (61274)
  • Update 3rd party actions within composite action. (61211)

Build Tooling

  • Remove block-editor package usage from components. (60999)
  • lint-staged-typecheck: Don’t run TSC when no TS project is affected. (60998)

First time contributors

The following PRs were merged by first time contributors:

Contributors

The following contributors merged PRs in this release:

@aaronrobertshaw @afercia @ajlende @carolinan @cbravobernal @colorful-tones @DaniGuardiola @desrosj @draganescu @ellatrix @fabiankaegy @fullofcaffeine @geriux @huubl @itzmekhokan @jameskoster @jasmussen @jeryj @jorgefilipecosta @jsnajdr @juanfra @juanmaguitar @lanresmith @MaggieCabrera @Mamaduka @mirka @ntsekouras @oandregal @ockham @ramonjd @retrofox @richtabor @SantosGuillamot @scruffian @shail-mehta @sirreal @stokesman @sunil25393 @swissspidy @t-hamano @talldan @twstokes @tyxla @youknowriad

#block-editor#core-editor#gutenberg#gutenberg-new

#gutenberg-new

Performance Chat Agenda: 7 May 2024

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

  • Announcements
  • 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

Developer Blog editorial meeting summary, May 2, 2024

Summary of the WordPress Developer Blogblog (versus network, site) meeting, which took place in the  #core-dev-blog channel on the Make WordPress 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/.. Start of the meeting in Slack.

Attendees: @greenshady, @ironnysh, @ndiego, @milana_cap @bph (as facilitator). @bcworkz and @webcommsat (async)

Last meeting notes: Developer Blog editorial meeting summary, April 4, 2024

Updates on the site

Congrats to our new contributors to get their Documentation Contributor badges: @jsnajdr @beafialho @magdalenapaciorek @ironnysh @jonsurrell @luisherranz @cbravobernal and @flexseth

Newly published post since the last meeting: 

Since the last meeting, we published articles by new writers and received support from more reviewers. (see above)

Huge Thank you to the writer and reviewers! 

Project Status

The project board for Developer Blog content is on 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/.

In Progress:

Post on the To-do-list, assigned to writers.

Topics, approved in in need of a writer

If you are interested in taking on a topic from this list or know someone who would be a good person to write about them, comment on the Issue or 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.” @bph in slack either in the #core-dev-blog channel or in a DM.

Topics closed

  • Learnings from two Site Migrations After consulting Jasmine, it was clear that her idea wasn’t suitable for the developer blog. I offered to assist her to publish some place else.

New Topics approved

Topics not approved:

There were no clear approval signals, and it seems the topics still need to narrow down the proposal to clear problem statements and suggested solutions. The discussions continue.

Open Floor

Next meeting: Jun 6, 2024, at 13:00 UTC in the #core-dev-blog channel

Props to @greenshady for review of the post.

#meeting, #meta, #summary

Data Liberation: Outreach recap and updates

Over the last 2 months I’ve been reaching out and talking to folks in the community about the Data Liberation project. I want to say thank you to all those who provided feedback and input in survey responses, 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/., emails, Zoom meetings, and in person.

From that feedback here are a few trends and insights I would like to share:

  • One of the biggest challenges when migrating to WordPress is the handling of content as it is transformed to Blocks. Validating 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. markup is tricky (as it happens on the client side) particularly when third party platforms may have malformed or custom HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers..
  • Although there is always room for improvement, the WordPress -> WordPress migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. space is well served by plugins and tools like WPCLI.
  • There is lots of interest in how to handle the importing of custom fields and post metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress..
  • Folks agree philosophically with better, more usable exports from WordPress.

Key Principles

Based on the feedback and discussion so far – I wanted to highlight some key principles for the project as we move forward.

Data Liberation starts as 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

In terms of the initial delivery method – a plugin is where we will start. This existing proposal includes prototype plugin that detects the platform of a site and utilizes existing user guides to prompt the user through the migration process (using the ‘Tour’ functionality found on other Make P2s).

This plugin can provide a great base for us to guide users through the steps, and to the tools they need to migrate.

Playground plays a vital role

Leaning into the power and flexibility of  WordPress Playground is a fantastic opportunity. It brings the potential of previewing a migration without impacting your existing site,or even if you don’t have a WordPress site at all yet!

Transforming HTML to Blocks is the path forward

Improving the way HTML is converted into blocks and validates brings advantages across all kinds of migrations. Whether provided in an import file, or scraped from platforms that don’t provide an export – transforming HTML into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks is what will help us free user’s content.

Content Portability is the primary goal

The aim of any Data Liberation solution is to allow users to do what they want with their own content. Whilst any efforts to include appearance and styling, in order to achieve visual parity, are a bonus – the key goal is portability of the content itself.

Better export is important (but comes next)

Philosophically, any effort of Data Liberation needs to consider exporting content from WordPress as well as importing. There are definite improvements we will work towards here – but this will be something that we work on in the future after first improving importing.

With these principles to guide us – our next step (stay tuned) is a defined plan for the project.

WordPress 6.5.3 RC1 is now available

WordPress 6.5.3 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release:

  • Use 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
    • As this is a minor 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, select the Point Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use 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/ to test: wp core update https://wordpress.org/wordpress-6.5.3-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.5.3 RC1 features 11 fixes in Core as well as 8 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.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

The following block editor issues from 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/ are fixed:

  • #60489 – Layout: Skip outputting base layout rules that reference content or wide sizes if no layout sizes exist
  • #60620 – Fix inserter pattern pagination focus loss
  • #60608 – Fix static posts page setting resolved template
  • #60641 – Font Library: Fix modal scrollbar
  • #60661 – 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.: Allow multiple event handlers for the same type with data-wp-on.
  • #60668 – Layout: Always add semantic classes
  • #60845 – List View: Fix stuck dragging mode in UIUI User interface in Firefox when dealing with deeply nested lists
  • #60764 – Don’t output base flow and constrained layout rules on themes without theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.

What’s next?

The dev-reviewed workflow (double committer sign-off) is now in effect when making changes to the 6.5 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"..

The final release is expected on Tuesday, May 7th, 2024. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ 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/. #6-5-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

Thanks to @grantmkin, @hellofromtonya for pre-publication review and @davidbaumwald @desrosj for RC package assistance.

#6-5, #6-5-x, #minor-releases, #releases

Summary, Dev Chat, May 1, 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.5 retrospective survey is now closed. Thank you to everyone who responded! Expect a follow-up post with collected, anonymized results once @priethor@marybaum, and @akshayar have finished processing all of 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/ 18.2 was released on April 24. Read about what’s new in this release.

The remaining Phase 3 related overview issues were created for folks to join Phase 3: Block LibraryPhase 3: WorkflowsPhase 3: Revisions, and Phase 3: Collaboration index. Thanks to everyone who worked on creating and updating these Phase 3 issues!

Forthcoming Releases

We’re in the 6.6 release cycle. @annezazu shared that the roadmap draft is well underway, and @ella has already created this tracking issue to coordinate PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher backports.

@fabiankaegy noted that it is worth calling out that there are still a few roles that are looking for volunteers. @priethor added: in particular, 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. Lead role is the one with the most in need of volunteers. There are a few inexperienced volunteers for the docs lead role, but it would be great if somebody with experience in the role could participate, too. Please reach out to @priethor directly if you have any questions.

A quick update about the next maintenance release, WP 6.5.3. There are currently 3 open trac tickets and 1 Gutenberg ticket left to resolve. A 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). is planned for May 2 at 17:00 UTC, with a tentative release date planned for May 7. There is more information about this release in this post, including 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. scrub schedule and how you can get involved.

A quick reminder that our next Gutenberg release (18.3) is in progress and the Release Candidate is scheduled for May 2.

Discussion

We dedicated the discussion time to revisiting the conversation that was kicked off last week during our announcements related to recent #core-editor conversations about how we can improve how contributors follow along with editor updates and improve communication within the project.

To kick things off, @joemcgill shared some suggestions that @youknowriad posted on the agenda:

I know a lot of 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. follow core updates by following the commits that happen on the #core slack channel. I believe that we should be doing the same for editor commits. These commits are already shared on slack on #core-editor-commits channel. That would be IMO a great way for core contributors to keep up with what’s happening on the editor side and potentially interact (even on merged PRs like we do for closed tickets on tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.) without waiting for the code to reach Core through backports or anything.

I think we can also consider showing these commits directly in the #core channel in Slack like we do for Core commits because in the end, these are core commits too, they just happen on another repository. Today we have between 10 and 20 commits per day, I think that’s an acceptable number that won’t “flood” the channel that much and would bring more visibility.

We discussed that we could experiment with posting commit summaries to the #core channel for a short period of time, such as a few weeks, and evaluate how it works. We also discussed that the commits from Core provide more detailed summaries compared to the commits to trunk on the Gutenberg repo, so this is a potential improvement for the Gutenberg commits. @audrasjb noted the Core handbook link for Commit message best practices.

@joemcgill said that he will follow up on moving this forward this week.

@azaozz noted:

There was another concern in that discussion: many contributors that cannot contribute very regularly are missing when development starts for (major) new features. That results in not being able to start contributing to them in time, or not providing timely feedback, ideas, being able to test different approaches, etc.
One of the ideas how to fix this was to start announcing when new major features development starts in dev. chat (and in the summaries). Seems most/nearly all contributors follow make/core and that would benefit them.

@priethor noted that Dev chat time is not very EU-friendly, asking folks to announce features here can be a big ask depending on the project.

@joemcgill summarised that there are several things to unpack here, primarily:

  1. How can we make it easier for people to contribute to new features
  2. What is the right timing and method for communicating updates at key milestones for a feature (e.g., merges, etc.)

@hellofromtonya suggested: How about a Make/Core post with links to tickets or project board and/or the key labels for tracking?

Open Floor

@afragen gave an update on the Merge Proposal: Rollback Auto-Update, and noted that we haven’t received any issues with testing so @afragen believes that it’s going well and we’re on our way to commit in a week or so. Also, there are 6000+ active users of the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.. Please read the proposal and test the feature plugin in the next week, ideally before the next dev chat.

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

Performance Chat Summary: 30 April 2024

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

Announcements

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:
    • @joemcgill For our auto-loading improvents, #42441, I owe @pbearne feedback on a draft of the dev-note (planning to do so this week). I also left some feedback on the follow-up issue (#61045) that needs to be addressed, and then I think that is ready for commit.
      • @pbearne I need feedback on this as I went through coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and set the autoload for all update_options. If i felt they were adminadmin (and super admin) only options i set them to off
      • @joemcgill I think that’s a useful idea, but we should probably handle that in a separate issue/PR
      • @pbearne in an attempt to reduce options load on the front-end
    • @spacedmonkey I want to try and get https://github.com/WordPress/wordpress-develop/pull/6393 committed in the next couple of days. Just waiting on final feedback from @peterwilsoncc
    • @spacedmonkey also working on https://github.com/WordPress/wordpress-develop/pull/6311. It needs tests.
      • The wp_prime_network_options  function is an example of where it might not have a direct benefit out of the box. It is a developer api and would enable plugins to “do the right thing” I prime multiple networknetwork (versus site, blog) options caches at once.
    • @thekt12 I have started a new PR 6463 for caching #57789 (not ready for review). I was trying to see if we could cache before 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. to avoid unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. failures but seems that doing so only give 0.01% improvement.
      • At the moment I am trying to cache inside WP_Theme_JSON_Data::__construct and WP_Theme_JSON::__construct as they are the one with major 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.

Performance Lab Plugin (and other Performance Plugins)

  • @westonruterPR is ready for review which allows performance features to have plugin dependencies. This is needed for Image Prioritizer which depends on Optimization Detective. With this PR merged, the work on Image Prioritizer can press forward full steam.
  • @mukesh27 I worked on Progress indicator is missing when activating a feature and it has been merged! Requires a follow up though from this comment
  • @joemcgill For the 3.1.0 milestone, we have one issue that needs an owner to move forward: https://github.com/WordPress/performance/issues/1032. @westonruter were you planning to pick that up from Felix, or do we need someone else to help move this forward?
  • @westonruter Both Speculative Loading (PR merged) and Optimization Detective (PR pending merge, review please) will be able to be embedded in other plugins or themes to increase adoption. This is more relevant to Optimization Detective since it is lower-level plumbing which optimization plugins can leverage, and Speculative Loading is getting popular.
    • Also for Speculative Loading, there’s a PR open to add a filter for whether speculation rules are printed and default to not printing when the user is logged-in non-admin or PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher session is active. Could use additional eyes to confirm the approach. Should there be a checkbox for whether to enable for logged-in users? Also, perhaps Speculative Loading should add a Site Health check for when PHP sessions are being used on the frontend so a user can be aware why it doesn’t seem to be doing anything?

Active Priority Projects

Improve template loading

  • @joemcgill There are really only three issues remaining in this project, #59595, #59600, and #57789 (which we already discussed and is probably the most important next step).

INP research opportunities

Improving the calculation of image size attributes

  • @joemcgill I spent some time updating the overview issue for Improving Images sizes, and began filling in some details. This project covers two main efforts to improve the way WP calculates sizes:
    • Improving the default sizes algorithm (accounting for layout)
    • Implement the auto-sizes HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. spec (already handed by the auto-sizes plugin)
  • Rather than creating a whole separate performance feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. for developing the improvements to the default sizes algorithm, I think it makes sense to combine all of this into the original auto-sizes plugin.
  • In addition, I created an issue to track the work needed to measure and track the impact of these changes, in which I link to the latest data we were able to query from HTTPArchive as a baseline.
  • @joemcgill has assigned one issue to @mukesh27

Optimized autoloaded options

  • Updates covered in WordPress 6.6 item above

Open Floor

  • @mukesh27 Is there any plan to merge https://github.com/WordPress/performance/tree/trunk/includes/site-health/audit-autoloaded-options in core?
    • @spacedmonkey The blockerblocker A bug which is so severe that it blocks a release. for the above was at the lack of action to.
    • it is all well and good highlighting that there are 20 options that are very large, but with no way to fix it, a user it out of luck. I had planned to have a way of changing options to be from being autoloaded or not. Think checkbox and rest apiREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. to update the row in the database. I haven’t had anytime to look at now I am not sponsored.

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

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

Performance Chat Agenda: 30 April 2024

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

  • Announcements
  • 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, April 24, 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 @mikachan.
🔗 Agenda post

Announcements

An update for the 6.6 release squad has been posted, please note that the release squad is looking for one or two 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. Leads to focus on triaging TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and a Documentation Lead with previous experience for the role.

Also, a reminder that the WordPress 6.5 retrospective post has been published, please fill in the survey if you would like to leave feedback or suggestions for improvements to the release process. The form and comments will be open until April 26th, 2024

There was also a recent discussion in the #core-editor channel around several topics linked to how we can improve how contributors follow along with editor updates and improve communication within the project. There were several potential actions discussed, including:

  • Create more high-level tracking issues that are not tied to a 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..
  • Create Slack channels for high-level features, such as navigation (#feature-website-navigation) and the grid 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. (#feature-grid).
  • Create teams on 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/ for high-level features to create an easy point-of-contact and discussion space for these features.

@annezazu called out that she did some recent work cleaning up the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repo, which should help with this, including getting high-level overview issues in place for all phase 3 items.

Tied to this, 6.6 is the start of having set iteration labeled issues that are targeted for the release and should make it easier to follow release-specific, in-progress work: https://github.com/WordPress/gutenberg/labels/%5BType%5D%20Iteration

@jorbin suggested a make/core post outlining more specifics about the intended process for the iteration issues, to make sure things stay up to date.

@mikachan believes that a summary post is being written to help summarize the next steps from the discussion that happened over in #core-editor.

@johnbillion and @priethor both expressed concerns about potential siloing if we experiment with adding more feature channels.

Forthcoming releases

Next major release: 6.6

We are currently in the WordPress 6.6 release cycle.

Next maintenance release: 6.5.3

There are currently 15 open tickets in the 6.5.3 release milestone. There is more information about this release in this post, including 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. scrub schedule and how you can get involved.

@jorbin gave the following update:

6.5.3 is still on target for 7 May. Scrubs have been moving things forward. There are a couple of at risk tickets so if you see something towards the bottom of https://core.trac.wordpress.org/tickets/minor/workflow, it would be good to jump in to help.

There are also a few tickets on GitHub so look towards the left there to see tickets you can help move forward https://github.com/orgs/WordPress/projects/186

Next Gutenberg release: 18.2

Gutenberg 18.2 is scheduled for April 24 and will include these issues. During the meeting, @colorful-tones asked for support with a problem encountered while publishing.

Discussion

@peterwilsoncc previously raised that we should consider syncing the editor packages earlier in the release cycle. Could this be attempted for 6.6? Slack reference.

  • This process is documented here, but @youknowriad warned that a lot of that work is also manual for the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher part and not something that doesn’t have a clear workflow.
  • @johnbillion noted a related issue, #60967, which could help with this process.
  • @joemcgill suggested that we put some focus on reducing friction of the PHP syncing during this release and will follow up with @youknowriad and tech leads @ellatrix, @vcanales, and @audrasjb about some next steps.

@afragen published the Merge Proposal for Rollback Auto-Update and asked for more testing and feedback in order to commit this early during the cycle.

Highlighted posts

The full list of posts from the last week in Core can be read on the agenda at this link.

Open floor

There was no time for the open floor section during this dev chat, but @drivingralle did mention a potential ticketticket Created for both bug reports and feature development on the bug tracker. for 6.6 on the agenda post:

Would be great if ticket #55184 could be included in 6.6.

Props to @mikachan for reviewing.

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