Jeffrey Paul 12:11 am on November 4, 2022
Tags: 6.1, 6.1.1 ( 7 ), minor releases ( 29 )

WordPress 6.1.1 Planning

Update 7 NOV 2022: Added @mamaduka as the Release Editor Tech Lead.

Update 9 NOV 2022: Added Bug Scrub for Thurs, Nov 10th.

Coming after the WordPress 6.1 release earlier this week, both @desrosj and I are planning to lead a 6.1.1 release for some fast-follow items that came up near the end of the 6.1 release cycle and have bubbled up post-release such that we would like to try and ship before the end-of-year holidays start to pull folks away from contributing. If there is a critical bugfix that has a 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./PR ready, then please look to add those to the 6.1.1 milestone in Trac or the WordPress 6.1.1 Editor Tasks project board in GitHub.

Schedule

The following schedule is what’s currently planned for the release, any additional 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, release candidates, or other items will be added here as they get scheduled.

Friday, November 4th, 2022 at 13:00 UTC	Bug Scrub focused on finalizing items for 6.1.1 in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress./GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ (Slack archive)
Thursday, November 10th, 2022 at 17:30 UTC	Bug Scrub ahead of 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). (Slack archive)
Friday, November 11th, 2022 at 16:00 UTC	6.1.1 Release Candidate (Slack archive, ZIP download)
Tuesday, November 15th, 2022 at 17:00 UTC	6.1.1 Release Party

Team

Given the short timeline planned for this release, we are leveraging folks from the 6.1 release squad to help get 6.1.1 released in an expeditious manner. All others are welcome to help during bug scrubs, working on patches/PRs, testing patches/PRs, and participating in any release parties.

Release Coordinator: @jeffpaul

Release CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Lead: @desrosj

Release Editor Tech Lead: @mamaduka TBD (if you’re interested and available, please reach out to @jeffpaul or @desrosj or comment on this post, thanks!)

Release Coordination

The #6-1-release-leads channel will continue to be used for all coordination and conversation related to the 6.1.x releases. This matches the pattern of communication that worked well for previous minor releaseMinor 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. cycles!

Additional 6.1.x Releases

The 6.1.1 release is the final release planned for 2022, a 6.1.2 seems feasible around the end of January but the Core team will want to look to confirm formal 6.1.x Minor Release Leads by then who can help shepherd future minor releases on the 6.1 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". (cc: @audrasjb @marybaum).

#6-1, #6-1-1, #minor-releases

Abha Thakor 11:25 am on November 2, 2022
Tags: 6.1, 6.1.1 ( 7 ), 6.2 ( 90 ), agenda ( 1,045 ), dev chat ( 763 )

Dev Chat agenda, November 2, 2022

The meetings take place on Wednesdays at 20:00 UTC in the #core channel on Slack, and usually last an hour. All are welcome to attend or catch up via the summary.

About Dev Chat.

The publication of the Dev Chat agenda was held for the release party of WordPress 6.1to include the updates related to it.

1. Welcome

Introduction from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @marybaum

Dev Chat summary, October 27, 2022 – thanks to @webcommsat for writing it and for checking items for today’s agenda.

2. Announcements

WordPress 6.1 “Misha” was released, November 1, 2022
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/ 14.5 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). expected November 2, 2022

During the last week:
6.1 Release Candidate 6 – October 31, 2022

6.1 Release Candidate 5 – October 28, 2022

Gutenberg 14.4 was released –“What’s new in Gutenberg 14.4” release post, October 27, 2022.

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

A Week in Core – October 31, 2022

Performance chat summary, November 1, 2022 – has some ticketticket Created for both bug reports and feature development on the bug tracker. updates including WebP, AVIF images, Object Cache. Also some calls for reviews.

Core editor improvement: enhancing the writing experience, October 28, 2022. Find more about other improvements to the core editor.

4. Forthcoming releases

Updates from the relevant teams relating to releases.

