Abha Thakor 8:07 am on September 1, 2022
Tags: 6.0, 6.1 ( 93 ), dev chat ( 624 ), summary ( 680 )

Dev Chat Summary, August 31, 2022

1. Welcome and introduction

The start of the weekly WordPress developers chat meeting in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team channel can be found at this Slack thread.

Meeting agenda preparation and facilitation: @webcommsat and @marybaum. Thanks to everyone who sent in materials or shared tickets.

Meeting summary: @webcommsat. Review: @marybaum, @costdev.

References: Contributor Handbook. Purpose and role of weekly Dev Chat, held on Wednesdays at 20:00 UTC.

2. Announcements

@bph: 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/ 14.0 is in the repo, and a Make Core post is in progress. The performance tests need another look. Props to @desrosj for getting it over the finish line and release leadRelease Lead The community member ultimately responsible for the Release. @onemaggie. Post dev chat – What’s new in Gutenberg 14.01.

3. Blogs posts

Core editor improvement: refining the template creation experience (August 25, 2022)

Post dev chat: A Week in Core (August 31, 2022) thanks to @audrasjb.

4. Upcoming releases

a) The next major is 6.1.

No specific updates from the Release Squad.
Some useful links:
6.1 development cycle
Bug scrub cycle

Other 6.1 related items:
– @pbearne: is keen to get these two filters #56045 and #37930 committed. Action: @davidbaumwald is looking into this. Anyone else able to assist too?

– @jeffpaul: Worth noting that 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 is in less than 3 weeks and historically we’ve tried to ensure features land week prior so ideally any new features/enhancements get in by Friday, September 9, 2022.

– @webcommsat: On an adminadmin (and super admin) task, the roadmap post for 6.1 does not seem to be linked from the development cycle page. Can this be added? The post also refers to a second post to follow, is this expected before Beta 1? Action: Follow-up.

– @webcommsat: A question for the release leads, do we have any update on the pre-release walkthrough date? It was provisionally set for September 13, 2022.
Update Sept 1 in release leads channel: pre-release walkthrough confirmed for September 13, at 16:00 UTC. @jpantani is organizing the event via Zoom. Announcement post to follow.
Action: Add walkthrough on next week’s dev chat agenda for an update.

b) Minor releases
Key links for anyone wanting to know more about the latest 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.0.2.
WordPress 6.0.2 security and maintenance release
HelpHub page for 6.0.2

@sergeybiryukov: 6.0.2 includes 3 security fixes, 12 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. fixes for core, and 5 bug fixes for 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. Please update if you haven’t yet.

c) Discussion on early timeframe
Core 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/. discussion highlighted by @jeffpaul: What should be the definition of the early timeframe within a major release cycle?

@clorith: Noting that the early keyword is in the workflow handbook under https://make.wordpress.org/core/handbook/contribute/trac/keywords/, and since it’s aimed specifically at committers, I would presume it’s aimed at committing early.

@davidbaumwald: @jeffpaul and I had a document somewhere that was going to be the prelude to a post about defining early.

@costdev: Just throwing this in as a consideration for the Make post: we might also consider having additional keywords for specificity. e.g. needs-early-decision, etc.

@clorith: In my head, “early discussion” is “discuss as much as you want until a decision is made, if it’s still in the discussion phase, it’s not ready for milestoning”. But that’s something that would likely come out of a make post with feedback I suspect .

@jeffpaul: I think the most important bit will be the timing of what “early” means.
Action: @clorith volunteered to draft a make/core post about it to gather input, and help cement this with a proper definition. Further discussion can be added on that post.

This has a related item on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher.
Ticketticket Created for both bug reports and feature development on the bug tracker. #55603 for discussion. This issue was highlighted at a bug scrub last week. Wider feedback is requested on the approach on the ticket 2nd-opinion php82

@hellofromtonya: The above ticket is something @jrf and I will be working on following up to live working session held recently.

