Bug Scrub Schedule for WordPress 6.3

It’s time to schedule the 6.3 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 sessions!
These 6.3 specific ticketticket Created for both bug reports and feature development on the bug tracker. scrubs will happen each week until the final release.

Alpha Bug Scrubs

Beta Bug Scrubs
Focus: issues reported from the previous beta.

  • TBD

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). Bug Scrubs (if needed)
Focus: issues reported from the previous 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)..

  • TBD

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

For your reference, here are some of the recurring sessions:

Have a recurring component scrub or triage session?
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.” @audrasjb, @chaion07, @oglekler, or @mukesh27 on 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/. to have it added to this page.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at any time? Yes, you can!

How? Ping @audrasjb, @chaion07, @oglekler, or @mukesh27 on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 6.3-focused? Awesome! It can be added it to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 6.3 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 6.3 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Thanks to @chaion07, @oglekler, or @mukesh27 for helping to put together the agenda.

#6-3, #bug-scrub, #core

Dev Chat Summary, June 7, 2023

The WordPress Developers Chat meeting took place on June 7, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Announcements

  • WordPress 6.4 Development Cycle: The third planned 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. for 2023 is taking shape! Check out the release team and supporting cohort, the release schedule, and learn how you can get involved with 6.4.
  • Gutenberg 15.9.1 available: 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. provides two fixes: custom fonts are again visible on the editor, and social icon colors now correctly reflect changes in Global Styles. Thanks to everyone involved in this release.

Highlighted posts

Here’s an overview of updates in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between May 22 and June 5, 2023:

  • 37 commits
  • 63 contributors
  • 91 tickets created
  • 9 tickets reopened
  • 71 tickets closed
  • and 10 new contributors in this period ♥️
  • Contribute to Core at WordCamp Europe Contributor Day 2023: Are you preparing to join the WordCampWordCamp WordCamps 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 2023 CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tables on Contributor DayContributor Day Contributor 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/.? Check out this helpful post to get started, and to set up a local environment in advance of the event. Note: there are no more tickets for Contributor Day, the additional attendee tickets have now all gone.
    For those people who want to get started contributing to core, but were unable to get tickets, the links below are a good start:
  • June 2023 Developer Blog Editorial Meeting: Update from @webcommsat for the Editorial Group – If you are looking to contribute through writing blogblog (versus network, site) posts, check out the summary from this most recent Developer Blog editorial meeting for a list of articles under discussion or in need of a writer. There are editors who support the posts through the process of being published, so don’t worry if you have not contributed to the Developer Blog previously.
    • Have an idea for a post? Great! You can also suggest posts that you would like to read or contribute to the blog. Or do you just want to read excellent content geared toward WordPress developers? Got you covered there, too: check out the latest posts.
    • The Editorial Group wants is encouraging developers to come along and contribute on topics that are approved and suggest new ones, including on how to use new features in a release etc. Please do chat with people at WCEU who might be interested. There is a lot of support available.

Release updates

WordPress 6.3 will be the next major release. Stay in the 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. by checking out:

  • Roadmap to 6.3
  • WordPress 6.3 Planning Roundup
  • and following along in the #6-3-release-leads channel
  • with 6.3 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 less than 3 weeks away are there any enhancements or feature requests milestoned there that need help with patches, testing, review, or committing?

Query on Fonts-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.

  • @joemcgill raised during the performance ticketticket Created for both bug reports and feature development on the bug tracker. scrub earlier, a few contributors were wondering about the Fonts-API and whether any support was needed to test that feature since it’s being developed in 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. 
  • @hellofromtonya: Help is always appreciated! Always! There are a number of issues / enhancements being worked on that can use some testing reports and code help.
    • The Fonts API project board on GitHub.
    • The Ongoing Roadmap which has a list of “required for Core introduction” items.
    • In addition to those tickets/items, general testing to try and break it are appreciated.
    • When it’s moved out of “experimental” (note, the API is still experimental and will be until all of the required items are done and released in Gutenberg), then it’ll be a single PR to test and commit.
    • Why single PR? Because it’s been well-tested in Gutenberg over many months. Once it’s ready, it should be fully ready for Core introduction.
    • What is keeping it in “experimental”?
      The biggest reason is: the interaction between 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. and Fonts API for populating typography pickers in editors (not including the Site Editor). This issue. The scope of this will change with the introduction of the Font Library.
    • What’s the Font Library?