a) Latest 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.1

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. for 6.1 find them at the dev-notes-6-1 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.). The Field Guide for 6.1.

b) Next 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.: 6.1.1

c) Next major: 6.2

post on Escaping Table and Field names with wpdb:prepare () which has been postponed to WordPress 6.2
the Core Editor meeting highlighted the priorities list for the Navigation Block in WordPress 6.2. Contributors have posted some revised designs for new editing experiences which are being proposed as a focus for the next release(s).

Is there an update on the discussion on earlies?

If you have an update from release leads or any teams collaborating on related items, please add a comment.

5. Component maintainers updates / tickets / requests for help

Please add your request for tickets you would like to raise as a comment.

6. Open Floor

Please add your Open Floor item as a comment.

Thanks to @marybaum for reviewing the agenda.

#6-1, #agenda, #dev-chat

#6-1, #6-1-1, #6-2, #agenda, #dev-chat

Jb Audras 8:56 am on November 1, 2022
Tags: 6.1, core ( 601 ), week in core ( 245 )

A Week in Core – October 31, 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 October 24 and October 31, 2022.

39 commits
69 contributors
43 tickets created
13 tickets reopened
46 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.1 🛠

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

Improve the wording of “Site Address” field description – #50629

Build/Test Tools

Ensure PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. related workflows are properly marked as failed – #55652
Hardcode the ref for the workflow dispatch on failure – #55652
Introduce a workflow for testing and building default themes – #56898
Correctly restore the wp_installing() status in Ajax tests – #56793
Move dbDelta() tests to the db directory – #56793, #56782
Move wp_handle_comment_submission() tests to the comment directory. – #56793
Move wp_mail() tests to the pluggable directory. – #56793
Move some @covers tags in the formatting group to the class DocBlockdocblock (phpdoc, xref, inline docs) – #56793
Move the tests for WP class methods to the wp directory – #56793, #56782
Move the tests for pluggable function signatures to the pluggable directory – #56793, #56782
Prevent wp_update_themes() from running in wp_ajax_update_theme() tests – #56793
Remove skipWithMultisite() and skipWithoutMultisite() from get_user_count() tests – #56793
Remove skipWithMultisite() from an Ajax test for attachments – #56793
Remove unused $user_ids property in Tests_Ajax_Autosave class – #56793
Rename classes in phpunit/tests/ajax/ per the naming conventions – #56793
Rename classes in phpunit/tests/comment/ per the naming conventions – #56793
Split the tests from category.php into individual test classes – #56793
Split the tests from multisite.php into individual test classes – #56793
Temporarily skip WOFF file test on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 – #56817

Bundled Themes

Twenty Twenty-Three: Merge the latest changes from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ – #56383

Coding Standards

Correct alignment in Tests_Ajax_Autosave::wpSetUpBeforeClass() – #56793

Database

Revert [53575] – #56933, #52506

Docs

Add a @since note for object-fit support in safecss_filter_attr() – #56855
Update a link to the Custom Elements spec in unsupported_valid_tag_names() unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. docblock – #56792

Editor

Allow arrays for deprecated asset types in 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. registration – #56707
Correctly apply Button block styles for classic themes – #56467
Ensure global styles are rendered for third-party blocks – #56915
Update packages for 6.1 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). 3 – #56467

Help/About

Add link to the 6.1 release video – #56357
Update About section images – #56357

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.

Change how WP_Textdomain_Registry stores the default languages path – #39210

KSES

Display a notice if any of the required globals are not set – #47357

Media

Add object-fit to the allowed list of CSSCSS Cascading Style Sheets. properties – #56855
Reverts get_attached_file() changes for normalized Windows paths – #56924

Query

Move cache key generation to its own method – #56802

Role/Capability

Revert the newly added update_role function for 6.1

Themes

Ensure custom global styles are imported properly – #56901

Upgrade/Install

Update $_old_files for 6.1 – #56934

Props