@hellofromtonya: Please note, WordPress Core will not be fully compatible with PHP 8.2 by the time the new PHP version is released. Handling of dynamic properties has a POC but will not be ready in time. The plan is to commit.

5. Components and tickets

Are you a component maintainer? Shepherding a ticket? Beta 1 is four weeks away, scheduled for September 20, 2022.

@sergeybiryukov:

General: Code modernization efforts have continued on preparing WordPress core for PHP 8.2. Thanks @jrf, @antonvlasenko, @costdev, and everyone testing the PHP 8.2 PRs! Ticket #56033 for more details.

@clorith

Site Health has been making strides this past week with a few tickets going in (and a few being gardened and closed as no longer relevant, or non-reproducible).

@webcommsat: Just a reminder to our other component maintainers, please do share your updates and any help you need. You can add these asynchronously to the dev chat agenda or to the Summary on the Make/ Core blogblog (versus network, site). You can also raise any tickets that you would like to highlight for help, especially if they are planned for the next release.

6. Open Floor

– Topic description core Slack channel. Action: agreed to add Dev Chat date and time.

Props to @webcommsat for the dev chat summary and @marybaum and @costdev for review, and to those who facilitated the meeting.

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

Abha Thakor 2:30 am on August 31, 2022
Tags: 6.0, 6.1 ( 93 ), core ( 491 ), dev chat ( 624 ), summary ( 680 )

Summary, Dev Chat, August 24, 2022

These are the notes from the weekly WordPress developers chat held on Wednesday August 24, 2022.

1. Welcome and introduction

The start of the meeting discussions on the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team channel can be found at this Slack thread
Meeting Agenda for August 24, 2022: @marybaum
Meeting preparation and facilitation: @webcommsat, @marybaum, and everyone who sent in materials or shared tickets
Meeting notes: @webcommsat
Meeting notes Editor/Review: @nalininonstopnewsuk, @marybaum, @costdev. There has been a delay in publishing this summary due to the availability of any reviewer because of the holidays. Thank you for your understanding.
Summary from Dev Chat August 17, 2022: thanks to @webcommsat and reviewer @marybaum
For those new to the team, the Contributor Handbook can be a good place to start. Find out more about the weekly Dev Chat meeting, held on Wednesdays at 20:00 UTC.

2. Announcements

WordPress 6.0.2 RC 1 has landed! Please download and test.

3. Blogblog (versus network, site) posts

This is not all the posts published on the core blog during the last week, but major items highlighted for comment or queries.

A week in core (published August 25, 2022) – thank you @audrasjb

Feedback by September 9, 2022 is requested on a new system for updating HTML attributes.

The 16th Full Site Editing Call for Testing is still open. This features a simpler testing exercise. Deadline is September 2, 2022. Thanks @annezazu for the update.

4. Upcoming releases

a) The next major is 6.1.

@marybaum shared that @priethor has asked for green-yellow-red lights looking ahead 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. release and almost all green were reported in the #6-1-release-leads channel.
No other updates were received on the agenda or during the meeting from the squad.

b) The next minor is 6.0.2.
The Release Candidate (RC1) is out.

Update via @sergeybiryukov

next release party is expected Tuesday August 30, 2022 at 16:00 UTC in the #core 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/.
list of tickets fixed so far
6.0.x project board for Gutenberg

5. Components and tickets

This section is for updates from component maintainer or anyone shepherding a ticketticket Created for both bug reports and feature development on the bug tracker.. Beta 1 is five weeks away, so the time is ripe!

Updates from @sergeybiryukov for Build/Test Tools, Database, General, Themes, Date/ Time components

Build/Test Tools

As of yesterday, PHPUnit test runs on 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/ Actions include PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.2, though addressing compatibility issues is still a work in progress. PHP 8.2 is expected to be released at the end of November 2022. Thanks @jrf.

More details at: Ticket #56009 Prepare for PHP 8.2

