Estela Rueda 7:42 pm on May 19, 2022
Tags: 6.0 ( 64 ), core, dev chat ( 541 ), summary ( 557 ), week in core ( 173 )

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.

The newest post WordPress 6.0 release candidate phase
6.0 Development Cycle
6.0 Bug Schedule
WordPress 6.0 Field Guide – this brings together 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 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. related to the release
Dev Notes category in general
Help wanted: Test WordPress 6.0
Accessibility improvements in 6.0
WordPress 6.0 Editor Tasks Board
Status of Webfonts API for inclusion in WordPress 6.0 (April 22, 2022)

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

webcommsat AbhaNonStopNewsUK 12:26 am on May 18, 2022
Tags: 6.0 ( 64 ), agenda ( 744 ), core, dev chat ( 541 )

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

Jb Audras 9:48 pm on May 16, 2022
Tags: 6.0 ( 64 ), core, week in core ( 173 )

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

Improve WP_User_Query tests following [53362] – #53177

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

Colin Stewart 1:20 pm on May 11, 2022
Tags: bug scrub ( 69 ), core, props ( 5 )

Early Bug Scrub Schedule for 6.1

As work begins on 6.1, it’s time to schedule some early 6.1 bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub sessions.

These scrubs will happen once a week, usually scheduled for Thursdays at 18:00 UTC, though there may be some adjustments to accommodate releases, as well as religious and national holidays.

Right now, this only includes Early Scrubs. A release schedule for Alpha, 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., and 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). scrubs will follow soon.

Early Scrubs:

Focus: early tickets milestoned for 6.1, tickets that require more time or early testing.

Hosted by @costdev

Hosted by @audrasjb

Starting from Thursday, 23 June 2022, 20:00 UTC, @audrasjb will be hosting recurring 6.1 bug scrubs every Thursday at 20:00 UTC.

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

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

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

Accessibility Scrub: Every Friday, 15:00 UTC, in the #accessibility channel.
Help/About & Quick / Bulk Edit Scrub: Every Monday, 19:00 UTC, in the #core channel.
Editor Scrub: Every Tuesday, 14:00 UTC, in the #core-editor channel.
Testing Scrub: Every Friday, 13:15 UTC, in the #core-test channel.
Design Scrub: Every Tuesday, 16:00 UTC, in the #design channel.

Have a recurring component scrub or triage session?
PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @costdev on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. to have it added to this page.

Want to lead an Early Bug Scrub?

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

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

Your scrub can be added it to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!

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

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to @costdev on Slack.

Props to: @hellofromtonya for proof-reading.

#bug-scrub, #core

webcommsat AbhaNonStopNewsUK 8:00 am on May 11, 2022
Tags: agenda ( 744 ), core, dev chat ( 541 )

Dev Chat Agenda, May 11, 2022

With RC2 and waiting for some posts, this agenda is being published on May 11. Updated in item 4 with the RC3 date and next major 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.

The weekly WordPress developers chat takes place 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/. channel of Making WordPress at 20:00 UTC

Summary from Dev Chat on May 5, 2022 – thanks to @webcommsat for the notes. Who can do notes for the meeting on May 11?

2. Announcements

WordPress 6.0 RC2 is available for testing (released May 10, 2022).

Gutenberg 13.2 has landed!

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 9, 2022 (published May 11, 2022)

Performance Team Meeting Summary, May 10, 2022 – includes some updates on WebP, some POCs needed for the Site Health and Measurement sub groups. At the end of the post, there is a list of areas where help is needed.

Open floor item in the Editor Chat agenda for May 11, 2022 on a discussion around adding a new label to the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repo around issues that impact adoption. The aim would be to have an easier way to see, at a glance, what big issues are impacting the adoption of Gutenberg.

Full Site Editing Program Testing Call 14 – Rallying Recipe Reviewers. Deadline for feedback: 18 May 2022

Early 6.1 scrub schedule: Mondays at 18:00 from @costdev

4. Upcoming releases

Next major: WordPress 6.0

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

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). 3 Release Party on May 17, 2022 – meet in the #core Slack channel. As always with releases, there’s a chance this time may change the day of depending on how things are progressing. The time will be communicated across channels (#core-editor, #6-0-release-leads, and in #core). All welcome.

The next major bug scrub before RC3 will be on Thursday May 12, 2022, 21:00 PM UTC. The full bug scrub schedule for 6.0

5. Open Floor

