Final releases of WordPress 3.7 – 4.0

As announced earlier this year, the security team will be dropping support for WordPress versions 3.7 – 4.0 as of December 1, 2022.

The final releases for these versions of WordPress will take place on November 30, 2022 (the last day of support). The release party is scheduled to begin at Wednesday, November 30th, 2022 at 00:00 UTC.

These release will update the notices in the WordPress adminadmin (and super admin) to inform users their version of WordPress is no longer receiving security updates.

The design for these notices can be found on the original post announcing the dropping of support; the patches are included on ticketticket Created for both bug reports and feature development on the bug tracker. #56786.

For the purpose of clarity: new versions of WordPress 4.1 and later will not be released on the 30th.

Editor chat summary: 16 November 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, November 16, 2022, 14:00 UTC in Slack. Moderated by @bph.

Announcements and Links

Key project updates

@andrewserong posted an update on the Layout Option post

@annezazu updated the High Priority list of the issues for Phase 2 Customization 

There are quite a few issues, for which designs are available, and they are now in need of developers.

Global Styles

Editor

Navigation

Templates

Should any of these issues interest you to tackle, and you have the bandwidth, you could add yourself as assignee via the project board

Also, even if you are not yet ready to contribute, and some of us have full plates, you can still chime in on the issues and discuss the most recent approach.

Task Coordination

@getdave commented on the agenda post: He’d like to flag this bugfix for the Link UI text replacement. It would be great to get some reviews on it. Dave also has been working with other contributors on the new UX for Editing Menus in the Navigation block. Reviewers and contributors are very welcome.

@paaljoachim commented on the Agenda post: I would like to bring some attention to this comment by @aaronrobertshaw
“We want a means of setting text decoration (including none) on individual blocks as well as 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. & global styles.”

Open Floor

 No open floor discussion topics were raised during the meeting.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Read complete transcript

Props to @paaljoachim for review

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

Dev Chat summary: Wednesday, November 16, 2022

The weekly WordPress developers chat meeting was held in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/. at 20:00 UTC.

Start of the meeting in Slack.

Announcements

Slack link.

WordPress 6.1.1 landed yesterday!

Nominations for 2023 Core Team Representatives are now open. The deadline for nominations is December 2, 2022.

Blogblog (versus network, site) posts of note

Slack link.

No other blog posts were shared.

Upcoming releases

Slack link.

For those new to dev chat, this is where any updates on the releases are shared.

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. is 6.2

WordPress 6.2 Development Cycle. This will be the first major release of 2023. 6.2 is in alpha and tickets are still early.

The next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. is 6.1.2

Due to upcoming holidays, these timelines were discussed:

6.1.2 planning post: mid-December 2022 or January 2023

6.2 planning post: January 2023

2023 planning post: January, likely ahead of the 6.2 planning post

Components and tickets

Slack link.

a) Components

For anyone new, there is a help / ticketticket Created for both bug reports and feature development on the bug tracker. update section each week in dev chat. Contributors can add requests to the agenda post for tickets they would like to highlight. If a maintainer can not make dev chat, they can also share their updates on the agenda.

If you are a maintainer, it is really helpful to share news about your component in dev chat live or on the agenda post. It is also a chance for all your efforts to be shared and to ask for more people to review a particular item.

No major news this week for these components:

  • 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
  • Help/About
  • Quick/Bulk Edit

b) Tickets

None were raised.

Open Floor

Slack link.

a) Removing functions during release candidates

This comment on the agenda post was discussed. It asserts that this 10/24/22 release candidate commit (54682) removed the reset() function, and asks for removing functions during release candidates to be disallowed – if it’s not already.

In the replies that followed, it was mentioned that when 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). methods or functions are changed, developers using them for tests could be sent a warning email, and that it could help if to use function_exists() to confirm functions are still available.

Props to @marybaum for leading the meeting, @davidpotter for writing the summary and to @davidbaumwald for reviewing, and to @webcommsat, @marybaum, @bph, @jeffpaul, @sergeybiryukov, @elrae, @joedolson, @desrosj, and @hellofromtonya for participating.

#6-2, #dev-chat, #summary

A Week in Core – November 14, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between October 31 and November 7, 2022.

  • 47 commits
  • 120 contributors
  • 97 tickets created
  • 27 tickets reopened
  • 104 tickets closed

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Administration

  • Add missing escaping for a few strings used as HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. attributes – #57093

Bundled Themes

  • Twenty Seventeen: Improve letter-spacing reset for non-latin alphabets – #56994

Canonical

  • Protect against error for term not exists queries – #55955

Coding Standards

  • Apply spacing changes after composer format#57057
  • Declare $wp_taxonomies global at the top of unregister_taxonomy()#57058
  • Use consistent spelling for “cacheable” in WP_Query::get_posts()#57012

Docs

  • Document the usage of $wpdb global in WP_Date_Query methods – #57033
  • Document the usage of globals in some functions – #57082
  • Fix block_editor_rest_api_preload() parameter type – #56810, #56792
  • Improve globals documentation in unregister_taxonomy() and wp_term_is_shared()#57058, #56792
  • Replace HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. links with HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in class-json.php docblocks – #57017, #56792
  • Replace HTTP links with HTTPS in class-pop3.php docblocks and JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. vendor readme file – #57017, #56792
  • Typo correction in get_registered_nav_menus() docblockdocblock (phpdoc, xref, inline docs)#57101, #56792
  • Various docblock fixes in Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site administration functions – #56792

