The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
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 ticketticketCreated 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
WordPress 6.6 Beta 2 was released on June 11. Contributors will now be focused on testing and fixing bugs discovered during betaBetaA 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.
Forthcoming releases
Next major releasemajor releaseA 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
No maintenance releases are currently being planned.
Next GutenbergGutenbergThe 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.6
Gutenberg 18.6 is scheduled for June 19 and will include these issues. This version will NOT be included in the WordPress 6.6 release.
Discussions
As we’re in the middle of the 6.6 release cycle, we’ll prioritize any items for this release. Please review the Editor Updates section of this agenda for a list of updates of several key features related to this release.
Unified publish flows: after a discussionrevisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. have been returned to a higher level of prominence in the publish flow. Thank you everyone who chimed in.
Phase 3: In line commenting: a PR continues to be worked on to bring about an initial experimental feature for in line blockBlockBlock 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. commenting. This will also be implemented as an experiment in order to get feedback.
Site Editor: a PR is underway for Feature: Set editor rendering mode by post type which would allow developers to set the default rendering mode of the block editor (show template or not). In the PR a discussion is underway about setting the template lock view as the default for pages for 6.7 and having this as a user setting in a follow up PR that users can override.
Styles: a PR is underway to add a Font size presets UI and is ready for broader testing/feedback.
Outside of the above, @annezazu has published the 6.6 source of truth early look. It’s expected things might shift during the beta period but hopefully this helps folks prepare for the release and help educate others on what’s to come.
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.
3.1.0 launched on June 6 to include new performance pluginPluginA 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 assets
Early WordPress 6.6 BetaBetaA 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 performance results [GitHub issue]
Contributor DayContributor DayContributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WordCampWordCampWordCamps 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, Turin, Italy on Thursday June 13
Priority items
WordPress performance TracTracAn 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 plugin (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
Open floor
If you have any topics you’d like to add to this agenda, please add them in the comments below.
WordPress 6.6 betaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is today
Performance lab 3.2.0 release scheduled for June 6
Priority items
WordPress performance TracTracAn 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 pluginPluginA 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
Open floor
If you have any topics you’d like to add to this agenda, please add them in the comments below.
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 ticketticketCreated 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
WordPress 6.6 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for June 4. Contributors will now be focused on testing and fixing bugs discovered during beta testing.
Forthcoming releases
Next major releasemajor releaseA 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
The release candidaterelease candidateOne 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). for 6.5.4 is now available for testing. The full release is scheduled for June 5.
Next GutenbergGutenbergThe 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.5
Gutenberg 18.5 is scheduled for June 5 and will include these issues. This is the last version of Gutenberg to be included in WordPress 6.6.
Discussions
As we’re in the middle of the 6.6 release cycle, we’ll prioritize any items for this release. Please review the Editor Updates section of this agenda for a list of updates of several key features related to this release.
Editor updates
You can keep up to date with the major Editor features that are currently in progress for 6.6 by viewing these Iteration issues.
Props to @annezazu for putting together these updates.
Synced Patterns now allow for overrides and they are connected with the BlockBlockBlock 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. Bindings APIAPIAn 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. – If you are interested on how this works @santosguillamot just published an Update for the Beta phase – with short videos and a list of how things work and what will have to wait for 6.7
Inserter: a PR landed to show all blocks when searching for blocks while a block is selected. The prior experience showed either a limited set or no blocks depending on allowed blocks.
Unified publish flows: an issue is open to consider returning revisionsRevisionsThe WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. to a higher level of prominence, another great area to share feedback and your perspective.
Outside of the above, @annezazu has published the 6.6 source of truth early look. It’s expected things might shift during the beta period but hopefully this helps folks prepare for the release and help educate others on what’s to come.
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.
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 ticketticketCreated 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 1 week from today. From this point on, core contributorsCore ContributorsCore 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. should focus on testing and fixing bugs discovered during betaBetaA 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. We should also begin publishing Dev Notesdev noteEach 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.
Forthcoming releases
Next major releasemajor releaseA 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
@jorbin has confirmed that there will be a 6.5.4 release scheduled for June 5, to accommodate #61269. An RCrelease candidateOne 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 scheduled for May 30.
Next GutenbergGutenbergThe 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.5
Gutenberg 18.5 RC is scheduled for May 31 and will include 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.
@fabiankaegy has flagged that there are a number of commits that still need to be synced from the Gutenberg repo as part of this tracking issue. He also is tracking related PRs in this table on the WP 6.6 Editor Tasks board. Support from folks to review and commit these PRs is appreciated as we approach the 6.6 beta 1 deadline.
Unify publish flows: Curious to hear from folks around a change to the Revisions panel making it behind a three dot menu (adding an extra step) rather than displaying it as a top level item in the post sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. For scheduled posts, a PR is underway to ensure the publish date control selection is shown within the modal.
BlockBlockBlock 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. shadows: Edit/create shadows in global styles landed and is in a solid spot for the release.
Block HooksHooksIn 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.: after more research and experiments, work to Add support for block name aliases for variations is being mostly pushed to 6.6 except for items from this list, which should all be significantly lower risk, and prepare the ground for the bigger changes (for are targeted for 6.7).
Inserter: a PR is underway to explore showing all blocks when searching for blocks while a block is selected. The current experience shows either a limited set or no blocks depending on allowed blocks.
Data Views: a recent PR bootstraps an APIAPIAn 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. to allow third-party developers to register and unregister post type actions. This is going to be available in the Gutenberg pluginPluginA 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 only for now and is not planned for 6.7 but relates to the overall efforts.
AccessibilityAccessibilityAccessibility (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): review and join a discussion around a recently opened issue for Consistent Sidebar DOM and Open/Closing Interactions
Opportunities to get involved and help:
Needs CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Contributor dev review: as mentioned previously a PR is underway to Add plugin template registration API so plugins can easily register templates and template parts. Please help test if you’re a plugin author who would benefit from this. It’s also ready for someone with a strong Core & PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher background to dive in to review. This is not slated for 6.6.
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.
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 ticketticketCreated 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 ContributorsCore 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 betaBetaA 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 noteEach 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 (SlackSlackSlack 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).
@ellatrixrecently announced that the last GutenbergGutenbergThe 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 candidateOne 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 releaseA 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
@jorbinrequested 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.
Data Views: Many PRs have been merged over the last week, including several bugbugA 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, a new ViewActions component, ViewTable component, ViewGrid component, and enhancements for small screens.
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.
#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 APIAPIAn 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.
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 WordCampWordCampWordCamps 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 TracTracAn 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 pluginPluginA 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 bugbugA 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.
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 ticketticketCreated 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.
Next major releasemajor releaseA 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
Next GutenbergGutenbergThe 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 blockBlockBlock 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.
CoreCoreCore 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:
Need REST APIREST APIThe 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/. review: The ability to add relative paths to theme assets has advanced, however there are implementation details for editor support that are not yet resolved. It’s a big feature and it needs to be done right so if any REST API folks can share thoughts on the proposed approach to resolve relative paths to theme assets in theme.jsonJSONJSON, 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. it would be very appreciated.
Registering templates for plugins: a new PR looks to Add plugin template registration API so plugins can easily register templates and template parts. Check it out for an early look.
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.
Performance lab 3.1.0 release scheduled for May 20
Priority items
WordPress performance TracTracAn 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 pluginPluginA 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.
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 ticketticketCreated 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.
WordPress 6.5.3 was released on Tuesday, May 7. This minor releaseMinor ReleaseA 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 bugbugA 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 CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. and 9 bug fixes for the blockBlockBlock 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.
Forthcoming releases
Next major releasemajor releaseA 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
Now that 6.5.3 is released, let’s discuss planning for the next maintenance release.
Next GutenbergGutenbergThe 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.3
Gutenberg 18.3 is scheduled for May 8 and will include these issues.
Discussions
Following up with some updates from previous week’s discussion:
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 trunktrunkA 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.branchbranchA 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.
Block bindings APIAPIAn 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.: check out the latest update of completed work and remaining blockers + decisions to make for the release. Please review and chime in! This includes efforts to improve the UI.
Expanding style variations: a recent blockerblockerA bug which is so severe that it blocks a release. has been split into its own issue Reducing specificity of default block style variation styles. Please chime in with thoughts on possible approaches.
Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.