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 our bug tracker.
Mini 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 of performance issues for 6.1.1
https://core.trac.wordpress.org/ticket/56923 – PR committed; should become available when @mamaduka syncs 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/ to coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. on Thursday
https://core.trac.wordpress.org/ticket/56815 – assigned to @flixos90 for review
https://core.trac.wordpress.org/ticket/56900 – assigned to @peterwilsoncc for commit
https://core.trac.wordpress.org/ticket/56945 – @flixos90 has PR in progress at https://github.com/WordPress/wordpress-develop/pull/3536 that needs review and feedback, especially from Gutenberg team. @annezazu working to loopLoopThe 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. someone in there.
https://core.trac.wordpress.org/ticket/56948 – ready for commit, just needs a final review; assigned to @peterwilsoncc
https://core.trac.wordpress.org/ticket/56952 – @adamsilverstein to look into
https://core.trac.wordpress.org/ticket/56974 – @flixos90 took a first look at the PR last week and will give it a comprehensive review today
https://core.trac.wordpress.org/ticket/56990 – @adamsilverstein‘s changes need review/testing
https://core.trac.wordpress.org/ticket/56991 – @spacedmonkey‘s fix at https://github.com/WordPress/wordpress-develop/pull/3575 needs review
https://core.trac.wordpress.org/ticket/57012 – ready for commit by @peterwilsoncc
@adamsilverstein: Discovered a library, jSquash, that brings image format encoding/decoding to the web. Tested a bit and oping to use it to enhance the core image 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. with modern image capabilities. If successful, would let us introduce AVIF support without depending on server-side support.
@tillkruess: Chatted with @johnjamesjacoby about adding a health check for the new wp_cache_supports() function to show which object caching features are supported/not supported but recommended. See https://github.com/WordPress/wordpress-develop/pull/3347. For example, get_multiple() is quite important. Any feedback on adding as a health check?
@spacedmonkey: Now have wp_cache_supports in core that we could use and wp_cache_supports( 'get_multiple') in all options. Instead of loading all options in one cache key, load each in their own cache key and all in single call.
JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. & CSSCSSCascading Style Sheets.
@flixos90: Plugin codebase is now updated to reflect our recent modifications to the focus areas per https://github.com/WordPress/performance/pull/566, thanks to @mukesh27
Welcome back to a new issue of Week in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between October 31 and November 7, 2022.
TicketticketCreated for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.
Code changes
Administration
Remove role="img" from decorative SVG images – #56824
Move update_blog_status() tests to their own file – #56793
Remove a custom callback for checking action call count in multisitemultisiteUsed to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site tests – #56793
Restore blogblog(versus network, site) switching in update_posts_count() test – #57023
Bundled Themes
Twenty Twenty-One: Properly bump to version 1.7 – #56450
Add brackets to a function name in get_page_template() description – #56792
Correct DocBlockdocblock(phpdoc, xref, inline docs) formatting for wp_sitemaps_enabledfilterFilterFilters 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. – #56792
Document the usage of globals in upgrade_550() and upgrade_560() – #56983
Fix typo in a comment in wp_prepare_revisions_for_js() – #56981
Replace HTTPHTTPHTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. links with HTTPSHTTPSHTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in class-json.php docblocks – #57017, #56792
Typo correction in wp_dropdown_users() docblock – #56792
Update comments in wp_nav_menu() tests per the documentation standards – #56792
CategoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. specific templates always appear as not found – #56902
General
Use HTTPS for the b2/cafélog link in readme.html – #57018
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/ 14.5 RC1 is ready to test and Gutenberg 14.5 imminent.
Should we rethink how CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Chat works (again))?
The attendance and purpose of the chat seem to be both withering for the past six months or more. Let’s spend some time to figure out what happens and what could we change to make use of our time and participation in a relevant and impactful manner.
If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:
If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.
The weekly WordPress developers meeting takes place in the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make WordPress SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. on Wednesdays at 20:00 UTC.
Dev Chat, October 27, 2022 meeting summary – thanks @webcommsat. Can you volunteer to help draft future dev chat summaries? Speak to @marybaum or @webcommsat if you can volunteer next week. There is help available.
2. Announcements!
WordPress 6.1 has landed!
@bph shared 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/ 14.5 RC1 has also landed! The pull request (PR), pending a release post.
@ndiego is the release leadRelease LeadThe community member ultimately responsible for the Release. for Gutenberg 14.5.
Performance chat summary, November 1, 2022 – has some ticketticketCreated for both bug reports and feature development on the bug tracker. updates including WebP, AVIF images, Object Cache. Also some calls for reviews.
@jeffpaul said he was most interested in what people are seeing in the forums, TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., GitHubGitHubGitHub 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/, etc. on concerns in 6.1 that might be earmarked for a 6.1.1 release.
@audrasjb: Aside from the WPML issue, I think it’s pretty quiet for a 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..
@jeffpaul asked what people were hearing or seeing in relation to 6.1.
Jeff highlighted that @annezazu has posted a couple items in #6-1-release-leads: Slack message: 1 & 2. – @annezazu: wanted to bring in feedback from what I’m hearing on WordPress.comWordPress.comAn online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ and VIP — There are some fatal errors related to WPML and some infinite loops reported in Trac Ticket #56926. Initially she proposed to flag this in the #hosting-community channel.
– @annezazu (post in the 6.1-release-leads on November 1): On a UXUXUser experience related note — seeing these main issues in GitHub:
@audrasjb raised that there seems to be an issue with ManageWP backups on 6.1. He did not feel it needed to be addressed on the WordPress core side, and would be a fix to be done by the service owner, as with the WPML issue.
@clorith raised Gutenberg issue #44166, reported pre-release. Highlighted that although it not break usability, it does change visuals of sites in unexpected and some times not-so-nice-looking ways. 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. inserter missing is a big one though.
@jeffpaul said there were items that got set aside in the run-up to the 6.1 launch that hopefully were documented and added to the 6.1.1 milestone in Trac as well.
@clorith: The “+” button missing on some scenarios item Anne listed.
Under Open Floor in the agenda, @NekoJonez advised there are reports of MailPoet crashing on 6.1, but had not recreated it on two websites using it. It is raised on the master post on the forums.
@jeffpaul suggested a scrub to identify what realistically could be targeted in 6.1.1. He recommended that anything that contributors would like to be included is set as a 6.1.1 milestone in Trac or labelled accordingly in GitHub. This way the tickets can be considered in a 6.1.1 scrub.
In discussion with @desrosj, 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. could be in the week of November 14, 2022. This date they believe would be most ideal to get things done before the US Thanksgiving holidays and before some contributors might less available with the holidays and end of year vacation schedules. He highlighted that there were definitely some items that we would want to try and get into this sort of a “fast-follow release” and would be best not to delay until January. [A post dev chat update is at the end of this section in the notes]
@marybaum asked about putting a release squad together.
@jeffpaul: “I think we might be able to find a way on the who but part of that will be determining what we’re trying to get into 6.1.1 so we know what’s needed for help. Thus getting things identified and into Trac/GitHub appropriately will help.
@jeffpaul said he could probably lead a scrub on Friday, but would ideally need more contributors involved in the review. But before then, he called for everyone’s help to “share what you’re hearing and ensuring things are in Trac/GitHub so the scrub has a chance to collect what’s ideal in 6.1.1 so we can continue to push quickly if we’re going to realistically get something out the week of the 14th (which that timeline is a bit dependent on what it is we’re targeting in 6.1.1).”
@desrosj: due to the quick turnaround, he felt it probably makes the most sense to use 6.1 squad members with appropriate skill sets and backgrounds based on what needs to be included. He said there was just not enough time to onboard a new squad for this one.
5. Component Maintainers and Tickets updates/ requests for help
a) Components
@sergeybiryukov: Build/Test Tools, Date/Time, General, I18Ni18nInternationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks: No major news this week.
@marybaum: Help/About and Quick/Bulk Edit: also no major news
@audrasjb: nothing new on Menus, Widgets, Upgrades.
No other updates from maintainers.
b) Tickets
None were raised.
6. Open Floor
@pbiron: raised the issue highlighted during Open Floor last week (thanks @webcommsat for including it in the summary last week). Read the discussion in full in the Make WordPress Slack. The discussion focused on changes to the 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 that are not released into the wild in the form of a Gutenberg release for any testing/confirmation before being ported over for inclusion in Core (especially for a major release during 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).).
@jeffpaul replied that it was something at the top of his mind coming out of 6.1 and that he would like to to have a collaborative conversation with the 6.1 RCs, editor leads, and core leads to talk through the various pain points for core and Gutenberg processes, and how we might find ways to make that ‘work better’ for whoever steps in to help lead 6.2. Given that this group is likely focusing on 6.1.1 in the near term and that people will want some time off after that, it might be for January, unless someone from that group wants to try and schedule time before 2023?
@davidbaumwald: asked if this could be automated? Like PR commit exists in a release/tagtagA directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)? He highlighted that it is “a bit tricky” as there some changes that happen when porting GB code to core(namespacing functions, file paths, etc.)
@pbiron highlighted discussion in the threads of the original message on Slack about the mechanics. He raised that what is concerning to some is that things from Gutenberg were merged into core for 6.1 before they were even merged into the Gutenberg 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., let alone a Gutenberg release.
@hellofromtonya: BackportbackportA 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. merge expectations / criteria: likely needs consensus on what can and cannot be backported to Core, such as first must be formally released in Gutenberg.
@davidb: as there’s so much to watch over, suggested core could have some sort of bot that checks a pull request (PR) to ensure it was in a previous Gutenberg release/tag.
@jeffpaul recognized that there are likely things that core needs to consider adjusting/changing to better accommodate Gutenberg. He described it as a two-way relationship. He said he did not not want to try and introduce something that impairs the Gutenberg team’s ability to continue their always-impressive velocity and release cadence.
@pbiron called for an early “real” discussion to take place.
@marybaum suggested a post on the Core blog to start the discussion.
@jeffpaul: said he would like to co-ordinate async conversation with key people from 6.1 to try and collaborate on a make/core post with thoughts that can evolve into more legitimate proposals/tweaks leading into 6.2.
@pbiron: post-major-release ‘recap/lessons learned’ make/core posts have been fairly standard recently, and recommended that this discussion should certainly be part of putting that together for 6.1.
@jeffpaul agreed and added that he would like a bit more interactivity to that than a form or comment sprawl on a post to collect input that’s summarized in a make/core post. “We need to impact change here as it was not a smooth process and if not for some experienced contributors / committers / code owners we may have been much worse off in 6.1 (so again, thanks to everyone who did contribute and try to help along the way!)”
@marybaum suggested a special extra Dev Chat Session to discuss this. @clorith agreed as it is about core processes. Discussion about setting up an special channel for the discussion, and some felt there were already too many channels.
@davidbaumwald suggested starting with asynchronous feedback and logistics handling first. Then move to some sort of sync meetings, if necessary. He thought the retro is probably the first piece to the puzzle.
@hellofromtonya reminded for this discussion to be fruitful, contributors from #core-editor need to actively participate too.
@marybaum suggested a long post akin to the way @desrosj to introduce the problem.
@hellofromtonya: in relation to @jeffpaul‘s suggestion, Tonya felt starting with the 6.1 release squad’s Core and Editor leads is a good starting place to get the ball rolling,
Tonya added: “One more thought: participation in release retrospective forms is / has been low. Active multi-channel discussions could help. ‘Channel’ does not mean slack channels.
“The goal is continuous improvement. These retrospectives after a release need more participation to collect more feedback to help make things better. Leveraging the power of open sourceOpen SourceOpen Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL..”
@davidbaumwald: Yeah, or questions/feedback offered with no response.
@marybaum highlighted that if contributors who send feedback, get no response, they may be loathed to offer more feedback in the future.
Update 7 NOV 2022: Added @mamaduka as the Release Editor Tech Lead.
Coming after the WordPress 6.1 release earlier this week, both @desrosj and I are planning to lead a 6.1.1 release for some fast-follow items that came up near the end of the 6.1 release cycle and have bubbled up post-release such that we would like to try and ship before the end-of-year holidays start to pull folks away from contributing. If there is a critical bugfix that has a patchpatchA 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./PR ready, then please look to add those to the 6.1.1 milestone in Trac or the WordPress 6.1.1 Editor Tasks project board in GitHub.
Schedule
The following schedule is what’s currently planned for the release, any additional 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. scrubs, release candidates, or other items will be added here as they get scheduled.
Bug Scrub focused on finalizing items for 6.1.1 in TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress./GitHubGitHubGitHub 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/
6.1.1 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).
Given the short timeline planned for this release, we are leveraging folks from the 6.1 release squad to help get 6.1.1 released in an expeditious manner. All others are welcome to help during bug scrubs, working on patches/PRs, testing patches/PRs, and participating in any release parties.
ReleaseCoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead:@desrosj
Release Editor Tech Lead:@mamadukaTBD (if you’re interested and available, please reach out to @jeffpaul or @desrosj or comment on this post, thanks!)
Release Coordination
The #6-1-release-leads channel will continue to be used for all coordination and conversation related to the 6.1.x releases. This matches the pattern of communication that worked well for previous 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. cycles!
Additional 6.1.x Releases
The 6.1.1 release is the final release planned for 2022, a 6.1.2 seems feasible around the end of January but the Core team will want to look to confirm formal 6.1.x Minor Release Leads by then who can help shepherd future minor releases on the 6.1 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". (cc: @audrasjb@marybaum).
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/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
@get_dave – I’ve been mainly focused on the Nav 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.:
Iterating on a new approach to referencing Navigation Menus by slug from the Nav block. I had to pivot in response to (valid) objections from the 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/. team who didn’t want us to modify the REST to accept slugs.
Also fixed a bug in Page List which made it unselectable within the Nav block…which wasn’t helpful. Unfortunately this wasn’t allowed into 6.1 but apparently it might be in the next patchpatchA 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. release.
Editor 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. scrubs
@mamaduka – I wanted to mention that @ndiego and I are hosting a weekly Editor bug scrub every Tuesday at 14:00 UTC. Everybody is welcome to join.
Phase 2 & WordPress 6.2
@get_dave – I was curious to hear more based on this question by @fabiankaegy to @priethor: “How does the Phase 2 roadmap relate to the priorities for WP 6.2?”.
@priethor – The complete WP 6.2 roadmap is not available yet, and there is no release date for 6.2 (we closed the 6.1 release around 12 hours ago), so it’s hard to dive specifics other than we should all push forward to finish the main Phase 2 priorities and be able to say FSE is “ready, out of 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.” in 6.2.
The meetings take place on Wednesdays at 20:00 UTC in the #core channel on Slack, and usually last an hour. All are welcome to attend or catch up via the summary.
The publication of the Dev Chat agenda was held for the release party of WordPress 6.1to include the updates related to it.
1. Welcome
Introduction from coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.team repTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.@marybaum
WordPress 6.1 “Misha” was released, November 1, 2022 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/ 14.5 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). expected November 2, 2022
Performance chat summary, November 1, 2022 – has some ticketticketCreated for both bug reports and feature development on the bug tracker. updates including WebP, AVIF images, Object Cache. Also some calls for reviews.
Updates from the relevant teams relating to releases.
a) Latest 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.1
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. for 6.1 find them at the dev-notes-6-1tagtagA directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). The Field Guide for 6.1.
b) Next 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.: 6.1.1
the Core Editor meeting highlighted the priorities list for the Navigation Block in WordPress 6.2. Contributors have posted some revised designs for new editing experiences which are being proposed as a focus for the next release(s).
Is there an update on the discussion on earlies?
If you have an update from release leads or any teams collaborating on related items, please add a comment.
5. Component maintainers updates / tickets / requests for help
Please add your request for tickets you would like to raise as a comment.
US changes next week (w/c 6 November) – meeting will shift ahead by one hour to stay at our regular time, so Nov 8 meeting will be at Tuesday, November 8, 2022 at 10:00 AM EST
@adamsilverstein: On the AVIF front, it looks like Apple is building support right into WebKit, which means AVIFs will work on older iOSiOSThe operating system used on iPhones and iPads./MacOS as long as users upgrade Safari (currently support depends on the underlying OS). See https://github.com/WebKit/WebKit/pull/5669. The coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker. is https://core.trac.wordpress.org/ticket/51228; the only outlier for AVIF support is now Microsoft Edge. In addition to 50%+ improvement over JPEG compression, AVIF images add support for HDR on the web; a contributor linked some sample images from the TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticket that are quite impressive.
@adamsilverstein: When working on the PR for setting fetchpriority=high on the non-lazy-loaded LCP image, noticed the first image on 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. themes isn’t having the lazy-loading attribute omitted as expected. Opened #56930 and PR #3538 to resolve; reviews appreciated. Also related: #56927, #55996.
@spacedmonkey: Also flagging https://github.com/WordPress/gutenberg/issues/45224 as related; @adamsilverstein will add link to the Trac ticket
@mehulkaklotar: Working on some improvements to Performance Lab:
Issue #560 – PR #565 – WebP upload configuration checkbox not showing in Settings > Media for multisitemultisiteUsed to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site -> Merged
@adamsilverstein: There has been some communication with Matt, repeating what he said on his post about concerns about WebP not being ready to be default mostly because it is hard to use outside of the web context. Hopefully in the future we’ll be able to get this kind of feedback earlier in a feature’s lifecycle. To move WebP further, we would need to address the underlying issue, either by improving ecosystem compatibility (which is happening naturally over time) or by improving browser capabilities (e.g. save as JPEG).
@spacedmonkey: In multisite, we used to proxy all attachments through PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher. Could we do that here? Proxy to see if there is WebP support, and if not, return JPEG. Has its downsides but thinking out loud.
@adamsilverstein: Didn’t know about that; could potentially only handle “missing” images that way using htaccess
@spacedmonkey: It’s still part of core: https://github.com/WordPress/wordpress-develop/blob/trunk/src/wp-includes/ms-files.php
@masteradhoc: Could we open a ticket in the Chromium GH for save as JPEG to see if they could add? Would help the biggest part of the web.
@adamsilverstein: Yes, think it’s worth asking them to consider.
@flixos90: We can’t really solve the problem in a clean way in WP though, since the right-click Save As behavior can’t be modified via PHP or JSJSJavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors.. Wish browsers supported some way of achieving a JPEG download of a WebP image on the web, e.g. if you use a <picture> element it could be default download as JPEG even when WebP is served in the browser. Or there could be some kind of download-src attribute.
@rmccue: Have run into this while serving images dynamically, no great way to handle
@flixos90: Looking to see if there’s anyone we can work with on this internally at Google
@spacedmonkey: Reviewed performance in 6.1-RC3 and updated results here; looking good. FSE themes are still slower than classic themes. Created some tickets related to issues found; have been working on https://github.com/WordPress/wordpress-develop/pull/3540.
@flixos90: Also did an analysis on RC3 last week; major improvement over RC1 and RC2. Still a few areas that were slightly worse than 6.0, but some of that is due to added functionality. Still a few quirks where regressionregressionA 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. is noticeably worse, namely in the wp_head action. Have tracked down the particular change that makes wp_head slower even in classic themes; PR with a potential fix here: https://github.com/WordPress/wordpress-develop/pull/3536.
@spacedmonkey: Biggest issue is that class is static methods and variables, which makes it hard to review and test.
@adamsilverstein: Digging back into the testing environment work that started awhile ago to see what we can pick up and use and what an MVPMinimum Viable Product"A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia could look like. Still researching/documenting, but more to come.
@mxbclang: @aristath is continuing to work on the SQLite integration module in https://github.com/WordPress/performance/pull/547; feedback welcome
@spacedmonkey: Thoughts on running core unit tests against SQLite, similar to how tests are run against memcache? Could allow the tests to fail for now, but would highlight where we need to fix issues.
@spacedmonkey: Is this Trac or MetaMetaMeta 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.?
@flixos90: Planning to review https://github.com/WordPress/performance/pull/566 today, which brings the focus areas up-to-date.
@mehulkaklotar: I have worked on issue #561 – PR #570 – Investigate unexpected input Warning message during release build process -> Needs review and testing both
WordPress 6.1 “Misha” was released 1st of November. 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/ 14.5 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). should be released 2nd of November.