Editor

  • Avoid running certain logic around theme.json parsing unnecessarily for classic themes – #56945
  • Correctly style separator blocks when only a background-color is defined – #56903
  • Improve Archive template description – #57001
  • Improve frontend performance for get_default_block_editor_settings()#56815
  • Improve how min/max font sizes are calculated for fluid typography – #57075
  • Improve performance of WP_Theme_JSON class by reducing usage of expensive array functions – #56974, #57067
  • Update 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 packages to the latest patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. releases – #57038, #56818, #56955, #56923

Filesystem

  • Return FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients./FTP Sockets exists() methods to a previous state – #56966, #51170, #28013

Formatting

  • Check that both normalizer_* functions exist in remove_accents()#56980

General

  • Use HTTPS for the b2/cafélog link in readme.html#57018

Help/About

  • Fix inconsistency in auto-updates help tabs – #56921

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.

  • Always pass $locale to load_textdomain()#57060
  • Initialize textdomain registry in wp_load_translations_early()#57051

Media

  • Prevent decoding attribute corrupting 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. data – #56969

Menus

  • Apply menu-item-has-children class in sub-menus – #56946, #28620

Networks and Sites

  • Replace “N/A” with “Not applicable” in choose_primary_blog()#57040

Posts, Post Types

Query

  • Bypass caching for filtered SELECTs – #57012
  • Don’t attempt caching if running a WP_User_Query before plugins_loaded – #56952
  • Prevent ID only queries erroring when starting the loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.#56948

Tests

  • Combine duplicate update_posts_count() tests – #57023, #56793
  • Correct the test for get_blogaddress_by_id() with a non-existing ID – #56793
  • Resolve WP_Query test failures on MariaDB due to indeterminate sort order – #57012
  • Restore blogblog (versus network, site) switching in update_posts_count() test – #57023

Text Changes

  • Improve the wording of the email sent to confirm site deletion – #56921
  • Remove capitalization on “site editing” – #57026
  • Replace “Full site editing” with “Site Editor” – #57026
  • Update @since mentions for [54786] changes – #57026

Themes

  • Improve WP_Query call getting global styles – #56900
  • Re-order valid link pseudo classes – #56928
  • Reduce usage of wp_get_theme function. – #57057
  • Revert one instance of wp_get_theme() from [54817] – #57057

Update/Install

  • Deactivate 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/ 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 version older than 14.1 – #56985

Upgrade/Install

  • Delete the comments-query-loop folder in wp-includes/blocks#57080

Props

Thanks to the 120 (!) people who contributed to WordPress Core on Trac last week: @mukesh27 (12), @SergeyBiryukov (12), @desrosj (11), @spacedmonkey (10), @peterwilsoncc (9), @audrasjb (7), @flixos90 (6), @costdev (5), @TimothyBlynJacobs (5), @ocean90 (4), @hellofromTonya (4), @sabernhardt (3), @aristath (3), @andrewserong (3), @NekoJonez (2), @wildworks (2), @mikachan (2), @dd32 (2), @ironprogrammer (2), @swissspidy (2), @upadalavipul (2), @miguelaxcar (2), @mxbclang (2), @czapla (2), @poena (2), @davidbaumwald (2), @mamaduka (2), @azaozz (2), @nithins53 (2), @ramonopoly (2), @kowsar89 (2), @joen (2), @cbravobernal (2), @namithjawahar (1), @rjasdfiii (1), @dilipbheda (1), @10upsimon (1), @Bjorn2404 (1), @itpathsolutions (1), @kadamwhite (1), @codesdnc (1), @nuvoPoint (1), @outrankjames (1), @oandregal (1), @manuilov (1), @pbiron (1), @webmandesign (1), @sippis (1), @petitphp (1), @mattkeys (1), @stentibbing (1), @rajeshraval786 (1), @pento (1), @pypwalters (1), @haritpanchal (1), @webaxones (1), @Chaton666 (1), @obenland (1), @oakesjosh (1), @subrataemfluence (1), @carazo (1), @johnwatkins0 (1), @claytoncollie (1), @Clorith (1), @chouby (1), @janthiel (1), @JeffPaul (1), @johnbillion (1), @amirrezatm (1), @lozula (1), @konyoldeath (1), @Mamaduka (1), @hiren1094 (1), @larsmqller (1), @LeonidasMilossis (1), @adamsilverstein (1), @innovext (1), @bernhard-reiter (1), @bph (1), @noisysocks (1), @mciampini (1), @talldanwp (1), @andraganescu (1), @scruffian (1), @get_dave (1), @isabel_brison (1), @ntsekouras (1), @ellatrix (1), @aaronrobertshaw (1), @gisgeo (1), @jchambo (1), @zodiac1978 (1), @gamecreature (1), @pkolenbr (1), @afragen (1), @jsh4 (1), @tyxla (1), @mcsf (1), @fpodhorsky (1), @kacper3355 (1), @davidvongries (1), @glendaviesnz (1), @mw108 (1), @joelmadigan (1), @rodricus (1), @jorbin (1), @azurseisme (1), @jrf (1), @vtad (1), @krunal265 (1), @ryankienstra (1), @riccardodicurti (1), @0mirka00 (1), @ndiego (1), @kevin940726 (1), @alexstine (1), @youknowriad (1), @cybr (1), @krupalpanchal (1), and @rajanpanchal2028 (1).

