This post summarizes the weekly editor chat meeting (agenda for 12th of July meeting) held on Wednesday, July 12 2023, 03:00 PM GMT+1. in Slack. Moderated by @paaljoachim.
Help test WordPress 6.3 Beta 4.
What’s new in Gutenberg 16.1? (June 29)
Gutenberg 16.2 RC3 is available for testing.
Final version of Gutenberg 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/ 16.2 will be released Wednesday.
Key project updates:
No updates of Key Projects during the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor meeting.
I’m going through the bug 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. reports from WP 6.3 board, checking what we can fix.
This work is very low level. The new Font Face will not impact the UI User interface directly. Indirectly, its impact is on printing the font-face CSS Cascading Style Sheets. so that fonts visually look correctly, ie use their font files to render properly. That CSS generator and printer role though has not changed from the Fonts API. What has changed? Where plugins introduce their fonts for user consideration and selection. That role moves to the Font Library.
FYI: Fonts API will not get replaced until the Font Library is introduced. And this work is not being introduced into WP 6.3, as it’s still experimental.
WP 6.3 is dropping PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 5.6 support, raising the minimum supported version to 7.0.
Gutenberg though needs to run on the last 2 WP major releases, meaning it can’t yet drop PHP 5.6 support.
The 2 PHP 5.6 PHPUnit CI jobs running on WordPress trunk have been removed from Gutenberg. Why? They were failing because Core no longer runs on PHP 5.6.
- Update your PRs if they are failing for PHP 5.6 CI jobs.
- When to drop PHP 5.6 support.
Discussion is here: Increase the PHP minimum supported version to 7.0
As I low-level contributor and triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. member, there were some suggestions within the past couple months ( i think here or in make.wordpress.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/ comments), that a release be devoted primarily to bug cleanup.
I’d just like to suggest that again… as a triager, I’m aware that some block 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 issues in github 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/ can be closed when new features are introduced but there are nearly 1,000 PRs (yes, some of them are drafts and probably be disregarded) but I imagine fellow contributors recognize the frustration of keeping up with PRs and searching through issues when they’ve already been reported.
A suggested label to go through. Open Gutenberg PR’s with no one to review these.
Maybe we can keep track some of those PRs in separate board. Bug fixes are usually easier to review, unless they rewrite the whole editor
Read complete transcript