Tickets/ Component Maintainers help requests

To start, there were a couple of requests for help in the open floor section of the #core-editor meeting on May 31, 2023, including:

No comments were raised during the live meeting on these two areas.

Open floor

Two items:

  • WordCamp Europe attendees were encouraged to ask any questions during the meeting or in the contributor-channel/ core channel relating to Core contribution.
  • @hellofromtonya: A proposal is drafted and will be published before next week’s dev chat. The proposal is for setting criteria for removing “beta support” from each PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8+ version. It includes seeing the criteria in action for WordPress 6.3 which could possibly mean removing “beta support” label from PHP 8.0 and 8.1 – maybe.

Next Meeting

The next meeting will be on June 14, 2023 at 20:00 UTC.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel.

Props to @ironprogrammer and @webcommsat for the summary, and @hellofromtonya for peer review.

#6-3, #6-4, #dev-chat, #meeting, #summary

Two Weeks in Core – June 5, 2023

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between May 22 and June 5, 2023. Sorry for not being able to publish a post last week, this one will cover two weeks!

  • 37 commits
  • 63 contributors
  • 91 tickets created
  • 9 tickets reopened
  • 71 tickets closed

Ticketticket Created 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

Bundled Themes

  • Remove/disable obsolete IE-specific skip-link-focus-fix – #54421

Coding Standards

  • Improve formatting of some SQL queries for better readability – #58372
  • Use strict comparison in wp-admin/includes/menu.php#57839
  • Use strict comparison in wp-admin/includes/schema.php#58042, #58047, #57839
  • Use strict comparison in wp-admin/includes/update.php#57839
  • Use strict comparison in wp-admin/network/sites.php#57839
  • Use strict comparison in wp-admin/network/users.php#57839
  • Use strict comparison in wp-admin/users.php#57839
  • Use strict comparison in wp-includes/category.php#57839
  • Use strict comparison in wp-includes/class-walker-category.php#57839
  • Use strict comparison in wp-includes/theme-compat/comments.php#57839

Comments

  • Deprecate wp_queue_comments_for_comment_meta_lazyload function – #58301
  • Move wp_queue_comments_for_comment_meta_lazyload function to the correct file – #58301

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

  • Attempt to raise the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher memory limit for cron event processing – #56628

Docs

  • Add a @since tagtag A 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.) for the pre_wp_setup_nav_menu_item 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.#56577
  • Miscellaneous corrections and improvements to docblocks – #57840
  • Various docblockdocblock (phpdoc, xref, inline docs) improvements in Custom 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. Image related functions, as per docblocks standards – #57840

Editor

  • Use register_block_type_from_metadata in register_core_block_types_from_metadata – #58342

Emoji

  • Remove extraneous sprintf() from _print_emoji_detection_script()#58436, #44632

Editor

External Libraries

  • Update jQuery to version 3.7.0 – #58083

Formatting

  • Add support for schwa in remove_accents() – #57609

General

  • Improve performance of the _wp_array_get() function – #58376

Help/About

  • Remove unwanted space in a link located on about.php#58373
  • Reverse the order of conditionals for displaying the “Go to Updates” link – #57839

I18Ni18n Internationalization, 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.

  • Improve _load_textdomain_just_in_time() logic when there are no translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. files – #58321
  • Provide gettext context to disambiguate various translation strings – #58424
  • Refactor determine_locale() for performance and readability – #58317

