Dan Soschin 4:50 pm on May 20, 2022
Tags: ,   

WordPress 6.0 Release Candidate 4 (RC4) Now Available for Testing

WordPress 6.0 is scheduled for release next week on May 24, 2022! This RC4 release is the last milestone for testing ahead of the official release.

You can view changes since the RC3 release via Gutenberg and Trac.

Thank you to all of the contributors who tested the 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./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). releases and provided feedback. Testing is a critical part of making each release strong and a great way to contribute to WordPress.

Installing RC4

This version of the WordPress software is under development. Please do not install, run, and test this version of WordPress on production or mission-critical websites. Instead, it is recommended that you install RC4 on a test server and site. 

You can test WordPress 6.0 RC4 in three ways:

Option 1: Install and activate the WordPress Beta Tester 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 (select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RC Only” stream).

Option 2: Direct download the release candidate version (zip).

Option 3: Run the following command to upgrade via WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/:
wp core update --version=6.0-RC4

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.0 RC4 and update the “Tested up to” version in their readme file to 6.0 this week. If you find compatibility problems, please post detailed information to the support forums, so these items can be investigated promptly.

Review the WordPress 6.0 Field Guide, for more details on this release.

You can find additional information on the entire 6.0 release cycle.

Check the Make WordPress Core blog for 6.0-related developer notes for further details on the 6.0 release.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible 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. report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.

Can you speak and write in a language other than English? Help translate WordPress into more than 100 languages!

A Haiku for RC4

R-C-4 just shipped
Are you ready for six-oh?
Help us test once more

Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat.

#6-0, #releases

annezazu 1:51 am on May 20, 2022
Tags: , ,   

Core Editor Improvement: Creating & containing containers

These “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvement 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.)) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects. 

In the last few versions of 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/ set to be included in WordPress 6.0, a collection of changes were made to simplify the discovery, use, and optionality of container blocks. When combined with the new 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. locking UIUI User interface, you can create layouts of your choosing and lock when you’re ready. 

Improved discoverability

When you select multiple blocks, the toolbar shows each variation of the Group block so you can quickly choose between the different variations while directly creating content. 

Of note, you can always ungroup blocks after you’ve done this if you’d like by using the ellipsis menu in the block toolbar and selecting Ungroup. 

More variations

Blocks are now easily grouped into either a Stack layout (vertical) or a Row layout (horizontal) with a single click. These flex-based containers allow for responsiveness at default for your content, especially when combined. From the 6.0 dev notedev 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 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. on Block markup updates for image, quote, list and group blocks:

It’s a flex container, meaning it has access to content justifications and block spacing. If combined with the Row block and its ability to optionally wrap onto new lines, it can enable basic responsive behaviors, such as two columns that stack to a single column on smaller displays.

You can switch between them in the 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. settings too after your initial selection to get a feel for what you want. The video below brings the entire experience together:

More design options

To customize things more, you can play with gap support, margin, typography options, and more. For margin and padding, thanks to Gutenberg 13.2 (not coming to 6.0), you can more readily visualize your changes too. Here’s a video from the release notes:

Lock when done 

When you have things exactly as you want them, you can lock whatever pieces you’d like of your creation to prevent removal or movement from the overall container blocks discussed above to individual blocks within. This is a great way to preserve your layout. Here’s a quick visual from a previous release post: 

If you’ve explored these new options in the release cycle for 6.0 or via the 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, feel free to share your creations below in the comments or even in the Pattern Directory. If you haven’t just yet, get excited to explore for WordPress 6.0.

#core-editor, #core-editor-improvement, #gutenberg

Héctor Prieto 8:04 pm on May 19, 2022
Tags: ,   

WordPress 6.0 Release Day Process

LAST POST UPDATE: May 20th

Preparation for WordPress 6.0 final release is underway. This post shares the release process, including the timeline and how you can help. The post will be kept up to date as the release process evolves.

Release Timeline Overview

The current plan is:

RC4 ✅

In an effort to increase the robustness and quality of the release, the release squad has agreed to launch an additional RC4 before the dry run. The WordPress 6.0 RC4 release party is scheduled on 2022-05-20 16:00 in the #core Slack channel.

Dry Run

The Dry Run is a key event to determine readiness for the final release. As noted above, the current plan is to start it on 2022-05-23 16:00. You are invited to observe and/or participate. It’ll happen in the #core Slack channel.