Congrats and welcome to our 31 (!!!) new contributors of the week: @miguelaxcar, @kowsar89, @rjasdfiii, @10upsimon, @Bjorn2404, @itpathsolutions, @codesdnc, @nuvoPoint, @outrankjames, @stentibbing, @carazo, @amirrezatm, @lozula, @konyoldeath, @larsmqller, @LeonidasMilossis, @innovext, @gisgeo, @jchambo, @gamecreature, @pkolenbr, @jsh4, @fpodhorsky, @kacper3355, @davidvongries, @mw108, @joelmadigan, @rodricus, @azurseisme, @krunal265, @riccardodicurti, ♥️

Core committers: @audrasjb (14), @sergeybiryukov (11), @peterwilsoncc (8), @desrosj (7), @flixos90 (3), @spacedmonkey (1), @ocean90 (1), @hellofromtonya (1), and @timothyblynjacobs (1).

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

Editor chat summary: Wednesday, 9 November 2022

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor 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, on Wednesday, November 09, 2022, 14:00 UTC.

General Updates

  • WordPress 6.2 Development Cycle.
  • GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 14.5 has been released and is available for download!

Async key project updates

Read the latest updates directly from the following tracking issues:

Task Coordination

@andraganescu

@mamaduka

Open Floor

Should we rethink how CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Chat works (again)?
The attendance and purpose of the chat seem to be both withering for the past six months or more. Let’s spend some time to figure out what happens and what could we change to make use of our time and participation in a relevant and impactful manner.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Read complete transcript

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

Dev Chat summary, November 9, 2022

The weekly WordPress developers chat meeting was held in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/. at 20:00 UTC.

Start of the meeting in Slack.

1.Welcome everyone

For anyone new to dev chat, you can find out more about this weekly meeting in the handbook.

The Dev Chat summary by @webcommsat and review by @pbiron and @audrasjb.

Agenda preparation – thanks to @webcommsat and @nalininonstopnewsuk for stepping in.

Meeting facilitators: @webcommsat and @desrosj, with @jeffpaul covering 6.1.1

2. Announcements

Reminder: WordPress 6.1 “Misha” was released, November 1, 2022

There is also now a 6.1 retrospective post – thanks @priethor

What’s new in Gutenberg 14.5 release post, November 9, 2022

3. Blogblog (versus network, site) posts

A Week in Core – November 7, 2022 – thanks to @audrasjb

No other blog posts were shared.

@webcommsat: a plug from the work from marketing, please do share social media posts from WordPress.org accounts. Social posts about the release continue to be very popular. If you are interested in stats, check out the marketing team’s blog as the notes report on this weekly.

Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. nominations and elections 2023

@webcommsat highlighted that teams are starting to think about team rep elections for 2023. More on this in future meetings from the current team reps @marybaum and @audrasjb. @chanthaboune is also planning to write a post on the Make/ Updates blog on team rep elections in the project, and has said teams that have a robust nomination process can get started for 2023. @jeffpaul offered to help with the nominations and elections process in core from his previous experience.

To keep this in people’s awareness and as encouragement to contributors, the team rep nominations will be on the agenda for future dev chats in the run up to the elections for 2023. Once the nomination post in published, contributors can self-nominate or nominate anyone they think would be good in this role. The post will be shared in dev chat. If people are potentially interested, they can also chat with @marybaum or @audrasjb before adding a nomination to the public post. The election list will be posted on the core blog, but as part of the process, there will be a confirmation check with anyone nominated to make sure they are happy to stand.

Background: Team Reps and what they do in the project; 2022 process for Core Team Rep nominations

Discussion followed on whether a core team rep needed to be a 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.. It was confirmed that it was not a requirement. @desrosj, and confirmed by …, “Honestly, it may be nice for both to not be a committer so that less coordination work falls on the shoulders of committers, and they have more free time to perform code reviews and commit duties. But being a committer also doesn’t disqualify you.”

4. Forthcoming releases

For those new to dev chat, this is where any updates on the releases are shared.

a) Latest major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.1

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1 find them at the dev-notes-6-1 tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). The Field Guide for 6.1.

Check out the 6.1 retrospective post – thanks @priethor.

@desrosj: All feedback and perspectives are welcome! Even if you were a casual contributor during the cycle, please do pass along your thoughts.

b) Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.1.1

WordPress 6.1.1 Planning is live.

  • Editor sync to core for tomorrow, November 10, 2022
  • 6.1.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 is scheduled for tomorrow, November 10, 2022 at 17:30 UTC
  • 6.1.1 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). planned for Friday November 11, 2022 at 16:00 UTC
  • plan for 6.1.1 release on November 15, 2022. The release party will start at 17:00 UTC and aim to be ready for testing of the minor release package around 18:00 UTC

These will both take place in the core channel of the Make WordPress Slack.

Everyone welcome to help. @jeffpaul do you have anything to add on 6.1.1

Call for help: @jeffpaul encouraged people to help test and provide feedback, assist with patches/PRs, and/or help with commits on items in 6.1.1.

Later in the meeting, @desrosj shared there are 21 tickets currently in the workflow for 6.1. Tomorrow (November 10), @jeffpaul and @desrosj will be ‘heavy handed punting’ these tickets.
Action: They asked for any ticketticket Created for both bug reports and feature development on the bug tracker. to be updated which people felt strongly about making it in the time available for this release.