Media

  • Conditionally skip lazy-loading on images before the 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. to improve LCP performance – #58211, #53675, #56930
  • Correct the fallback value passed to the $mimes parameter of wp_check_filetype_and_ext() from _wp_handle_upload(), and update corresponding documentation – #58349
  • Fix lazy-loading 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. by avoiding to modify content images when creating an 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.#56588
  • Prevent scaling up of images in the Image Editor – #26381

Menus

  • Add a short-circuit filter to wp_setup_nav_menu_item()#56577

Options, 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. APIs

  • Change the option can_compress_scripts to be autoloaded. – #55270

Themes

  • Use correct escaping function for aria-label in _navigation_markup()#58387

Upgrade/Install

  • Avoid an extra database query in populate_network()#58423

Users

  • Make sure bulk actions are only executed with the Apply button, not Change – #57952

Props

Thanks to the 63 people who contributed to WordPress Core on Trac last week: @sergeybiryukov (14), @mukesh27 (11), @costdev (10), @aristath (9), @afercia (9), @spacedmonkey (8), @poena (8), @flixos90 (5), @swissspidy (3), @nihar007 (2), @TobiasBg (2), @thekt12 (2), @audrasjb (2), @joedolson (2), @westonruter (2), @sabernhardt (2), @desrosj (2), @sakibmd (1), @azaozz (1), @suleymankenar (1), @przemekhernik (1), @umeshmcakadi (1), @krupalpanchal (1), @dhrumilk (1), @sh4lin (1), @peterwilsoncc (1), @RavanH (1), @ellatrix (1), @mikeschroder (1), @jrf (1), @samiamnot (1), @joemcgill (1), @salvoaranzulla (1), @gziolo (1), @sarequl (1), @NekoJonez (1), @sumitbagthariya16 (1), @ahsannayem (1), @Mista-Flo (1), @markoheijnen (1), @david.binda (1), @Cybr (1), @ironprogrammer (1), @andizer (1), @faisalahammad (1), @thakkarhardik (1), @johnbillion (1), @ocean90 (1), @haritpanchal (1), @Ankit-K-Gupta (1), @iandunn (1), @pkbhatt (1), @brookedot (1), @platonkristinin (1), @gonzomir (1), @mgol (1), @jorbin (1), @hbhalodia (1), @ankitmaru (1), @sudipatel007 (1), @naeemhaque (1), @nuhel (1), and @zunaid321 (1).

Congrats and welcome to our 10 new contributors of the week: @suleymankenar, @przemekhernik, @umeshmcakadi, @sh4lin, @sarequl, @pkbhatt, @platonkristinin, @hbhalodia, @sudipatel007, @nuhel ♥️

Core committers: @sergeybiryukov (17), @audrasjb (4), @spacedmonkey (4), @johnbillion (3), @westonruter (2), @swissspidy (2), @flixos90 (2), @azaozz (1), @antpb (1), @oandregal (1).

#6-3-2, #core, #week-in-core

Core Editor chat summary: 7th June 2023

This post summarises the weekly editor chat meeting (agenda for 7th June meeting) held on 2023-06-07 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

  • Gutenberg 15.9.1 is the latest release following on from 15.9.0.
  • The 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). wasn’t released yet.
  • Check out the Issue for backporting the PHP changes from the Plugin for the WordPress 6.3 release. Please check whether you’ve received a 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.” and if you have please take time to help get your changes ready.

Updates based on updated scope for site editing projects

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@ndiego:

  • Currently working on the release process for 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/ 16.0 RC1 and part of that is going through all of the PRs attached to the milestone to make sure each has a [Type] ... label. These are used to auto-generate the changelog.
  • Wanted to request that when folks create/review a PR, to please make sure they add a type label (i.e. [Type] Bug[Type] Enhancement etc.).
  • Focusing on the Contributor Guide sections of 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 Handbook. The goal is to get each page updated and accurate as well as adding missing info.