What happens during the dry run?

  • Review 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. reports to determine if any are critical to warrant another 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). (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).).
  • Checks and updates are done in the src/wp-admin/includes/update-core.php file.
  • Pre-release scripts are run to ensure test suites, coding standards, and checks pass.

If the results are acceptable, the release goes into a 24-hour code freeze period.

24 Hour Code Freeze

After the dry run and before the release party starts, a 24-hour code freeze goes into effect.

What does this mean? No source code for 6.0.0 (i.e., in the 6.0 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".) can be changed during these 24 hours.

What happens if a critical bug is reported during this period? The release squad will meet with committers and maintainers to determine if the issue is a blockerblocker A bug which is so severe that it blocks a release..

  • If yes, another RC release happens, and the release process restarts (meaning the dry run is repeated, and then the 24-hour code freeze clock restarts).
  • If no, then the bug is targeted for 6.0.1.

The Stable Release Party

As noted above, the release party on May 24th will start no sooner than 24h after the code freeze starts, with the exact time to be determined accordingly. You are invited to observe and/or participate. It’ll happen in the #core Slack channel.

The release party walks through the steps in the Major Version Release process for anyone who wants to follow along.

Please note releasing a major version requires more time than releasing a 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. or release candidate. There are more steps in the process. If there are any last-minute issues that need addressing, more time will be needed.

How You Can Help

A key part of the release process is checking that the ZIP packages work on all the different server configurations available. If you have some of the less commonly used servers available for testing (IIS, in particular), that would be super helpful. Servers running older versions of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher and MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. will also need testing.

You can even start this early, by running the WordPress 6.0 RC3 packages, which are built using the same method as the final packages.

During the release party, options will be provided on how to help test the release package.

Tips on What to Test

In particular, testing the following types of installs and updates would be much appreciated:

  • Does a new WordPress install work correctly? This includes running through the manual install process, as well as WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ or one-click installers.
  • Test upgrading from 4.0.35, 4.9.20, 5.8.4, 5.9.3, and 6.0 RC 3, as well as any other versions possible.
  • Remove wp-config.php file and test a fresh install.
  • Test single site and multisitemultisite Used 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/networknetwork (versus site, blog) (both subdirectory and subdomain) installations.
  • Does it upgrade correctly? Are the files listed in $_old_files removed when you upgrade?
  • Does multisite upgrade properly?

Testing the following user flows, on both desktop and mobile, would be great to validate each function as expected:

  • Publish a post, including a variety of different blocks.
  • Comment on the post.
  • Install a new 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/theme, or upgrade an existing one.
  • Change the site language.
  • If you’re a plugin developer, or if there are complex plugins you depend upon, test that they’re working correctly.

Props to @annezazu and @hellofromtonya for peer review.

#6-0, #release-process

Estela Rueda 7:42 pm on May 19, 2022
Tags: , , , ,   

Dev Chat Summary, May 18, 2022

Agenda followed for the weekly WordPress Developers Chat which included updates on the 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. 6.0. The meeting was facilitated by @marybaum and @webcommsat

Start of the meeting in #Core channel on the Make 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/..

2. Announcements

WordPress 6.0 RC3 is available for testing (released May 17, 2022). Since the RC1 release on May 3, 2022, there have been approximately 50 issues resolved in Gutenberg and Trac. Thanks to everyone involved and people who came along to test at the release party.

3. Blogblog (versus network, site) posts of note to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

A Week in Core – May 16, 2022  – thanks to @audrasjb.

What’s New in Gutenberg 13.2 (May 11, 2022.)

New free resources on Learn WordPress published in April 2022. Please help share.

4. Upcoming releases

Next major release: WordPress 6.0

Update

@annezazu : 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). 4 is planned for Friday May 20, 2022, with the Dry Run still slated for May 23, 2022 and the final release for May 24, 2022. Everything is on track, including a 6.0 video.

Update post-dev chat from the release co-ordinators:

You’re invited to the 6.0 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). 4, Dry Run, and Final Release Parties. Each party will aim to be held at 16:00 UTC in #core channel on Slack.

  • RC4 on May 20, 2022 (Friday)
  • Dry Run on May 23, 2022 (Monday)
  • Final Release on May 24, 2022 (Tuesday)

Final Release on May 24, 2022 (Tuesday) will happen 24 hours after the Dry Run completes. This is part of a true 24-hour code freeze. This means it will likely start more around 17:00 UTC assuming all goes well with the dry run. Please check #core and 6.0 release leads slack channel for any updates.