If you are a component maintainer or running a bug scrub and have any updates not already mentioned under 6.0 updates, you can raise them in this section too.

#agenda, #dev-chat

Jb Audras 6:44 am on May 11, 2022
Tags: 6.0 ( 64 ), core, week in core ( 173 )

A Week in Core – May 9, 2022

35 commits
64 contributors
61 tickets created
12 tickets reopened
51 tickets closed

Code changes

Build/Test Tools

Add 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". to the workflow for testing branches
Allow the local development environment to run on Apple M1 machines without requiring local configuration changes – #52356
Ensure version number is in ‘X.X’ format after float math: Tests_Basic::test_security_md() – #55667
Pass GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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 – #55668
Improve the logic of the SECURITY.md test to check all supported versions – #55667
Move get_inline_data() tests to a more appropriate place – #55652
Temporarily disable the test for “Supported Versions” section of GitHub Security Policy

Code Modernization

Rename parameters that use reserved keywords in wp-admin/includes/template.php – #55650
Rename parameters to match native PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher functions in wp-includes/compat.php – #55650

Coding Standards

Remove extra space in wp-admin/admin-ajax.php – #55692

Docs

Correct parameter types for serialize_block() and serialize_blocks() – #55648, #54729
Improve plugin_install_action_links 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.’s docs – #55480
Remove @return void from various DocBlocks – #54729

Editor

Add 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. for Comment Template 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. – #55643, #55634
Sets ‘paged’ query arg only when there are comments: build_comment_query_vars_from_block() – #55658
Update WordPress packages for 6.0 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. 4 – #55567
Update WordPress packages for 6.0 RC1 – #55567

General

Add missing strong 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.) to some error messages – #54437

Help/About

Add link to 6.0 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., fix missing placeholder in string – #55434
Update the About section for 6.0 – #55434

Media

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

Query

Restore late compact() call for the posts_clauses_request filter – #55699

Quick/Bulk Edit

Additional tests for showing taxonomies – #49701
Remove duplicate HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. IDs – #55575, #35483

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

Fixes /wp/v2/pattern-directory/patterns endpoint response for slug parameter – #55617

Script Loader

Explain why 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. prevents concatenation – #55628
Fix i18n edge case breaking dependencies – #55628

Security

Update the Security Policy to include WordPress 6.0

Site Health

Remove unused variables in WP_Site_Health::get_test_plugin_version() – #55683

Users

Allow any DB field to be returned by WP_User_Query – #53177
Improve WP_User_Query tests following [53362] – #53177

Props

Thanks to the 64 people who contributed to WordPress Core on Trac last week: @costdev (6), @SergeyBiryukov (5), @audrasjb (5), @hellofromTonya (3), @ndiego (3), @justinahinon (3), @aristath (3), @gziolo (3), @mukesh27 (3), @johnbillion (3), @bernhard-reiter (2), @peterwilsoncc (2), @spacedmonkey (2), @jrf (2), @antonvlasenko (2), @poena (2), @hellofromtonya (2), @ironprogrammer (2), @darerodz (2), @afragen (2), @zieladam (2), @dlh (1), @marybaum (1), @annezazu (1), @webcommsat (1), @dansoschin (1), @chanthaboune (1), @cbringmann (1), @sergeybiryukov (1), @eidolonnight (1), @laurlittle (1), @JeffPaul (1), @NekoJonez (1), @ocean90 (1), @luisherranz (1), @czapla (1), @cbravobernal (1), @davidbaumwald (1), @timothyblynjacobs (1), @manooweb (1), @critterverse (1), @azaozz (1), @estelaris (1), @chaion07 (1), @figureone (1), @azouamauriac (1), @antpb (1), @rajeshraval786 (1), @dd32 (1), @pbearne (1), @kraftbj (1), @boniu91 (1), @jsnajdr (1), @fcoveram (1), @ugyensupport (1), @desrosj (1), @talldanwp (1), @Cybr (1), @david.binda (1), @5um17 (1), @greglone (1), @joedolson (1), @sabernhardt (1), @pbiron (1).

Congrats and welcome to our 3 new contributors of the week: @laurlittle, @rajeshraval786, @fcoveram ♥️

Core committers: @sergeybiryukov (18), @peterwilsoncc (7), @hellofromtonya (4), @ryelle (2), @audrasjb (2), @johnbillion (1), and @gziolo (1).

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

webcommsat AbhaNonStopNewsUK 11:38 pm on May 6, 2022
Tags: 6.0 ( 64 ), core, dev chat ( 541 ), summary ( 557 )