@get_dave:

  • I been working on several PRs relating to the work underway to refresh and improve the core LinkControl component.
  • Adding focus mode for Navigation Menus as part of work to add Navigation section to the Browse Mode sidebarSidebar A 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..

Open Floor

It was a quiet meeting due to WCEU…

New Contributor review requests

#core-editor, #core-editor-summary, #meeting, #summary

WP Feature Notifications at WordCamp Europe Contributor Day

The WP Feature Notifications project will be at WordCampWordCamp WordCamps 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 Contributor DayContributor Day Contributor 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/., led by @sephsekla. We are a small, focused team, and always on the lookout for new contributors, so we would encourage anyone to get involved!

WP Feature Notifications is a feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins., with a proposal to modernise the way in which WordPress handles emails, adminadmin (and super admin) notices and user notifications. We are working towards the 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 version of a new, centralised system, with both PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher and REST-based APIs.

Contributing

The project has something for everyone, and all new contributors are very welcome!

For developers and other more technical contributors, we have several areas to focus on:

  • In-progress PHP work for the MVP
  • JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. improvements to make better use of WordPress components
  • A provisional TypeScript rewrite of the JavaScript UIUI User interface

We also have a number of areas to cover which are less technically focused:

  • Testing and feedback on our current proof of concept (version 0.2.0)
  • Feedback and pain points on the current WordPress notices and emails
  • Discussion and ideas for future requirements

No setup ahead of the event or prior knowledge is needed to get involved, but for more technical work we would recommend bringing a laptop with Docker, npm and Composer installed.

Find out more

We look forward to seeing you at the event!

If you’re interested in the project, you can also join the #feature-notifications channel in the Making WordPress Slack or find out more about the project at  https://github.com/WordPress/wp-feature-notifications.

#contributor-day, #feature-notifications

Dev Chat agenda, June 7, 2023

Additional information is included in this agenda to assist new and potential contributors to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. preparing for WordCampWordCamp WordCamps 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’s Contributor DayContributor Day Contributor 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/. this week.

1. Welcome and housekeeping

Summary from the Dev Chat on May 31, 2023 – props to @webcommsat.

2. Announcements

WordPress 6.4 Development Cycle – posted by @cbringmann.

Gutenberg 15.9.1 available. 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. provides two fixes: custom fonts are back again visible on the editor and social icon colors now correctly reflect changes in Global Styles. Thanks to everyone involved in this release.

3. Highlighted posts

Preparing to join the WordCamp Europe 2023 core tables at Contributor Day? Information to help you get started and set up a local environment in advance.

Update on the Developer Blogblog (versus network, site) from @webcommsat: If you are looking to contribute through writing blog posts, check out the summary from the June 2023 Developer Blog editorial meeting for articles that are under discussion or in need of a writer. There are editors who support the posts through the process of being published, so don’t worry if you have not contributed to the Developer Blog previously. You can also suggest posts that you would like to read or contribute to for the Developer Blog. New posts this month are also available.

4. Tickets or Components help requests

There are a couple of requests for help in the open floor section of the core-editor meeting from May 31, 2023 including on a writing flow issue for 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) relating to switching blocks, a proposal on The registerBlockSupportAPI.

Please add any items for this part of the agenda to the comments. If you can not attend dev chat live, don’t worry, include a note and the facilitator can highlight a ticketticket Created for both bug reports and feature development on the bug tracker. if needed.

5. Open floor

To start off open discussion, we would like to welcome questions from contributors attending WCEU.

If you have any additional items to add to the agenda, please respond in the comments below to help the facilitator highlight them during the meeting.

#agenda, #dev-chat

Performance Chat Summary: 6 June 2023

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

Announcements

Priority Projects

Server Response Time

Link to roadmap projects

Contributors: @joemcgill @spacedmonkey @aristath

Database Optimization

Link to roadmap projects

Contributors: @aristath @spacedmonkey @olliejones @rjasdfiii

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. & CSSCSS Cascading Style Sheets.