Recap of useful resources on 6.0

We share this expanding list every week in dev chat in the run up to the release, particularly to help those new to dev chat or those coming to find out about the release. If you have items for it, please  let us know on the agenda or during in the meeting.

Early bug schedule for 6.1

Release update relating to Learn WordPress and associated docs

@webcommsat: A cross-team update on where we are with training and Learn WordPress, and mapping this with end user on documentation and other opportunities for the release.

We have completed an extensive review (link to the full update in the #training channel on Slack) on where things are on the Learn WordPress side for 6.0, and will be continuing with the mapping and linking with end user documentation. There are a number of high priority items that need some further assistance for Learn WordPress.

If you are able to help with this, please add a comment in the #training Slack and with what you might be able to help with. We have put together some help for any developers / those familiar with the release who are able to help with this who are new to using the Learn WordPress side.

Thanks to Training, Documentation, Core and wider who have collaborated on this over the last weeks, and in advance as the work continues post release day too.

5. Open Floor

If you are a component maintainer or running a 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 and have any updates not already mentioned under 6.0 updates, you can raise them in this section too.

a) Component maintainers – items of note

Update from @sergeybiryukov

Build/Test Tools, Date/Time, General, 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., Permalinks:  No major news this week. 

b) 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/., June 2, 2022 – core tables.
@desrosj is bringing this together for the core tables at the event. Core will share an update on this hopefully next week. If you can volunteer to help on the day, contact @desrosj.

Props to: @estelaris for writing the summary, @webcommsat  and @marybaum for reviewing.

#6-0, #dev-chat, #summary, #week-in-core

David Smith 5:12 am on May 19, 2022
Tags: , , , ,   

Editor Chat Summary: 18th May 2022

This post summarises the weekly editor chat meeting (agenda here) held on 2022-05-18 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

Task Coordination

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

@noisysocks:

@manfcarlo (not present – shared by @paaljoachim):

  • I want to draw attention to Page Break block ( core/nextpage ) not working as expected.
  • It was patched in January but there are some problems with the 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. that will need to be re-patched.
  • Details are in the latest comment on the issue.

@mamaduka – I got sidetracked with shiny new issues, but I plan to continue working on 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. Locking feature.

@vcanales:

  • I’ve created a draft PR with a small proof of concept on creating random color palettes in the 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. Styles panel, with colors that work well together in terms of legibility.
  • It’s very early on, but I’ll be updating that PR with whatever issues I can surface. I’ll also come back every week to ask for input

@get_dave:

@tomasz:

  • I wanted to call for a review of Search Block extensibility: search query vars (now merged).
  • I would really appreciate a review of the proposed implementation as this would enable our team at Woo to provide more contributions around the Search Block if we could rely on this extensibility feature.

@zieladam:

  • I’ve been working with @gziolo on merging 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/ changes into the WordPress 6.0 release 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"..
  • The RC3 was released yesterday as @get_dave mentioned, next stop: RC4 and a stable version next week.
  • I’ve shipped [Gutenberg Data Tutorial] Part 4: Creating pages
  • I’ve proposed Typescript Entity configuration types – the last blockerblocker A bug which is so severe that it blocks a release. before shipping TypeScript types for getEntityRecord and other coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-data selectors for a great  autocompletion experience

@glendaviesnz (not present – shared by @paaljoachim):

  • There have been some requests for the addition of spacing presets in Gutenberg, similar to the font size presets that are already available, to allow theme designers to specify a select list of spacing values that can be applied to blocks.
  • It would be good to get some design feedback on this, in terms of the feasibility of adding this to the UIUI User interface, and how the UI for this might be structured.
  • I think there has been some ongoing discussion about the suitability of the current UI for selecting the font size presets, so would be good not to repeat any problems that might exist there.

Open Floor

The full Open Floor discussion is available 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/..

Right click action on List View (and in wider editor)

  • @andrewserong would like to surface this PR which explore adding right click behaviour to the List View.
  • He’d love feedback on whether overriding the native right click behaviour is something we want to do in Gutenberg.
  • @get_dave, @zieladam and @mamaduka were in favour so long as it considered a11yAccessibility 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) concerns.
  • @paaljoachim had reservations around discoverability.
  • It was noted that @alexstine had already provided a11y feedback and an opt out via editor settings has been added to the PR.
  • @hypest also noted that it should consider mobile interactions as well.
  • Agreed to leave further feedback on the Issue/PR itself.