A question was raised on timings for the 6.1.1 release. The 6.1.1 planning post helps with this and is currently pinned to the top of the core blog.

c) Next major: 6.2

The Development Cycle page is up on the core blog and will be updated as we move through the cycle.

No other updates on 6.2 at dev chat.

5. Component maintainers updates / tickets / requests for help

a) Components

For anyone new, there is a help / ticket update section each week in dev chat. Contributors can add requests to the agenda post for tickets they would like to highlight. If a maintainer can not make dev chat, they can also share their updates on the agenda.

If you are a maintainer, it is really helpful to share news about your component in dev chat live or on the agenda post. It is also a chance for all your efforts to be shared and to ask for more people to review a particular item.

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

@webcommsat: About/ Help and Bulk/ Quick Edit components – weekly focus on this will resume next week due to illness in the group. We will also be joined by two contributors who are interested in becoming maintainers or helping more with components. Timezones to enable this are being looked at.

b) Tickets

Action: @costdev requested if anyone is familiar with setting up WordPress to use FTPFTP FTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients., testing on #56966 would be much appreciated. There is a detailed and very helpful testing note is on the ticket.

#56966: Updating plugins with WP6.1 creates .maintenance file and leaves it

No other tickets raised nor added to the agenda.

6) Open Floor

@costdev asked if the 6.1.1 release party could be held at 18:00 UTC rather than the planned 17:00 UTC as there were a lot of clashes with the Upgrade/Install component meeting during 6.1. The move would reduce disruption and mean the Upgrade/Install team could join for testing releases. They had to regularly skip the component meetings which are at 17:00 UTC to make sure the release was installing correctly.

Action: Agreed time change. Final party will still start at 17:00 UTC but the packaging and testing will move to around 18:00 UTC. @jeffpaul to update the Make/Core post timeline.

Props to: @webcommsat and @desrosj for running dev chat, @webcommsat for the summary, and to @jeffpaul and @costdev for review.

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

Dev Chat agenda, November 9, 2022

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

About Dev Chat.

Thank you @nalininonstopnewsuk and @webcommsat for stepping in to help with the agenda, and to @robinwpdeveloper who will be helping with the summary for the first time at today’s meeting.

1. Welcome

Dev Chat summary, November 2, 2022 – thanks to @webcommsat for summarizing the discussion, and to @audrasjb and @pbiron for review.

2. Announcements

Reminder: WordPress 6.1 “Misha” was released, November 1, 2022

What’s new in Gutenberg 14.5” release post, November 9, 2022

Note: in the releases part of the agenda, there are important updates for this week on 6.1.1.

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

A Week in Core – November 7, 2022

4. Forthcoming releases

Updates from the relevant teams relating to releases.

a) Latest major release: 6.1

Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. for 6.1 find them at the dev-notes-6-1 tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.). The Field Guide for 6.1.

b) Next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.1.1

Information shared by @jeffpaul: there is a 6.1.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 scheduled for tomorrow, November 10, 2022 at 17:30 UTC and 6.1.1 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). planned for Friday November 11, 2022 at 16:00 UTC. These will take place in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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/..

c) Next major: 6.2

If you have an update from release leads or from any teams collaborating on related items, please add it to the comments.

5. Component maintainers updates / tickets / requests for help

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

6. Open Floor

Please add your Open Floor item as a comment.

#agenda, #dev-chat

What’s new in Gutenberg 14.5? (9 November)

