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