Compatibility with the recent versions of MariaDB (10.6+) 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/. (8.0+) was improved. With these and some other changes, specifically skipping tests for non-implemented REST API methods, most of the test runs from various hosting environments on the Host Test Results page successfully pass now, except for PHP 8.2.0alpha2 for now.

More details at: Tickets #51740 and #53623

Database

General: Code modernization efforts have continued on preparing WordPress core for PHP 8.2.

Thanks @jrf and @antonvlasenko.

More details at: Ticket #56033 PHP 8.2 explicitly declare all known properties

Themes

A 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. Themes 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. is now available on the Add Themes screen, to match a similar filter in the WordPress.org Theme Directory. Thanks @luminuu and @audrasjb.
Ticket #56283 Add “Block theme” filter under “Add themes” for more details.
The support for Update URI theme 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. was added to core. This allows third-party themes to avoid accidentally being overwritten with an update of a theme of a similar name from the WordPress.org Theme Directory. Thanks @dd32, @meloniq, @costdev
Changeset [53933] and ticket #14179 for more details.

Thanks everyone who contributed to those tickets!

Date/Time, 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. components

Permalinks: No major news this week.

Site Health component

@clorith:

Tickets #54508 (add more information to site health message) & #54617 (add more details when site health checks fail) could benefit from copy review; @webcommsat and @marybaum will follow up.

Updates on Help/About and Bulk/ Quick Edit components

@marybaum: We moved one ticket on: #56210.

Thanks @webcommsat @ogleckler @nalininonstopnews and @sergeybiryukov for comments / discussion on components in these two components. Thanks for the commit @audrasjb.

@nalininonstopnewsuk:

Quick Edit/ Bulk edit – on the next few Mondays we will continue to look at some of the tickets and doing some triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.. We did some exploration on one particular ticket this last week. We will bring it to a bigger scrub potentially after that depending on progress.

As Mary had lost her internet connection, @nalininonstopnewsuk added: Thank you everyone for sharing. Dev chat is a good place for component maintainers to be able to share progress on their tickets and highlight any issues. You can let the core team reps know if you need some assistance too.

As a newer maintainer, I appreciate the outreach from the team reps and from documentation at releases time. Dev chat also helps get more people to look at a specific point in an issue if needed. Just putting in my thoughts. @marybaum: Very valuable! Thanks so much.

Upgrade/ Install component

@costdev: Upgrade/Install: While we’ve had reviews from individual committers who happen to be on the Security, Docs and Polyglots teams, we’d like to make an official request to these teams here in dev chat and in their respective channels to review the Rollback Update Failure feature plugin for any potential issues.

No further update from maintainers nor tickets. Thanks everyone who has added tickets above.

6. Open Floor

@marybaum: We are going to talk about dev chat 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. US 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/..

There were no other items added to the agenda today apart from the links we have already shared. Nothing else was raised.

@marybaum: Also huge thanks, Nalini, for stepping in and helping lead this chat today! Thanks and for the info you have sent across on some words for the glossary relating to the handbook Nalini. @nalininonstopnewsuk: Thank you for the handbook link about what dev chat does and its purpose. It is very interesting and useful.

Props to: @webcommsat for the dev chat summary, and @marybaum, @nalininonstopnewsuk, and @costdev for review.

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

Dan Soschin 4:50 pm on August 23, 2022
Tags: 6.0, minor releases ( 19 ), releases ( 35 )

WordPress 6.0.2 RC1 is now available

WordPress 6.0.2 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). 1 (RC1) is available for testing! Some ways you can help test WordPress 6.0.2 RC1:

Use 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
- As this is a minor 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, select the Point 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. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
Use 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/ to test:
wp core update https://wordpress.org/wordpress-6.0.2-RC1.zip
Directly download the Beta/RC version.

What’s in this release candidate?

6.0.2 RC1 features 12 bug fixes on Core, as well as 5 bug fixes (view PRs merged from July 5th onwards) for 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.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

The following block editor issues 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/ are fixed:

What’s next?

The developer-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) is now in effect when making changes to 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"..

The final release is expected on Tuesday, August 30th, 2022. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ 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/. #6-0-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