“What’s new in 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/…” posts (labeled with the #gutenberg-new tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are posted following every Gutenberg release on a biweekly basis, discovering new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project.


Gutenberg 14.5 has been released and is available for download!

It consolidates the list view and document information, expands margin and padding support while improving spacing visualizers, and sets the groundwork for future releases with numerous code quality improvements and 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.

Table of Contents

Access the list view and document information all from one panel

Prior to Gutenberg 14.5, there were separate icons in the Editor toolbar for “List View” and “Details.” The Details popover presented a document outline and information like the character and word count. The List View panel displayed a hierarchical view of all blocks in the document.

The Details popover and List View panel have now been combined into a single panel offering a more streamlined way to manage the current document. This new “Document Overview” panel is accessible by clicking on the original List View icon in the toolbar.

Confidently edit 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. spacing using improved visualizers

Configuring block spacing (margin, padding) can be tricky, especially when determining how the spacing of one block will impact those blocks around it. Spacing visualizers significantly improve this experience by allowing you to “visualize” each change you make.

Gutenberg 14.5 enhances this functionality by displaying visualizers as soon as you hover over a spacing control rather than just when edited. This is a small change, but an important one since most CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks now support spacing controls. The release itself adds spacing to numerous comment-related blocks.

Changelog

Enhancements

  • Add block pattern categories’ descriptions to the 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/. and update the descriptions. (45244)
  • Create Block: Update templates to use APIs introduced in WP 6.1. (44185)
  • setAvailableMetaBoxesPerLocation: Merge new metaboxes into existing. (45156)
  • Spacing visualizer: Add option to trigger with mousover as well as value change. (44955)
  • Style Engine: Add support for dimensions.minHeight property. (45334)
  • Try: Add layout classnames to inner block wrapper. (44600)

Block Library

  • Audio, Video: Add toolbar button to add/remove caption. (45112, 45113)
  • Comment Template, Post Comment Count, Post Comments Form, Post Comments Link: Add spacing support. (45101, 45150, 45091, 45184)
  • Gallery: Register styles with Style Engine. (43070)
  • Navigation: Return undefined from useEffect. (45239)
  • Social Icons: Add rel attribute. (45469)
  • Video: Update tracks editor icon to text button. (45245)

Components

  • Block mover button: Do not show focus styles on pointer interactions. (45126)
  • BorderControl, BorderBoxControl, BorderRadiusControl: Update control components to allow 40px height. (41860)
  • BoxControl, Card, ToolsPanel: Remove unnecessary wrappers in stories. (45305)
  • Button: Change the color on the destructive button focus state. (44427)
  • Button: Refactor Storybook to controls and align documentation. (44105)
  • ColorPalette: Convert to TypeScript. (44632)
  • DateTimePicker: Add __next* props in Storybook. (45164)
  • FontSizePicker: Update design when withSlider is set. (44598)
  • FormFileUpload: Remove unused story file. (45286)
  • NumberControl: Add custom spin buttons. (45333)
  • RadioGroup: Mark as deprecated. (45389)
  • Navigator: Revert the removal of overflow styles from NavigatorScreen. (45303)
  • SelectControl: Add onChange, onBlur, and onFocus to storybook actions. (45432)
  • Storybook: Addon to wrap stories in max-width div. (45134)
  • TextControl: Set Storybook control types on help, label and type. (45405)
  • ToggleGroupControl: Add de-selectable variant. (45123)
  • ToggleGroupControl: Remove invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. props from types. (45114)

Post Editor

  • Edit Post: Improve distraction-free mode notices. (45348)
  • hasChangedContent: Remove obsolete blocks check. (45090)
  • Move document information and outline to list view panel. (44788)

Global Styles

  • Add :visited pseudo selector to 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. schema. (45236)
  • Embed, Gallery, Video: Add deprecation for the caption element. (45166, 45173, 45169)
  • File Block: Add a deprecation for the button element class name. (45159)
  • Table Block: Add a deprecation for the figcaption element class name. (45161)

Bug Fixes

  • Ensure block content is always returned as a string after processing. (45330)
  • Fix distraction free shortcut typo. (45186)
  • Fix resizeable editor scrolling. (45189)
  • Fix handling of nullish comments in the pot-to-PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher script. (45414)
  • Fix image caption supports Voice Control. (44850)
  • Fix PHP warning in pattern categories REST API controller. (45410)
  • Fix Prevent infinite 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. in Tag Processor in certain truncated documents. (45537)
  • Hide insertion point when moving out of the canvas. (45420)
  • Metaboxes: Perform hasMetaBoxes check on every save. (45145)
  • Prevent unexpected copying of the post title. (41284)
  • Raw Handling: When pasting bullet characters, convert to astericks for markdown converter. (45017)
  • Web Font: Fix ascent/descent-override property typo. (45125)

Block Library

  • Button: Reset background-image property for outline button style. (45234)
  • Cover, Search, Spacer: Fix control widths. (45329)
  • Navigation: Fix saving/loading experience of uncontrolled blocks. (45486)
  • Navigation: Add padding to buttons when Submenus Open on click is enabled. (44605)
  • List: Fix migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. when the nested list is invalid. (44822)
  • Page List: Allow direct selection of nested Page List block by avoiding dual rendering within block. (45143)
  • Site Tagline: Fix user permission HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. errors. (45140)
  • Site Title: Avoid 403 errors for users with low permissions. (45093)

Components

  • AnglePickerControl: Set Storybook label control type to text. (45122)
  • AutocompleteUI: Close popup when click happens outside of the popover. (44795)
  • BorderControl: Await floating-ui state changes when rendering/opening popover to fix 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. failures. (45241)
  • Button component: Fix RTL alignment when containing icon and text. (44787)
  • ColorPalette: Fix transparent checkered background pattern. (45295)
  • ExternalLink: Update to support onClick handler. (45214)
  • InputControl: Allow inline styles to be applied to wrapper instead of inner input. (45340)
  • ItemGroup: Fix RTL text alignment when item is clickable. (45280)
  • Popover: Fix deprecations. (45195)
  • PublishDateTimePicker: Retrieve all future posts in a given month. (44540)
  • SpacingSizesControl: Remove UnitControl inline style use. (45412)
  • TabPanel: Add tests and changelog for onSelect behavior change. (45211)
  • UnitControl: Fix disabled style is overridden by forms.css. (45250)
  • Visual Editor: Fix permission error. (45262)

Site Editor

  • Fix clipped body background style in the Site Editor. (45261)
  • Only mark the ‘Site’ menu item active when editing a home template. (42807)

Performance

Documentation

  • Add a readme to the letter spacing component. (45308)
  • Add changelogs for internal refactorings using inert. (45269)
  • Add “Do not use in production” message to content locking experimental 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.’s. (45291)
  • Add Storybook intro. (45115)
  • Code Quality: Fix some misspelled words. (45222)
  • Disabled: Update documentation to clarify the absence of inert polyfill. (45272)
  • Fix incorrect character in code example. (45355)
  • Fix missing anchor link in FAQ URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org. (45232)
  • FontSizePicker: Update changelog for #45041. (45180)
  • Updating curation document to include content lock ability. (44908)
  • useAnchorRef: Update deprecation message. (45302)

Code Quality

  • Block Editor: Improve MediaReplaceFlow tests. (45424)
  • Block Editor: Refactor align tests to RTL. (45152)
  • Editors: Refactor icon tests to follow no-container rule. (45422)
  • Fix indent and quote in dependbot.yml. (45167)
  • Fix PHP 8.1 deprecation for strncmp(). (44829)
  • Popover: Use new placement prop instead of legacy position prop. (44392, 44387, 44389, 44398, 44399, 44394, 44395, 44390, 44396, 44388)
  • PostTextEditor test: Wrap .blur calls in act(). (45243)
  • Replace the MainDashboardButton slot with a setting in the site editor. (45149)
  • Run script loader test. (45288)
  • Site Editor: Move the save view state to the edit site store. (45200)
  • Small follow-ups to the distraction free mode PR. (45151)
  • Tests: Use container instead of container.firstChild for snapshots. (45278)
  • useFocusOutside: Rewrite hook to TypeScript, rewrite tests to model RTL and user-event. (45317)
  • useFocusableIframe: Refactor to TypeScript. (45428)

Components

  • Add a popover variant prop and refactor popovers to use it, deprecate isAlternate. (45137)
  • Add parseQuantityAndUnitFromRawValue tests. (45260)
  • FontSizePicker: Rewrite unit tests to use userEvent and be more comprehensive. (45298)
  • BorderBoxControl: Improve tests. (45208)
  • ContextSystemProvider, useUpdateEffect, SlotFill, Snackbar, TabPanel: Refactor to pass exhaustive-deps. (45044, 44403, 44934, 44935)
  • Remove unnecessary .firstChild from tests. (45419)
  • Update some ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. 18 related types. (45279)

Global Styles

  • Add wp_theme_has_theme_json as a public API to know whether a theme has a theme.json. (45168)
  • Deprecate WP_Theme_JSON_Resolver:Theme_has_support(). (45380)

Tools

Testing

  • Add Playwright Compatibility-classic-editor Test. (43979)
  • Add end-to-end tests for Drag-and-Drop in the inserter. (44631)
  • Cleanup after the writing flow end-to-end tests. (45119)
  • Fix failing PHPUnit tests. (45265)
  • Fix uploading artifacts even when the tests are successful. (45187)
  • Migrate iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.-rendering test case. (44535)
  • Migrate tests to Playwright. (43963, 45267, 44916, 44507, 45393, 43964, 45202)
  • Re-enable skipped Gallery block end-to-end test. (45266)
  • Try fixing Site Title flaky end-to-end tests. (45160)
  • Update Playwright to v1.27. (45193)

Build Tooling

  • ESLint: Add and enable eslint-plugin-testing-library. (45103)
  • ESLint: Exclude Playwright tests from testing library rules. (45366)
  • Fix native Demo editor build error when using Xcode 14 to build to a physical device. (45120)
  • Remove comments from compiled styles. (43177)
  • Upgrade rtlcss to v4.0.0. (43208)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Post Editor

VersionLoading TimeKeyPress Event (typing)
Gutenberg 14.512.08s70.53ms
Gutenberg 14.411.97s69.15ms
WordPress 6.09.29s42.64ms

Site Editor

VersionLoading TimeKeyPress Event (typing)
Gutenberg 14.59.35s77.82ms
Gutenberg 14.411.56s74.72ms
WordPress 6.06.92s37.79ms

Note that the performance benchmark tests were automatically run against 6.0 rather than 6.1. This is because the “Tested up to” version of 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 was not updated to 6.1 once the new version of WordPress was published. This will be corrected for Gutenberg 14.6.

Contributors

The following contributors merged PRs in this release:

@aaronrobertshaw @alvitazwar @andrewserong @annezazu @aristath @BE-Webdesign @bph @brookewp @carolinan @chad1008 @ciampo @dcalhoun @dmsnell @ellatrix @fluiddot @GeoJunkie @georgeh @getdave @glendaviesnz @gziolo @Initsogar @jorgefilipecosta @jornp @jsnajdr @kevin940726 @KevinBatdorf @kienstra @Mamaduka @mikachan @mirka @noisysocks @ntsekouras @oandregal @pkorzelius @pooja-muchandikar  @ramonjd @SavPhill @scruffian @SiobhyB @Soean @t-hamano @talldan @tellthemachines @tyxla @walbo @youknowriad

The following PRs were merged by first-time contributors:

Kudos to all the contributors that helped with the release! 👏

Thanks to @priethor and @mamaduka for their assistance with the release, and props to @joen for the image and video!

#block-editor, #core-editor, #gutenberg

A Week in Core – November 7, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between October 31 and November 7, 2022.

  • 19 commits
  • 24 contributors
  • 93 tickets created
  • 8 tickets reopened
  • 53 tickets closed

WordPress 6.1 « Misha » was released on Tuesday November 2, 2022! 🚀

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

  • Remove role="img" from decorative SVG images – #56824

Build/Test Tools

  • Don’t ZIP theme ZIP files – #56898
  • Fix more set-output deprecated warnings – #56820, #56882, #56793
  • Combine duplicate update_posts_count() tests – #57023, #56793
  • Move update_blog_status() tests to their own file – #56793
  • Remove a custom callback for checking action call count in multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site tests – #56793
  • Restore blogblog (versus network, site) switching in update_posts_count() test – #57023

Bundled Themes

  • Twenty Twenty-One: Properly bump to version 1.7 – #56450

Coding Standards

  • Correct alignment in various files – #56791

Docs

  • Add brackets to a function name in get_page_template() description – #56792
  • Correct DocBlockdocblock (phpdoc, xref, inline docs) formatting for wp_sitemaps_enabled 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.#56792
  • Document the usage of globals in upgrade_550() and upgrade_560()#56983
  • Fix typo in a comment in wp_prepare_revisions_for_js()#56981
  • Replace HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. links with HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. in class-json.php docblocks – #57017, #56792
  • Typo correction in wp_dropdown_users() docblock – #56792
  • Update comments in wp_nav_menu() tests per the documentation standards – #56792

Editor

  • Improve Archive template description – #57001
  • CategoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. specific templates always appear as not found – #56902

General

  • Use HTTPS for the b2/cafélog link in readme.html#57018

Props

Thanks to the 24 people who contributed to WordPress Core on Trac last week: @desrosj (2), @mukesh27 (2), @audrasjb (2), @upadalavipul (1), @elifvish (1), @ryokuhi (1), @sabernhardt (1), @viralsampat (1), @colorfultones (1), @bgardner (1), @wildworks (1), @ndiego (1), @Chaton666 (1), @dilipbheda (1), @webaxones (1), @jrf (1), @franz00 (1), @ockham (1), @mikachan (1), @mamaduka (1), @rajanpanchal2028 (1), @haritpanchal (1), @SergeyBiryukov (1), and @aleksganev (1).

Congrats and welcome to our 2 new contributors of the week: @franz00, @aleksganev ♥️

Core committers: @sergeybiryukov (11), @audrasjb (4), @desrosj (3), and @jorgefilipecosta (1).

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

Dev Chat summary, November 2, 2022

The weekly WordPress developers meeting takes place in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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 Wednesdays at 20:00 UTC.

Slack link to the start of this week’s meeting.

Agenda, thanks to @webcommsat for preparing it and going through core posts.

Meeting facilitated by: @marybaum.

Dev Chat, October 27, 2022 meeting summary – thanks @webcommsat. Can you volunteer to help draft future dev chat summaries? Speak to @marybaum or @webcommsat if you can volunteer next week. There is help available.

2. Announcements!

WordPress 6.1 has landed!

@bph shared GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 14.5 RC1 has also landed! The pull request (PR), pending a release post.

@ndiego is the release leadRelease Lead The community member ultimately responsible for the Release. for Gutenberg 14.5.

During the last week, there have been two 6.1 Release Candidates:
6.1 Release Candidate 6 – October 31, 2022

6.1 Release Candidate 5 – October 28, 2022

Gutenberg 14.4

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

A Week in Core – October 31, 2022

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

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

4. Upcoming releases

a) 6.1