Summary Dev Chat, May 5, 2022

Link to the start of the meeting on the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds 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/. channel.

Agenda followed for the meeting.

Dev Chat summary from April 27, 2022 meeting – thanks to @webcommsat for doing these.

2. Announcements

WordPress 6.0 Release Candidate 1 (released on May 3, 2022). This was the hard string freeze for the 6.0 and branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". for the release. You can help by taking part in testing and make the release the best it can be. Thank you to everyone who came to the release parties this week.

WordPress 6.0 Beta 4 was released on May 2, 2022. It was not part of the originally published development cycle. It was aimed at providing an opportunity for testing some specific issues that were resolved since 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. 3.

Early focused meetings will take place on Mondays at a revised time of 18:00 UTC. Thanks to @costdev for working on this. These meetings will mean early tickets can get the attention they need, without disrupting devchat/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. Thanks to @costdev who will be running these meetings. The meetings will focus on:

targeting 3-4 tickets per meeting, discussing the proposal/bug
updating the ticketticket Created for both bug reports and feature development on the bug tracker. with opinions/findings
for some tickets that require investigation, some of the investigation might be possible during the meeting, otherwise we could schedule a date/time for contributors to get together to do any necessary deep-dives (either in chat, or via mob programming)

What’s New in Gutenberg 13.1 (April 27, 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/ 13.1 brings border support to the Columns 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., a number of improvements to the Comments blocks, along with a range of 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) enhancements.

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

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

Full Site Editing Program Testing Call 14 – Rallying Recipe Reviewers. Deadline for feedback: 18 May 2022

4. Upcoming releases

Next major: WordPress 6.0

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

@annezazu – Quick run down:

A new project board is being considered for 6.0.x releases for Core Editor issues as there are a few that are slated for a 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.. Stay tuned there but know bugs are being handled appropriately and are very much appreciated.
Check out this great post from @peterwilsoncc on what this current 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). phase means: https://make.wordpress.org/core/2022/05/04/wordpress-6-0-release-candidate-phase/
6.0 RC 2 is next week on May 10, 2022 and I hope to see you all at the release party! Expect it to be around the same time at 16:00UTC.

About page:
- @marybaum: Well I believe the About Page strings got committed ahead of the hard string freeze, and the rest of that process is going as it has in recent releases.
- @annezazu: The 6.0 video in progress will also be ready in time for a commit just before the final release. It will be linked in the About Page.
- @webcommsat: The ticket has some more details.
- @ryelle: The About page should be pretty much done – any feedback about things looking broken is welcome, but the only changes planned are to add in the correct links.

Some other useful resources on 6.0

A recap of some of the useful resources on 6.0 including the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.!

The newest post WordPress 6.0 release candidate phase
6.0 Development Cycle
6.0 Bug Schedule
WordPress 6.0 Field Guide – this brings together 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 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. related to the release
Dev Notes category
Help wanted: Test WordPress 6.0
Accessibility improvements in 6.0
WordPress 6.0 Editor Tasks Board
Status of Webfonts API for inclusion in WordPress 6.0 (April 22, 2022)

5. Open floor

Component maintainers

@sergeybiryukov: Build/Test Tools component: Two issues were fixed in the 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. suite:

Pass GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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, so that tests that should only run on trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. don’t unintentionally run on other branches. See ticket #55668 for more details.
Update the test for supported versions in the SECURITY.md file so that major versions like 6.0 are handled correctly. See ticket #55667 for more details.

General: The Microsoft IIS configuration file was updated to account for WordPress coding standardsWordPress Coding Standards A collection of PHP_CodeSniffer rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official standards for WordPress Core.. Testing is welcome from anyone running their own local IIS server on Windows. See ticket #53377 for more details.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., Permalinks: No major news this week.

Other open floor items

From the release documentation team, if any component maintainers or committers are still working on dev notes for 6.0 or have not had chance to reply to @bph, please can you let her know.
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 (WCEU) 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/. Core Tables, June 2, 2022 – @desrosj would you like to share anything on this today? We can share this in a future week.

You’re invited to the 6.0 RC 2 Release Party at 16:00 UTC on May 10, 2022 (click to add to your calendar). Meet in #core and be ready to wave hello, emoji reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/., and help test. As always with releases, there’s a chance this time may change the day of depending on how things are progressing. If the time is changed, it will be communicated across channels (#core-editor, #6-0-release-leads, and in #core). Hope to see you there!