The WordPress 6.0.2 release is led by @sergeybiryukov @gziololo

#6-0, #6-0-2, #minor-releases, #releases

#6-0, #minor-releases, #releases

annezazu 7:28 pm on July 7, 2022
Tags: 6.0, retrospective ( 13 )

WordPress 6.0 Retrospective Recap

This post seeks to summarize the feedback received from the 6.0 retrospective, shared on May 27th. Thank you to the eight people who took the time to share their feedback and to those who also did so publicly on the post itself. To keep the post succinct, some non-actionable feedback has been consolidated.

Please keep in mind that these are just suggestions and things to consider for the future rather than items that will be implemented later.

What would you keep?

Outside of the following, there were repeat mentions of how collaborative, kind, and communicative the squad was as a whole in answering pings, making decisions, and supporting each other.

Early sharing of the feature highlight grid to influence About page, release video, etc.
Weekly check-ins.
Dedicated release channel for coordination.
Redundancy with co-leads in various roles to allow for more focus on details, higher capacity for work, etc.
Lack of heroic efforts and last-minute dashes
Collaborative decision making, e.g. with regard to the WebFonts 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.
Structured release parties

What would you add?

More support for Docs & Training resources, matching devs that worked on issues with those writing docs/training.
Clearer documentation around resolving tricky issues during a release and when to bring leadership in.
Consider having apprenticeship roles for release squad roles to create a backup and for the continuity of the project.
A reimagined About page that designers can build directly using blocks.
Improved automations, specifically for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Lead role.
Release squad should be picked as early in the release process as possible to allow time to prepare.
Consider adding documentation lead role for End User documentation
Improve process for identifying items that need 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., including labeling of PRs that need dev notes, considering multiple types of flags (DevNotedev 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. / MiscDevNote / 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.), ensuring documentation is in place for what needs dev notes, and implementing automation to collect all items.
Checklist for each member of the squad at each release phase for improved coordination.

What would you remove?

Confusion/concerns around the Webfonts API situation.
Confusion around the initial 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 post and what role everyone played. This was very quickly resolved.
Backporting months worth 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/ PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes before the release.
Lack of decisions and process around stabilizing and introducing experimental APIs, leading to a backlog.
Improving the process of introducing, stabilizing, and phasing.
Secrecy around jazzer leading to a lot of complexity around release time.
Too many places for tracking documentation updates from the docs team.
Complicated process for dev notes, including recommendations to stop using comments on the 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/ DevNote tracking issue for collecting all dev notes and change deadline to Beta 1 to give docs team more time.
Implementing a feature freeze in Gutenberg a week earlier to leave more room for integration with WordPress Core and reduce the length of beta releases.
Share more marcoms around the behind the scenes work with performance and 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) so the UIUI User interface changes aren’t over indexed on messaging wise.

How did the collaboration feel?

This section included ways for one to indicate how much they agreed or disagreed with a statement around collaboration.

Collaborating on this release was easy results

Pie chart showing that 62.5% of people strongly agree, 25% slightly agree, and 12.5% slightly disagree that collaborating was easy.

Collaborating on this release was enjoyable results

Pie chart showing that 75% of people strongly agree and 25% slightly agree that collaborating was enjoyable.

Collaborating on this release was efficient results

Pie chart showing that 50% of people strongly agree, 12.5% slightly agree, and 37.5% slightly disagree that collaborating was efficient.

Collaborating on this release was well organized results

Pie chart showing that 50% of people strongly agree, 37.5% slightly agree, and 12.5% slightly disagree that collaborating was well organized.

The release process was transparent and easy to follow

Pie chart showing that 37.5% of people strongly agree, 37.5% slightly agree, and 25% were neutral that the release process was transparent and easy to follow.

Would you like to be a part of future squads?

87.5% of people said “I have been part of the release squad and I will gladly repeat”. 12.5% of people said “I haven’t been part of the squad but I would like to try in the future”.

Next Steps