Additional to the links above.

@jeffpaul said he was most interested in what people are seeing in the forums, TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, etc. on concerns in 6.1 that might be earmarked for a 6.1.1 release.

@audrasjb: Aside from the WPML issue, I think it’s pretty quiet for a major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope..

@jeffpaul asked what people were hearing or seeing in relation to 6.1.

Jeff highlighted that @annezazu has posted a couple items in #6-1-release-leads: Slack message: 1 & 2.
@annezazu: wanted to bring in feedback from what I’m hearing on WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ and VIP — There are some fatal errors related to WPML and some infinite loops reported in Trac Ticket #56926. Initially she proposed to flag this in the #hosting-community channel.

@annezazu (post in the 6.1-release-leads on November 1): On a UXUX User experience related note — seeing these main issues in GitHub:

@audrasjb raised that there seems to be an issue with ManageWP backups on 6.1. He did not feel it needed to be addressed on the WordPress core side, and would be a fix to be done by the service owner, as with the WPML issue. 

@clorith raised Gutenberg issue #44166, reported pre-release. Highlighted that although it does not break usability, it does change visuals of sites in unexpected and some times not-so-nice-looking ways.
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. inserter missing is a big one though.

@jeffpaul said there were items that got set aside in the run-up to the 6.1 launch that hopefully were documented and added to the 6.1.1 milestone in Trac as well.