Props to @webcommsat for the summary, @marybaum and @annezazu for reviewing

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

webcommsat AbhaNonStopNewsUK 8:00 pm on May 3, 2022
Tags: 6.0 ( 64 ), agenda ( 744 ), core, dev chat ( 541 )

Dev Chat Agenda, May 4, 2022

1. Welcome

Dev Chat summary from the meeting on April 27, 2022 – @webcommsat

2. Announcements

WordPress 6.0 Beta 4 (released on May 2, 2022).

Early focused meetings will take place on Mondays at a revised time of 18:00 UTC.

What’s New in Gutenberg 13.1 (April 27, 2022).

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.

Key links for 6.0 and updates from the squad will be in the agenda item 4, after these blog posts.

A Week in Core – May 2, 2022

Full Site Editing (FSE) Outreach Program Testing Call 14: Rallying Recipe Reviewers (April 28, 2022). Leave feedback by May 18, 2022

Any others?

4. Upcoming releases

Next major: WordPress 6.0

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

Useful resources/ calls for testing

6.0 Development Cycle
6.0 Field Guide (dev notes will continue to be added)
6.0 Bug Schedule
Help wanted: Test WordPress 6.0

5. Open floor

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

Could you help with writing the summary from dev chat for a future meeting? Comment below or message core team reps @marybaum and @audrasjb in the Core Slack channel.

Props to: @webcommsat and @marybaum for working on items for the agenda.

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

Jb Audras 7:05 am on May 3, 2022
Tags: 6.0 ( 64 ), core, meta6273 ( 3 ), week in core ( 173 )

A Week in Core – May 2, 2022

72 commits
55 contributors
43 tickets created
8 tickets reopened
65 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 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. 3 and Beta 4 🛠

Code changes

Administration

Trigger a notice for incorrect add_menu_page() parameter – #40927

Bootstrap/Load

Avoid a PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher warning when setting the $pagenow global in wp-includes/vars.php – #54700
Move some more administration-related hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. to admin-filters.php – #54795
Move administration related hooks to admin-filters.php – #54795

Build/Test Tools

Update the NPM dependencies to the latest versions – #54727
Reduce file size of About page texture – #48703
Add unit tests for wp_fuzzy_number_match() – #54239
Add unit tests for some XML-RPC functions – #53490
Ignore EOL differences in 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. tests – #54725

Bundled Themes

Note visually hidden text for translators – #55591
Update NPM dependencies for default themes – #54727
Twenty Twenty-One: Make translator comments referencing the post title consistent – #55564
Twenty Twenty-Two: Add three style variations – #55433

Code Modernization

Rename parameters that use reserved keywords in wp-includes/class-wp-comment-query.php – #55327
Rename parameters that use reserved keywords in wp-includes/class-wp-embed.php – #55327
Rename parameters that use reserved keywords in wp-includes/class-wp-image-editor-gd.php – #55327
Rename parameters that use reserved keywords in wp-includes/class-wp-image-editor.php – #55327
Rename parameters that use reserved keywords in wp-includes/class-wp-network-query.php – #55327
Rename parameters that use reserved keywords in wp-includes/class-wp-query.php – #55327
Rename parameters that use reserved keywords in wp-includes/class-wp-query.php – #55327
Rename parameters that use reserved keywords in wp-includes/class-wp-site-query.php – #55327
Rename parameters that use reserved keywords in wp-includes/class-wp-term-query.php – #55327
Rename parameters that use reserved keywords in wp-includes/class-wp-user-query.php – #55327
Rename parameters that use reserved keywords in wp-includes/class.wp-scripts.php – #55327
Rename parameters that use reserved keywords in wp-includes/class.wp-styles.php – #55327
Rename parameters that use reserved keywords in wp-includes/comment-template.php – #55327
Rename parameters that use reserved keywords in wp-includes/deprecated.php – #55327

Coding Standards

Remove extra alignment level in the data provider for wp_validate_boolean() tests – #54725, #54728
Remove extra spaces in docblocks of the Walker_PageDropdown class – #54728

Comments

Avoid DB error in comment 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. queries – #55218

Docs:

Add missing documentation for WP_*_Query::get_search_sql() method parameters – #54729
Adjust comments in Gruntfile.js per the documentation standards – #54729
Clarify the name and description of some parameters in the Walker class – #54729
Correct alignment for the customize_nav_menu_available_items 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. DocBlockdocblock (phpdoc, xref, inline docs) – #54729
Correct parameter types for serialize_block() and serialize_blocks() – #55648, #54729
Corrections and improvements to docblocks for function and hooks relating to fatal error handling – #54729
Docblock adjustements in the Walker class – #54729
Formatting corrections for various docblocks – #54729
Further clarify a comment for the main part of wp-login.php – #54746
Improve plugin_install_action_links filter’s docs – #55480
Improve documentation of the walker argument for various functions – #54729
Make the @return tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) for Translation_Entry::key() more precise – #55640
Remove @return void from various DocBlocks – #54729
Remove double spaces in tests/phpunit/README.txt – #55637
Use third-person singular verbs for function descriptions in Core Comment API and Comment template functions – #54729
Various docblock corrections – #54729
Various docblock corrections and improvements for changes introduced in 6.0 – #54729
Various docblock improvements – #54729

Editor

Fix core ‘Featured’ pattern categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. registration – #55567
Register ‘lock’ attribute for every 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. on the server – #55567
Show comment previews in the Comment 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. – #55634
Update WordPress packages for 6.0 Beta 3 – #55567
Update WordPress packages for 6.0 Beta 4 – #55567

External Libraries

Update the underscore library to version 1.13.3 – #55547

Mail

Improve the docblocks for actions and functions related to the parsing of authentication cookies – #54729

Media

Ensure wp_crop_image() returns correct file type – #55403
Ensure wp_read_image_metadata filter returns array for $iptc and $exif – #54637
Validate track number ID3 tags before use – #55204

Plugins

Improve plugin_install_description filter’s docs – #55480

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

Correct the schema for the wp/v2/block-directory/search endpoint – #53621
Fixes /wp/v2/pattern-directory/patterns endpoint response for slug parameter – #55617

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.

Increase cache hits in WP_Term_Query when using include and exclude parameters – #55352

Themes

Add internal-only 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.’s webfonts handler (stopgap) – #55567, #46370
Remove ‘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/’ as translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. context in _wp_theme_json_webfonts_handler() – #55567, #46370

Tools

Further automate backporting from Gutenberg to Core – #55642

Upgrade/Install

Prevent DB errors caused by web fonts API – #55632

Users

Validate WP_User_Query‘s fields argument – #53177

Widgets

Fix Classic Widgets screen toggle response on small screens – #48896

Props

Thanks to the 55 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (20), @aristath (15), @justinahinon (14), @poena (14), @jrf (14), @costdev (8), @peterwilsoncc (6), @zieladam (5), @hellofromTonya (4), @audrasjb (3), @sabernhardt (2), @hellofromtonya (2), @desrosj (2), @mamaduka (2), @antonvlasenko (2), @dlh (2), @darerodz (2), @ndiego (2), @pbiron (2), @afragen (2), @manooweb (2), @spacedmonkey (2), @pbearne (2), @kebbet (1), @kjellr (1), @azouamauriac (1), @inc2734 (1), @jffng (1), @gziolo (1), @bph (1), @jonoaldersonwp (1), @adamsilverstein (1), @kmix39 (1), @Boniu91 (1), @genosseeinhorn (1), @sergeybiryukov (1), @mat-lipe (1), @mjkhajeh (1), @felipeelia (1), @mukesh27 (1), @TimothyBlynJacobs (1), @johnbillion (1), @ntsekouras (1), @grandeljay (1), @Spacedmonkey (1), @chouby (1), @konradyoast (1), @timothyblynjacobs (1), @volodymyrkolesnykov (1), @sumitsingh (1), @mikeschroder (1), @bernhard-reiter (1), @czapla (1), @janh2 (1), and @azaozz (1).

Congrats and welcome to our 4 new contributors of the week: @kmix39, @genosseeinhorn, @mjkhajeh, @grandeljay, @janh2 ♥️

Core committers: @sergeybiryukov (32), @peterwilsoncc (10), @johnbillion (8), @audrasjb (7), @gziolo (5), @hellofromtonya (3), @desrosj (3), @spacedmonkey (1), @mikeschroder (1), @jffng (1), and @davidbaumwald (1).

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

webcommsat AbhaNonStopNewsUK 10:17 pm on April 27, 2022
Tags: 6.0 ( 64 ), core, dev chat ( 541 ), summary ( 557 )

Dev Chat Summary, April 27, 2022

Notes from the weekly WordPress developers chat held 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/. of Making WordPress.

Start of the meeting in Slack