Link to roadmap project

Contributors: @mukesh27 @10upsimon @adamsilverstein

  • @spacedmonkey I would love some feedback on https://core.trac.wordpress.org/ticket/56990
  • @10upsimon Enhancing The WP Scripts 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. with Loading Strategy continues to progress nicely:
    • Continued work on better handling of deferred inline scripts to be strict CSP compliant (in final stages of review)
    • Ongoing work against core PR related to script strategies and the script dependency tree
    • Re-visitation of documentation updates required following recent changes to the body of work introduced via a handful merged PR’s
  • @joemcgill Re Script Loading API: The aim of the current approach is to fully support the Script Loader API, including attached inline styles, while maintaining loading order for backward compatibility so that current blocking scripts can more easily adopt one of the more performant loading strategies. Even though the PR now meets CSP best practices, there is still disagreement about whether this should be included. @westonruter is finishing up some improvements that should finalize the “full” approach. Meanwhile, I’m prepping a path to remove delayed inline handling in order to unblock the main functionality from being committed prior to 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.
    • Latest delayed inline scripts approach is happening here
    • Issue to remove delayed inline support for a core merge (if needed) is here
    • I think the main question is whether we end up merging the full implementation or a reduced scope version while continuing to decide on the right approach for supporting inline scripts attached to async/defer scripts.

Images

Link to roadmap projects

Contributors: @flixos90 @thekt12 @adamsilverstein @joemcgill

  • @flixos90 I have been reviewing the fetchpriority support PR https://github.com/WordPress/wordpress-develop/pull/4495 that @thekt12 has been working on. It’s getting close to the finish line in terms of core implementation. Once that is sorted out, we’ll have to make sure tests pass and add test coverage for the new functions
    • So that’s not quite ready for a full review yet (mostly due to tests), but feel free to take a look at the main code already

Measurement

Link to roadmap projects

Contributors: @adamsilverstein @olliejones @joemcgill @mukesh27

  • @joemcgill No new updates on automated tests, but we’re hoping to add some documentation about how to perform measurements to the Performance Team handbook in the coming weeks (maybe even in time for contributor day at WCEU)

Ecosystem Tools

Link to roadmap projects

Contributors: @joegrainger

  • @joegrainger For the Plugin Checker, we have completed Milestone 1 and started working on the second phase. This is implementing the initial checks that will be part of the plugins first release. You can follow the progress on the GitHub repo here. Thanks!

Creating Standalone Plugins

Link to GitHub overview issue

Contributors: @flixos90 @mukesh27 @10upsimon

  • @flixos90 Still awaiting approval of the Dominant Color Images 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 the plugin repo

Open Floor

  • @spacedmonkey One thing I want to look into after WCEU, is inlining styles. WordPress has ability to inline styles since 5.8. Functionality was added in 5.8 for block styles. But there are other small styles that use this improvement.
    • If you don’t know, in-line styles means outputting css inline in a style tagtag A 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.) over a link tag with an external request. This saves a httpHTTP HTTP 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. request and faster because of none blocking requests.
    • I am going to create a ticketticket Created for both bug reports and feature development on the bug tracker. and I will share it on this channel if anyone is interested.
    • I also want to document this functionality better for plugin / theme developer are aware of it and start to use it.
    • @10upsimon Curious to hear your thoughts/opinion on potentially also supporting deferred styles @spacedmonkey I know this has come up once or twice in discussions relating to the script loading strategy work. Is this something you feel is worth exploring? Critical CSS is generally inlined, but I feel that non critical css could benefit from deferral in certain situations?
    • @spacedmonkey This is something the team at XWP was looking into a while back. There is a benefit, but you have to know what you are doing. For many plugins and themes, it hard to know when a style is needed. Adding this functionality into core makes sense to me and should works the same way as deferring scripts works.
    • @westonruter Perhaps only feasible to have an API for plugins and themes to register styles that should be delayed.
    • @spacedmonkey The developer api should be the same imo
    • @westonruter Doesn’t seem feasible to do it automatically
    • @10upsimon Certainly would have to be opt-in
    • @joemcgill Finding use cases to defer styles from core would be very helpful to justify a first-party API support
    • @spacedmonkey On a similar note, block themes have ability to load on block styles for blocks core knows are on the page. Would love somehow if that functionality came to classic themes as well. Maybe by parsing all blocks before headers are sent…
    • @westonruter Block themes could actually open up possibilities for automatic delayed styles, come to think of it. If we can determine the blocks that would be in the first viewport, then block styles identified for the page but below the first viewport could be delayed (basically ditto Jonny)
    • @spacedmonkey I haven’t pushed for defer styles as I wanted to see deferred scripts in first. Once scripts is in, we should work on style defer. Even if it is just for constancy
  • @joemcgill Want to make sure that we’re keeping an eye on the performance impact of the new Fonts API that is being worked on for 6.3 in the Gutenberg repo see: https://github.com/WordPress/gutenberg/issues/41479#issuecomment-1522427602