@clorith: The “+” button missing on some scenarios item Anne listed.

Under Open Floor in the agenda, @NekoJonez advised there are reports of MailPoet crashing on 6.1, but had not recreated it on two websites using it. It is raised on the master post on the forums.

b) The next major is 6.2

The development cycle for 6.2 – this will be the first major release of 2023 and is in the early planning stages.b

No update for this week’s dev chat.

c) The next minor is 6.1.1

@jeffpaul suggested a scrub to identify what realistically could be targeted in 6.1.1. He recommended that anything that contributors would like to be included is set as a 6.1.1 milestone in Trac or labelled accordingly in GitHub. This way the tickets can be considered in a 6.1.1 scrub.

In discussion with @desrosj, this minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. could be in the week of November 14, 2022. This date they believe would be most ideal to get things done before the US Thanksgiving holidays and before some contributors might less available with the holidays and end of year vacation schedules. He highlighted that there were definitely some items that we would want to try and get into this sort of a “fast-follow release” and would be best not to delay until January. [A post dev chat update is at the end of this section in the notes]

@marybaum asked about putting a release squad together.

@jeffpaul: “I think we might be able to find a way on the who but part of that will be determining what we’re trying to get into 6.1.1 so we know what’s needed for help.  Thus getting things identified and into Trac/GitHub appropriately will help.