Thanks to the 69 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (9), @audrasjb (7), @peterwilsoncc (5), @desrosj (5), @spacedmonkey (4), @davidbaumwald (4), @bernhard-reiter (4), @hellofromTonya (3), @mukesh27 (3), @cbravobernal (3), @pbearne (3), @oandregal (2), @scruffian (2), @aristath (2), @flixos90 (2), @poena (2), @sergeybiryukov (2), @ndiego (2), @hellofromtonya (2), @ocean90 (2), @kebbet (2), @sabernhardt (2), @ironprogrammer (2), @andraganescu (2), @andrewserong (2), @mikeschroder (2), @jorbin (2), @costdev (2), @annezazu (2), @bosconiandynamics (1), @joedolson (1), @nendeb55 (1), @jrf (1), @TJNowell (1), @TobiasBg (1), @raduiason (1), @ckanderson22 (1), @KnowingArt_com (1), @pento (1), @pbiron (1), @doctorlai (1), @manfcarlo (1), @xknown (1), @seriouslysenpai (1), @ivanjeronimo (1), @adamsilverstein (1), @ramonopoly (1), @azaozz (1), @EidolonNight (1), @admwgn (1), @critterverse (1), @joen (1), @jpantani (1), @laurlittle (1), @cbringmann (1), @kellychoffman (1), @pablohoney (1), @mreishus (1), @tobifjellner (1), @anariel-design (1), @wildworks (1), @ajlende (1), @gigitux (1), @czapla (1), @richtabor (1), @digical (1), @kafleg (1), @mikachan (1), and @gziolo (1).

Congrats and welcome to our 3 new contributors of the week: @admwgn, @gigitux, @digical ♥️

Core committers: @sergeybiryukov (21), @davidbaumwald (5), @desrosj (4), @bernhard-reiter (3), @ryelle (2), @hellofromtonya (1), @antpb (1), @peterwilsoncc (1), and @swissspidy (1).

#6-1, #core, #week-in-core

Héctor Prieto 10:16 pm on October 31, 2022
Tags: 6.1, releases ( 46 )

WordPress 6.1 Release Candidate 6 (RC6) Now Available for Testing

WordPress 6.1 is scheduled for release tomorrow, November 1, 2022! This RC6 release is the last milestone for testing ahead of the official release.

The following issues have been addressed since RC5:

Unexpected quotes around search text in custom LIKE queries (see #56933)

This has resulted in a decision to postpone escaping table and field names with wpdb::prepare() to 6.2.

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 RC6

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

You can test WordPress 6.1 RC6 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.1-RC6

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.1 RC6 and update the “Tested up to” version in their readme file to 6.1 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.1 Field Guide, for more details on this release.

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

Check the Make WordPress Core blog for 6.1-related developer notes for further details on the 6.1 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!

Haikus for RC6

Table and field name
%i must wait for 6.2 now
Too weird for RC5

Props @annezazu, @marybaum, and @hellofromtonya for peer review.

#6-1, #releases

Craig Francis 9:43 pm on October 31, 2022
Tags: 6.1, dev-notes ( 542 ), dev-notes-6.1 ( 37 ), wpdb ( 6 )

Postponed to WP 6.2: Escaping Table and Field names with wpdb::prepare()

Support for %i to escape Table and Field names was postponed to 6.2, see:
https://make.wordpress.org/core/2022/10/08/escaping-table-and-field-names-with-wpdbprepare-in-wordpress-6-1/

A problem was found during RC5, where some extensions use field LIKE "%%%s%%", and expect the %s to remain unquoted.

This is undocumented behaviour. Officially the only time placeholders should not be quoted (for backwards compatibility reasons) is when using numbered or formatted string placeholders (this is unsafe, and should be avoided).

In this case, the first %% results in a literal "%", but this goes on to affect the %s.

For reference, developers should rely on wpdb::prepare() to quote all variables, so mistakes cannot be made. In this case it’s recommended to use something like the following:

$wpdb->prepare( 
     'field LIKE %s', 
     '%' . $wpdb->esc_like( $var ) . '%' );

Thanks to @AlanP57 for reporting, @hellofromtonya and @sergeybiryukov for reverting 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., @azaozz and @bph for helping document this, and everyone else for generally helping out.

#6-1, #dev-notes, #dev-notes-6-1, #wpdb

Jonathan Desrosiers 3:48 pm on October 28, 2022
Tags: 6.1, releases ( 46 )

WordPress 6.1 Release Candidate 5 (RC5) Now Available for Testing

WordPress 6.1 is scheduled for release next week on November 1, 2022! This RC5 release is the last milestone for testing ahead of the official release.

The following issues have been addressed since RC4:

get_attached_file(): New call to path_join() can have poor performance on NFS file systems (see #56924)

Installing RC5

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 RC5 on a test server and site.

You can test WordPress 6.1 RC5 in three ways:

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

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.1 RC5 and update the “Tested up to” version in their readme file to 6.1 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.1 Field Guide, for more details on this release.

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

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

How to Help Test WordPress

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

Haikus for RC5

Here’s two haikus for this final RC.

How about one more?
Getting closer and closer
Have you tested yet?

Last minute backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch.
Networked storage is tricky
Let’s make it faster

Props @davidbaumwald, @cbringmann, and @jpantani for post publish review, and @mikeschroder for the second haiku.

#6-1, #releases

Abha Thakor 11:58 pm on October 27, 2022
Tags: 6.1, dev chat ( 763 ), summary ( 878 )

Dev Chat summary, October 27, 2022

Notes from the weekly WordPress developers chat held in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/..

Start of the meeting on Slack.

The meeting was led by @marybaum and @webcommsat.

1. Welcome

Agenda followed for the meeting.

Summary from dev chat on October 19, 2022 thanks to @marybaum.

2. Announcements

Today is the last dev chat before 6.1 launches on Tuesday.

WordPress 6.1 Release Candidate 3 is now available. Thank you to everyone who supported this and to the testers at the release party.

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

@audrasjb gives a summary and thanks all the people involved on core tickets in the latest A Week in Core.

@priethor has published a guide to the final release process. You can start testing and other preparations for the big day now!

@sabernhardt discusses some new markup and styles in the world of Multisite.

@estelaris showcases a new design for HelpHub.

Gutenberg 14.4 has been released by first-time release leadRelease Lead The community member ultimately responsible for the Release. @JuanMe and is available in the plugin repo – Make blog post will be published tomorrow.

4. Releases

The following updates on 6.1 were shared or received by the release squad members.

@desrosj: two issues have been identified as potentially necessary fixes for an 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 (RC4), which is safe to anticipate at some point tomorrow.

Update from October 27, 2022: @desrosj and @priethor referred to the Release Day process post. This Release Day post will be kept updated as needed.

5. Components and tickets

a) @sergeybiryukov: Upgrade/Install component: Bringing attention again to the call to action for testing the Rollback feature on make/hosting.

Build/Test Tools component: A new workflow was introduced for testing and building default themes. Thanks @desrosj and @peterwilsoncc! Visit ticketticket Created for both bug reports and feature development on the bug tracker. #56898 for more details.

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. component: A performance issue in WP_Textdomain_Registry was identified and resolved. Thanks @swisspidy, @flixos90, @jonnyharris (check id), @ocean90, @costdev. More details on ticket #39210.

Date/Time, General, Permalinks component: No major news this week.

b) Testing 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 Dependencies

@afragen gave a reminder on the call to action for testing Plugin Dependencies. He requested feedback from hosting companies who have not as yet replied on the Rollback Updater Failure. The full discussion can be read in Slack – please note that there are some message threads as part of this discussion too.

@hellofromtonya added: “The goal is to collect data and feedback on shared web hosting platforms to address concerns. As many web hosts can get involved, the better.”