Our next chat will be held on Tuesday, June 13, 2023 at 15:00 UTC in the #core-performance channel in Slack.

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

Editor Chat Agenda: June 7th 2023

Facilitator and notetaker: @get_dave.

This is the agenda for the weekly editor chat scheduled for 2023-05-07 14:00 UTC.

This meeting is held in the #core-editor channel in the Making 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/..

If you cannot attend the meeting, you are encouraged to share anything relevant to 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.

#agenda, #core-editor, #core-editor-agenda, #meeting

Performance Chat Agenda: 6 June 2023

Here is the agenda for this week’s performance team meeting scheduled for June 6, 2023 at 15:00 UTC.


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

WordPress 6.4 Development Cycle

WordPress 6.4 will be the third major release of 2023. The following release team and its cohorts are contributors who answered the call for leadership volunteers and interest. This release aims to galvanize participation and shared ownership for those that identify as gender-underrepresented in the WordPress open sourceOpen Source Open 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. project. 

This post is shared earlier than in past releases to encourage new contributors to engage now and shadow the 6.3 release and consider whether you, too, would like to join the merry 6.4 cohort of contributors.

Release team

All release decisions will ultimately be this release team’s to make and communicate while gathering input from the community.

Release Cohort 

The Release Cohort are those contributors who committed to assisting the release team and supporting the goal of the gender-underrepresented lead release by spearheading efforts in their respective focuses. All contributions from all community contributors are welcome, whether you are part of a cohort or can contribute to a single PR. 

Release Schedule

April 7, 20236.4 Pre-planning post.
June 5, 2023Developer Cycle post.
July 18-25, 2023Alpha Begins, 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. is opened. 
September 26, 2023BetaBeta 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. From this point on, 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. will focus on testing and fixing bugs discovered during beta testing. Begin writing Dev Notesdev note Each 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 (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/. archive, ZIP download).
October 3, 2023Beta 2. Test the beta release, fix bugs discovered during beta testing, and continue writing Dev Notes and the About page (Slack archive, ZIP download).
October 10, 2023Beta 3. Test the beta release, fix bugs discovered during beta testing, and continue writing Dev Notes and the About page (Slack archive, ZIP download).
October 17, 2023Release 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). 1. Publish the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. with Dev Notes, commit the About page, begin drafting the release post, hard string freeze, and 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". for the release. (Slack archive, ZIP download).
October 24, 2023Release candidate 2. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
October 30, 2023Release candidate 3. Update the About page images and continue drafting the release post (Slack archive, ZIP download).
November 6, 2023Dry run for release of WordPress 6.4 and 24-hour code freeze (Slack archive).
November 7, 2023WordPress 6.4 is released (Slack archive, ZIP download)!

How to contribute