@jeffpaul said he could probably lead a scrub on Friday, but would ideally need more contributors involved in the review. But before then, he called for everyone’s help to “share what you’re hearing and ensuring things are in Trac/GitHub so the scrub has a chance to collect what’s ideal in 6.1.1 so we can continue to push quickly if we’re going to realistically get something out the week of the 14th (which that timeline is a bit dependent on what it is we’re targeting in 6.1.1).”

@clorith: offered to assist for this Friday.

@desrosj: due to the quick turnaround, he felt it probably makes the most sense to use 6.1 squad members with appropriate skill sets and backgrounds based on what needs to be included. He said there was just not enough time to onboard a new squad for this one.

Post dev chat update: a new board specifically for 6.1.1 has been created: https://github.com/orgs/WordPress/projects/57/views/1.

WordPress 6.1.1 Planning (published by @jeffpaul on November 4, 2022)

5. Component Maintainers and Tickets updates/ requests for help

a) Components

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

@marybaum: Help/About and Quick/Bulk Edit: also no major news

@clorith: nothing new on Site Health.

@audrasjb: nothing new on Menus, Widgets, Upgrades.

No other updates from maintainers.

b) Tickets

None were raised.

6. Open Floor

@pbiron: raised the issue highlighted during Open Floor last week (thanks @webcommsat for including it in the summary last week). Read the discussion in full in the Make WordPress Slack. The discussion focused on changes to 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 that are not released into the wild in the form of a Gutenberg release for any testing/confirmation before being ported over for inclusion in Core (especially for a major release during RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).).

@jeffpaul replied that it was something at the top of his mind coming out of 6.1 and that he would like to to have a collaborative conversation with the 6.1 RCs, editor leads, and core leads to talk through the various pain points for core and Gutenberg processes, and how we might find ways to make that ‘work better’ for whoever steps in to help lead 6.2. Given that this group is likely focusing on 6.1.1 in the near term and that people will want some time off after that, it might be for January, unless someone from that group wants to try and schedule time before 2023?

@davidbaumwald: asked if this could be automated? Like PR commit exists in a release/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.)?  He highlighted that it is “a bit tricky” as there some changes that happen when porting GB code to core(namespacing functions, file paths, etc.) 

@pbiron highlighted discussion in the threads of the original message on Slack about the mechanics. He raised that what is concerning to some is that things from Gutenberg were merged into core for 6.1 before they were even merged into the Gutenberg 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., let alone a Gutenberg release.

@hellofromtonya: 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. merge expectations / criteria: likely needs consensus on what can and cannot be backported to Core, such as first must be formally released in Gutenberg.

@davidb: as there’s so much to watch over, suggested core could have some sort of bot that checks a pull request (PR) to ensure it was in a previous Gutenberg release/tag.

@jeffpaul recognized that there are likely things that core needs to consider adjusting/changing to better accommodate Gutenberg. He described it as a two-way relationship. He said he did not not want to try and introduce something that impairs the Gutenberg team’s ability to continue their always-impressive velocity and release cadence.

@pbiron called for an early “real” discussion to take place.

@marybaum suggested a post on the Core blog to start the discussion.

@jeffpaul: said he would like to co-ordinate async conversation with key people from 6.1 to try and collaborate on a make/core post with thoughts that can evolve into more legitimate proposals/tweaks leading into 6.2.

@pbiron: post-major-release ‘recap/lessons learned’ make/core posts have been fairly standard recently, and recommended that this discussion should certainly be part of putting that together for 6.1.

@jeffpaul agreed and added that he would like a bit more interactivity to that than a form or comment sprawl on a post to collect input that’s summarized in a make/core post. “We need to impact change here as it was not a smooth process and if not for some experienced contributors / committers / code owners we may have been much worse off in 6.1 (so again, thanks to everyone who did contribute and try to help along the way!)”

@marybaum suggested a special extra Dev Chat Session to discuss this. @clorith agreed as it is about core processes. Discussion about setting up an special channel for the discussion, and some felt there were already too many channels.

@davidbaumwald suggested starting with asynchronous feedback and logistics handling first. Then move to some sort of sync meetings, if necessary. He thought the retro is probably the first piece to the puzzle.

@hellofromtonya reminded for this discussion to be fruitful, contributors from #core-editor need to actively participate too.

@marybaum suggested a long post on the Make/Core blog along the lines that @desrosj had introduced the problem on Slack (link at the top of this discussion summary)

@hellofromtonya: in relation to @jeffpaul‘s suggestion, Tonya felt starting with the 6.1 release squad’s Core and Editor leads is a good starting place to get the ball rolling.

Tonya added: “One more thought: participation in release retrospective forms is / has been low. Active multi-channel discussions could help. ‘Channel’ does not mean slack channels.

“The goal is continuous improvement. These retrospectives after a release need more participation to collect more feedback to help make things better. Leveraging the power of open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL..”

@davidbaumwald: Yeah, or questions/feedback offered with no response.

@marybaum highlighted that if contributors who send feedback, get no response, they may be loathed to offer more feedback in the future.

Props to @webcommsat for the summary, to @marybaum for running the meeting and review, and to @pbiron, @audrasjb for review.

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