c) Mary shared a message from @nalininonstopnewsuk: Nalini has been supporting a new contributor, @Robin, who wants to get more involved with the project. He is interested in helping with the components, after coming to dev chat and hearing about them. He may be able to help with the login/ registration component. Nalini has suggested he comes along with her to some scrubs for the Quick/ Bulk Edit component and follows some tickets to learn more about components and TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.. She also asks if a maintainer in the APAC timezone would be able to share with this contributor how they maintain a component. There is currently no maintainer for the login/ registration component.

6. Open Floor

@pbiron drew attention to a discussion in core earlier in the week. Read the discussion in full in the Make WordPress Slack. The discussion focused on changes to the plugin that are not released into the wild in the form of a 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/ release for any testing/confirmation before being ported over for inclusion in Core (especially for a 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. during 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).).

Props to: @webcommsat for the dev chat summary, and to @marybaum for review.
Thank you too to those who confirmed various sections.

#6-1, #dev-chat, #summary

Jonathan Desrosiers 3:56 pm on October 27, 2022
Tags: 6.1, releases ( 46 )

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

WordPress 6.1 is scheduled for release next week on November 1, 2022! This RC4 release is the last milestone for testing ahead of the official release.

The following issues have been addressed since RC3:

Global Styles: Not working for third-party blocks (see #56915)
WP_Theme_JSON_Resolver::get_user_data_from_wp_global_styles is incorrectly cached (see #56901)

Installing RC4

You can test WordPress 6.1 RC4 in three ways:

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

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.1 RC4 and update the “Tested up to” version in their readme file to 6.1 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.1 Field Guide, for more details on this release.

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

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

How to Help Test WordPress

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

A Haiku for RC4

One last step needed
Making six point one better
Together we launch

Props @davidbaumwald and @cbringmann for post publish review, and @jpantani for the haiku.

#6-1, #releases

Héctor Prieto 12:47 am on October 25, 2022
Tags: 6.1, core ( 601 ), release-process ( 25 )

WordPress 6.1 Release Day Process

Preparation for WordPress 6.1 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:

The Dry Run started scheduled on 2022-10-31 14:00 UTC, but was aborted during triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. as a blocker was found. ❌
RC6 was launched to fix the blockerblocker A bug which is so severe that it blocks a release.. 🚀
The Dry Run was resumed on 2022-10-31 22:30 UTC. ✅
The 24-hour code freeze started on 2022-10-31 23:29 UTC, at the end of the Dry Run. ⏳
The stable release party will start on 2022-11-01 23:30 UTC in the #core Slack channel. 📅

Edit History

October 27th: Dry Run was rescheduled to start earlier, as proposed in #6-1-release-leads.
October 31st: Provided RC6 launch, 24-hour code freeze start time, and release party start time.

Dry Run ✅

The Dry Run is a key event as a final walk-through for the final release. As noted above, the current plan is to start it on 2022-10-31 14: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 any necessary updates are made in the src/wp-admin/includes/update-core.php file.
Pre-release scripts are run to ensure test suites, coding standards, and other automated 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 mandatory 24-hour code freeze goes into effect. This locking period started on 2022-10-31 23:29.

What does this mean? No source code for 6.1.0 (i.e., in the 6.1 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 blocker.

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 not, then the bug is targeted for 6.1.1.

The Stable Release Party 📅

The final release will occur on 2022-11-01 23:30 in #core.

The release party on November 1st 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 any last-minute issues 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.1 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.37, 4.9.22, 5.8.6, 5.9.5, 6.0.3, and 6.1 RC3, as well as any other versions possible.
Remove the 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 @desrosj and @zoonini for peer review.

#6-1, #core, #release-process

Jb Audras 10:55 pm on October 24, 2022
Tags: 6.1, core ( 601 ), week in core ( 245 )

A Week in Core – October 24, 2022

49 commits
75 contributors
63 tickets created
12 tickets reopened
51 tickets closed