1. Welcome

Dev Chat summary from April 20, 2022 meeting

The agenda followed for April 27, 2022

2. Announcements

WordPress 6.0 Beta 3 released on April 26, 2022. This represented the soft string freeze for this release.

Status of Webfonts API for inclusion in WordPress 6.0 (April 22, 2022)

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

A Week in Core – April 25, 2022 – thanks to @audrasjb

An update on Preferred Languages Project – thanks to @swissspidy for the post (April 27, 2022) on the 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 plans for users to be able to select multiple preferred languages in settings. The post includes a call for contributions to development and testing. For background, more than half of all WordPress sites in the world use a language other than US English.

Exploration to enable better dev and visitor experiences with blocks (April 27, 2022)

4. Upcoming releases

Next major: WordPress 6.0

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

a) @annezazu: from the co-release coordinator side, 6.0 is moving along with 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 planned for next week:

some questions around the post comments query blocks work to resolve this week
lots of excellent work around preparing 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 a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and the 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. by the docs folks
the modified and private approach for webfonts API has shipped in beta 3: I will leave a comment on that post for good measure as an update.

b) @costdev: For those who haven’t seen it yet, there is a new TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. keyword, changes-requested. Slack reference

c) Shared by @dansoschin as an update on the about page for 6.0, earlier in the marketing meeting:

there’s work on a short video overview to accompany the release, to drop on release day

the About Page, which is part of the release package, will be more-or-less finalized in copy form and design form at the end of this week. The purpose of this file, as currently established, is to provide a brief update of what’s in the release and provide links to resources where you can find more information.

d) Update via @abhanonstopnewsuk: she is collecting information to share with Documentation, Training, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on what extra information/ steps would be useful for non-devs to take part in testing the release.

Some other useful resources on 6.0

5. Open floor

a) @costdev: As we approach RC1 and branching off for 6.1, I wanted to propose an early focused meeting on Mondays.

This would be similar to 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, but instead of trying to get through as many tickets as possible, it would be about targeting 3-4 tickets per meeting, discussing the proposal/bug, and updating the ticketticket Created for both bug reports and feature development on the bug tracker. with opinions/findings. For some tickets that require investigation, some of the investigation might be possible during the meeting, otherwise we could schedule a date/time for contributors to get together to do any necessary deep-dives (either in chat, or via mob programming). This would allow for early tickets to get the attention they need, without disrupting dev chat/bug scrubs. I’m happy to run these meetings.

What does everyone think?

comments from the meeting were largely in agreement with the idea of this meeting
this would clash with the current About Page/ Help Page and Quick Edit/ Bulk Edit regular scrub, which maintainers would look at the options to move to another time slot.
@costdev: is happy to start them as soon as we branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". for 6.1 then and I’ll see about getting them set up as recurring at that stage. Update: alternative date for the early-focused meeting, Mondays 18:00 UTC

b) @webcommsat: From the release documentation team, we are reaching out to component maintainers about dev notes for 6.0. Please look out for a message from @bph.
@bph: thanked maintainers who had already replied.

c) @marybaum: Dev Chat summary volunteers needed to help with compiling items for the agenda and drafting the summary. @webcommsat has kindly been persuaded to do the dev chat summary again this week. Please do think about volunteering for a future week.

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

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

Welcome!

Communication

2. Announcements

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.

4. Upcoming releases

Update

Recap of useful resources on 6.0

Release update relating to Learn WordPress and associated docs

5. Open Floor

1. Welcome

2. Announcements

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

4. Upcoming releases

5. Open floor

Code changes

Administration

Build/Tests Tools

Bundled Themes

Coding Standards

Database

Docs

Editor

Help/About

Media

Menus

Query

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.

Users

Props

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

Want to lead an Early Bug Scrub?

2. Announcements

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.

4. Upcoming releases

5. Open Floor

Code changes

Build/Test Tools

Code Modernization

Coding Standards

Docs

Editor

General

Help/About

Media

Query

Quick/Bulk Edit

Script Loader

Security

Site Health

Users

Props

2. Announcements

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

4. Upcoming releases

5. Open floor

1. Welcome

2. Announcements

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.

4. Upcoming releases

5. Open floor

Code changes

Administration

Bootstrap/Load

Build/Test Tools

Bundled Themes

Code Modernization

Coding Standards

Comments

Docs:

Editor

External Libraries

Mail

Media

Plugins

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.

Themes

Tools

Upgrade/Install

Users

Widgets