Request for feedback: enabling styling of interaction states in editor

  • @get_dave wanted to surface these design explorations on enabling styling of interaction states (:hover, :focus .etc) within the editor.
  • Now is a good time to provide feedback and raise concerns in order that the first iteration of the interface can be as good as it can be.
  • Folks were broadly in favour of this functionality being added.
  • @fabiankaegy was concerned about adding a lot of additional clicks to every interaction – felt this would be better served with a persistent setting instead of a local state in every component.
  • @get_dave requested input from folks experienced with Global Styles and 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. to discuss the potential data structure for such a feature.
  • @tomasz noted it would be nice to have a full overview of the state ie. color + typography etc. rather than split between different panels. A summary would avoid having to keep a mental map in your head of all interactions.
  • Please continue to discuss on the Issue.

Breaking change: promoting experimentalFetchLinkSuggestions to stable 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.

  • @get_dave would like to flag a PR which renames a long-standing experimental API to stable.
  • There’s been lots of discussion around experimental APIs and the deprecation strategy recently, so I wanted to flag this one final time before it gets merged.
  • Hopefully the impact is minor but it’s worth being aware of as it’s been around as __experimental for quite some time.
  • Noted that outreach has been done to community Plugins making use of the API.
  • Will merge this week unless there are any blockers raised.

Thanks to everyone who attended the meeting.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

webcommsat AbhaNonStopNewsUK 12:26 am on May 18, 2022
Tags: , , ,   

Dev Chat Agenda, May 18, 2022

This weekly WordPress Developers Chat takes place in the #Core channel of the Make 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/. on Wednesday May 18, 2022 at 20:00 UTC. All welcome.

1. Welcome

Dev Chat summary from the meeting on May 11, 2022 – thanks to @webcommsat. Could you write a dev chat summary in the future?

2. Announcements

WordPress 6.0 Release Candidate 3 (released May 17, 2022)

3. Blogblog (versus network, site) posts of note

A Week in Core (May 18, 2022)

What’s New in Gutenberg 13.2 (May 11, 2022)

4. Upcoming releases

Next major: WordPress 6.0

Updates from Release Co-ordinators and members of the squad.

Useful resources

5. Open floor

If you have any items for Open Floor, please add them in the comments below.

If you are a component maintainer and wish to raise a ticketticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.

Thanks to @marybaum and @webcommsat for working on the agenda and meeting planning.

Could you help with the summary from this week’s meeting? Comment below or message CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team reps @marybaum and @audrasjb in the Core Slack channel.

#6-0, #agenda, #dev-chat

Bethany Chobanian Lang 4:10 pm on May 17, 2022
Tags: , , hosting-community, , , ,   

Performance team meeting summary 17 May 2022

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

Announcements

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Site Health

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or 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.” in 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/.
  • @furi3r: Add Site Health test for full page caching (advanced cache) #220 was moved to 1.2.0 is just about ready and waiting for testing

Feedback requested

Measurement

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
  • No updates

Feedback requested

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

@aristath @sergiomdgomes

GitHub project

  • No updates

Feedback requested

Infrastructure

@flixos90

GitHub project

  • @shetheliving: Review the module proposal workflow and leave any feedback on the PR
    • @flixos90: We’ve been working on this to have a long-term plan for each module; want to avoid a module going into the plugin and growing stale without any iterations or next steps
    • @jeffpaul: I’ll review with an eye from the core perspective
    • @flixos90: Another benefit of this documentation is that it includes a high-level overview of how to propose a feature project for core, which isn’t really documented right now; this could be a good starting point for the future
  • @olliejones: Might be cool to have a stub performance-lab module for modification by would-be contributors
    • @flixos90: That’s a great idea, though there would be little to start with since a module can be pretty much anything. The best place to start right now is with the writing a module doc, though that’s more about the technical starting point and the new proposal doc is more about overall workflow.
  • @flixos90: Released v1.1.0 yesterday. Next release will be 1.2.0 on Monday, June 20, so we should target merge for anything for that release by about June 15.

Feedback requested