To get involved in WordPress core development, head over to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and shadow a 6.3 ticket by subscribing to and watching how contributors 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., test, comment, and commit as part of the release cycle. Need help? Check out the Core Contributor Handbook.

If you want to dive deeper into the upcoming WordPress versions, join the weekly meetings in the #core Slack channel, which occur next every Wednesday at 20:00 UTC, and the editor-focused meetings in the #core-editor Slack channel, every Wednesday at 14:00 UTC.

#6-4

Dev Chat Summary, May 31, 2023

(Update June 6, 2023 – posts on 6.4 and 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/ added to section at the end of this post.)

Notes from the weekly WordPress developers chat which took place in the core channel of Make WordPress Slack. All are welcome.

To read the meeting on 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/. itself, it starts at this link.

1.Welcome and housekeeping

Dev Chat agenda – thanks to @webcommsat for preparing.

Note: The agenda includes information links for releases and some related content to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., especially this and next week to help new contributors to core going to WordCampWordCamp WordCamps 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. To allow time for more discussions on tickets, all the links may not always be highlighted during the actual dev chat, and attendees are encouraged to check the full link list in the agenda itself.

Thanks to @ironprogrammer for facilitating the meeting.

2. WordPress Announcements 

Details on the latest Gutenberg 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 release: What’s new in Gutenberg 15.9? (31 May).

3. Highlighted posts

6.2 server performance analysis summary from the Core-Performance team.

Celebrating 20 years of WordPress – post by Josepha on May 27, 2023.

Analysis of the results of the individual learner survey from Learn.WordPress.org – posted by @webcommsat. This shares findings of the survey, and presents opportunities for cross-collaboration with Core and other Make teams.

Contributor Mentorship Programme – post by @harishanker. Share your feedback to help shape mentorship in our community, and even volunteer as a mentor!

The next phase of initiatives to promote and increase sustainability in the WordPress community and wider is the Proposal: establishment of a formal WordPress Sustainability Team. The sustainability initiative meets weekly on Fridays in the #sustainability channel on the Make WordPress Slack. All welcome to attend or view the discussions asynchronously.

4. Updates on releases

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

WordPress 6.3 will be the next major release.

Roadmap to 6.3 

WordPress 6.3 Planning Roundup

6.3 Bug Scrub schedule

#6-3-release-leads channel on Slack is a good way to keep up with what is happening with the release.

Last 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. for reference

6.2.2 Security release – this came out on May 20, 2023. It addresses 1 bug and 1 security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have.. As it is a security release, it is recommended that sites are updated immediately if you have not done so already.

Last Gutenberg release: 15.9 available to download.


4. Help requests relating to tickets or from Component Maintainers

If you have any tickets you would like to raise, you can share them in comments too. If you can not attend live, you can still add a ticketticket Created for both bug reports and feature development on the bug tracker. and your query in the comments, and the facilitator will be able to share it in the meeting.

Volunteers are also needed to help run 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. scrubs.

@oglekler requested feedback on ticket #58354 in the Help/About component.

@kebbett requested review and test the PR for ticket #57893. This ticket is in the 6.3 milestone.

@petitphp requested a second opinion on ticket #58312.

@mrinal highlighted ticket #58416.

5. Open floor

Update on core tables at WordCamp Europe – if you have an update to share, you can also add it to the comments on the agenda.
Preparing for WordCamp Europe 2023 Contributor Day.

@webcommsat shared the link to a draft post to be shared with WCEU team once published.

Post dev chat posts

Preparing to join the WordCamp Europe 2023 core tables at Contributor DayContributor Day Contributor 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/.? Information to help you get started and set up a local environment in advance.

WordPress 6.4 Development Cycle – published June 5, 2023.

Gutenberg 15.9.1 available.

Are you interested in helping draft Dev Chat summaries? Volunteer at the start of the next meeting on the #core Slack channel.

Props to @marybaum for review.

#6-3-2, #6-4-2, #contributor-day, #dev-chat, #summary, #wceu