At a high level, a few discussions and follows up have already occurred that others can participate in:

A follow up post was done since the retrospective sharing improvements and automations for the Core Editor release role in light of the experience of those this release cycle.
An open discussion is underway around how best to 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. PHP changes.
An open discussion is underway on the topic of improving ad clearing part of the backlog for experimental APIs.

Outside of the above, it’s clear that there are some process improvements particularly around documentation to consider including a role for End User documentation, changing the way documentation updates are tracked across multiple places, and the way in which dev notes are wrangled.

If you are interested in being a part of 6.1’s release squad and working to improve the experience, please share in the comments of the 6.1 planning post.

Thank you to @davidb @zieladam for reviewing.

#6-0, #retrospective

annezazu 4:52 pm on July 5, 2022
Tags: 6.0, 6.0.1 ( 7 ), minor releases ( 19 ), releases ( 35 )

WordPress 6.0.1 RC 1 is now available

WordPress 6.0.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). 1 (RC1) is available for testing! Some ways you can help testing WordPress 6.0.1 RC1:

Use 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
- As this is a minor 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, select the Point 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. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
Use WP-CLI to test: wp core update https://wordpress.org/wordpress-6.0.1-RC1.zip
Directly download the Beta/RC version.

What’s in this release candidate?

6.0.1 Release Candidate 1 features 11 bug fixes on Core, as well as 18 bug fixes (view PRs merged in June & July) for 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.

#55668 – Build/Test Tools: Pass 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/ Actions environment variables to the Docker container.
#55681 – Fix block-templates theme support not present in /themes REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. endpoint
#55808 – About page: Replace video thumbnail image
#55837 – Resolve WP_Term_Query cache problem
#55890 – Fix caching issues in WP_Term_Query class.
#55997 – Remove meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. from oembed allow list
#56093 – Register Comments Query 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. from metadata to enable title and description translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization..
#56097 – Themes: Revert the change of theme preview width on Add Themes screen.
#56126 – Block Patterns: Update the value used for keywords.
#55810 – Bundled Themes: Revert the Twenty Ten theme version to 3.6.

The following block editor issues from GitHub are fixed:

#41423 – Lower the priority of the gallery gap css so it loads after the block layout css
#41487 – Add utility classnames back to blocks that have layout attributes specified
#41354 – Block Library: Fix JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. Error in AvatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name. Block
#40329 – Media & Text: Remove font size declaration from template
#41631 – Comment Author and Date blocks: aligned editor markup with the frontend
#41328 – Handle no variation case in the block transform menu
#40710 – Fix/block 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. icon prop errors
#40593 – Prevent opening the links in editor for Latest Posts
#40671 – Navigation block “Open on click”: Inherit font style and font weight
#41627 – Comments Block: fixed issue with custom font sizes and links color
#40560 – Reuse code of the editor placeholder across Post Comments and Post Comments Form
#40563 – Improve the logic for warnings for Post Comments Form placeholder
#41603 – Post Comments Form: Add button that enables commenting to warning
#40799 – Ensure only the main query is modified when resolving template for new posts
#40859 – Strip whitespaces in render_block_core_cover before injecting the featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts..
#41827 – Post Template: Ensure layout classnames are not attached to inner li elements
#41907 – Pasting: Fix performance regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. due to removeWindowsFragments
#42131 – Post Comments Form: Fix warning 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.

What’s next?

The dev-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) is now in effect when making changes to 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"..

As per the proposed WordPress 6.0.1 schedule, the final release is expected on Tuesday, July 12th, 2022. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ 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/. #6-0-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

The WordPress 6.0.1 release is led by @sergeybiryukov @zieladam.

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

Jb Audras 10:32 pm on June 27, 2022
Tags: 6.0, core ( 491 ), week in core ( 215 )

A Week in Core – June 27, 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 June 20 and June 27, 2022.

49 commits
43 contributors
71 tickets created
9 tickets reopened
44 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 and on the next minor, WP 6.0.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