Open floor

  • @olliejones: Following up on the large site/many users work: https://core.trac.wordpress.org/ticket/55749
    • Have a new plugin to address the issues outlined there
    • Might be a candidate for a Performance Lab module
    • These issues are mostly fixable with filters and actions, but not completely
    • @adamsilverstein: Looks like a core side issue; the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. describes hte issue better. Is the issue specific to the REST endpoint or more generally about how the user query is constructed?
    • @olliejones: It’s actually central to WP_User_Query and WP_Meta_Query, but at the same time the REST endpoint’s set of parameters doesn’t allow for avoiding the query-pagination overhead

Help wanted

#core-js, #core-media, #performance, #performance-chat, #summary

Jb Audras 9:48 pm on May 16, 2022
Tags: , ,   

A Week in Core – May 16, 2022

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 9 and May 16, 2022.

  • 20 commits
  • 36 contributors
  • 45 tickets created
  • 12 tickets reopened
  • 45 tickets closed

The Core team is currently working on the 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., WP 6.0, and released 6.0 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). 2 🛠

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

Administration

  • Update design of the Dashboard welcome panel – #55532

Build/Tests Tools

  • Expand the test for conditional tags returning early if $wp_query is not set – #55104
  • Use a data provider in the test for conditional tags returning early if $wp_query is not set – #55104

Bundled Themes

  • Twenty Twenty-One: Add a missing HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. comment to indicate the end of .post-thumbnail section – #55724
  • Twenty Twenty-One: 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. fix for privacy policy section title – #55709

Coding Standards

  • Fix params indentation in pre_get_network_by_path hook docblockdocblock (phpdoc, xref, inline docs) – #55647
  • Restore the $pieces variable for SQL clauses in query classes – #55699
  • Restore the $pieces variable in WP_Query::get_posts() – #55699

Database

  • Use generic references to a database server in ms_not_installed() – #55701

Docs

  • Replace Codex URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org with a corresponding HelpHub article in the Additional CSSCSS Cascading Style Sheets. section in CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. – #55710, #48987
  • Docs: Use third-person singular verbs for function descriptions in the WP_Network class – #55646

Editor

  • Update WordPress packages for 6.0 RC 2 (part 2) – #55567
  • Update WordPress packages for 6.0 RC 2 – #55567
  • Use stricter assertions in comment template tests – #55708

Help/About

  • Update the About section for 6.0 – #55434

Media

  • Remove error suppression in wp_filesize() – #55678, #49412

Menus

  • Replace “drop down” (noun) with “dropdown” in a few strings – #55661

Query

  • Check if $wp_query is set in is_main_query() – #55104

TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.

  • Set use_desc_for_title to false by default in wp_list_categories() – #55530, #24766

Users

Props

Thanks to the 36 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (5), @peterwilsoncc (4), @audrasjb (3), @zieladam (2), @fcoveram (2), @johnbillion (2), @costdev (2), @mukesh27 (2), @hellofromtonya (2), @bernhard-reiter (1), @critterverse (1), @joedolson (1), @ndiego (1), @kebbet (1), @Cybr (1), @spacedmonkey (1), @antpb (1), @azouamauriac (1), @ironprogrammer (1), @nlpro (1), @sabernhardt (1), @NekoJonez (1), @haritpanchal (1), @andrija (1), @joyously (1), @just0nequestion (1), @stevenlinx (1), @tobifjellner (1), @hansjovisyoast (1), @tj692 (1), @timkersten655 (1), @teunvgisteren (1), @thijsoo (1), @nhadsall (1), @vdankbaar (1), and @dlh (1).

Congrats and welcome to our 9 new contributors of the week: @haritpanchal, @andrija, @just0nequestion, @tj692, @timkersten655, @teunvgisteren, @thijsoo, @nhadsall, @vdankbaar ♥️

Core committers: @sergeybiryukov (8), @audrasjb (5), @ryelle (2), @gziolo (2), @peterwilsoncc (2), and @hellofromtonya (1).

#6-0, #core, #week-in-core

Bethany Chobanian Lang 12:22 pm on May 16, 2022
Tags: , , ,   

Performance Chat Agenda: 17 May 2022

Here is the agenda for this week’s performance team meeting scheduled for May 17, 2022, at 15:00 UTC.

This meeting happens in the #performance channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

David Smith 11:04 am on May 16, 2022
Tags: , , ,   

Editor chat agenda: 18th May 2022

Facilitator and notetaker: @get_dave.

This is the agenda for the weekly editor chat scheduled for 2022-05-18 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 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.

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