Dev Chat summary: Wednesday, December 21, 2022

If you’re new to dev chat, you can find out more about this weekly meeting in the handbook. (calendar)

This meeting was held on 8:00 pm UTC. The next dev chat will be on January 4, 2023 at 8:00 pm UTC. Note: there will not be a dev chat on December 28, 2022.

1) Welcome

Meeting facilitator: @marybaum.

Agenda followed; thanks to @webcommsat for preparing it.

Start of the meeting in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make WordPress Slack.

Summary from the December 14, 2022 dev chat.

2) Announcements

  • 2022 Core team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @marybaum welcomes incoming 2023 core team reps @hellofromtonya and @webcommsat.
  • The 2022 State of the Word video is now available on youtube.

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

4) Upcoming releases

a) 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

6.2 is expected to land in March according to the State of the Word address.

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

5) Components and tickets

a) Components

No issues were raised.

b) Tickets assistance / highlight

No tickets were raised.

6) Open floor

@robinwpdeveloper notes the new core contributors meeting that happens every other Wednesday at 19:00 UTC (calendar) to help new core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. get started is scheduled at a time that makes it difficult for people in APAC time zones to attend. He proposes there be a new core contributor meeting scheduled on the first Wednesday each month at 5:00 UTC. Please comment on this post with feedback.

From the Core team: Props to our 2022 core team reps @audrasjb and @marybaum! 2022 was a challenging year and was made possible thanks to the wonderful examples you’ve set in leadership, kindness, and inclusivity. Thank you for everything you’ve done and continue to do to make the WordPress project flourish.

Props to: @marybaum for running dev chat, @dpotter05 for the summary, and to @webcommsat and @marybaum for review.

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

Dev Chat summary: Wednesday, December 14, 2022

Summary of the weekly WordPress developers’ chat in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel at 20:00 UTC.

1) Welcome

If you’re new to dev chat, you can find out more about this weekly meeting in the handbook.

Meeting facilitators: @marybaum and @webcommsat.

Agenda followed; thanks to @marybaum for preparing it.

Start of the meeting 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/..

Summary from the December 7, 2022 dev chat.

2) Announcements

The State of The Word approaches! It happens 18:00 – 19:30 UTC on December 15, 2022 (1.00 – 2.30 PM EST).

There are just two days left to get your choices in for 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. for 2023. Voting closes Friday, December 16 at 23:59 UTC.

What’s new in Gutenberg 14.7 post.

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

The WordPress Survey is available. Share it, fill it in, and help take the WordPress project further.

There is a proposal for Enhancing the Scripts API with a loading strategy from @adamsilverstein

A dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, 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. about content locking and other such enhancements.

The FSE program is seeking volunteers to use replay-io-for-capturing-bugs.

There is an open retrospective about the WordPress 6.1 release process. Feedback is welcome.

4) Upcoming releases

a) 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

Core team rep @marybaum encourages contributors to help with getting new features ready early and work on tickets while there is time between releases.

b) 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. will be 6.1.2

This will likely be in January 2023 per the 6.1-release-leads channel – Slack link.

5) Components and tickets

a) Components

Build/Test Tools – @sergeybiryukov

  • Xdebug tests now run on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.2 too. Thanks @desrosj! Ticketticket Created for both bug reports and feature development on the bug tracker. #56009 has more details.
  • An issue in WP_HTTP unit tests with api.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ no longer returning the expected response after nginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. https://www.nginx.com/. update was identified and fixed. Ticket #57306 has more details.

General – @sergeybiryukov

  • Work has continued on renaming parameters that use reserved PHP keywords. Ticket #56788 has 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 – @sergeybiryukov

  • No major news this week.

Help/ About – @webcommsat

  • Maintainers been looking at some tickets awaiting review and at a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. in another ticket. If anyone has a view on this ticket #24567, it will be reviewed next.

Quick /Bulk Edit – @webcommsat

  • Maintainers been looking at this updated ticket #12940.

b) Tickets assistance / highlight

No tickets were raised.

6) Open floor

No issues were raised.

The next dev chat will be on December 21, 2022 at 20:00 UTC in the core Slack channel. This will be the last developers chat for 2022. It will restart in January 2023.

Props to: @marybaum and @webcommsat for running dev chat, @dpotter05 for the summary, and to @webcommsat and @marybaum for review.

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

Dev Chat summary: Wednesday, December 7, 2022

Summary of the weekly WordPress developers’ chat in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel at 20:00 UTC.

1) Welcome

If you’re new to dev chat, you can find out more about this weekly meeting in the handbook.

Meeting facilitators: @marybaum and @webcommsat.

Agenda followed; thanks to @marybaum for preparing it.

Start of the meeting 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/..

Summary from the November 23, 2022 dev chat.

2) Announcements

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.7 release due out shortly.

Voting is open for Core Team reps for 2023, until Friday, December 16, 2022.

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

A Week in Core – December 5, 2022

Core Accessibility Team Rep nominations are open and will be reviewed on Friday, December 16, 2022.

4) Upcoming releases

a) The next major is 6.2.

b) The next minor is 6.1.2.

No updates from the release teams at this time.

5) Components and tickets

a) Components

Quick/ Bulk Edit component update via @webcommsat

  • #12940 has a discussion to close the ticketticket Created for both bug reports and feature development on the bug tracker. or go for an alternative option
  • #16502 has a PR that is close to final review and merge for 6.2

Build/Test Tools component update via @sergeybiryukov

  • Basic e2e coverage for Gutenberg was added. Ticket #57197 for 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 component – @sergeybiryukov

  • No major news this week

b) Tickets

  • @webcommsat highlighted #57238 on WebP and the update from @adamsilverstein in the performance team’s meeting.
  • @costdev mentioned a new PR for Requests 2.0.0 #54504. The new PR should resolve the case-sensitivity issue and preload Requests 1 files before the upgrade begins, and should prevent the fatal errors we saw in 5.9 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. 2. Discussion on plans for this for earlies: aim to review this week and hopefully committed soon after.
  • @sergeybiryukov raised 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. ticket #6612, a discussion ticket for bumping the recommended PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher version to 8.0+
  • @petitphp asked for review and testing of #43867 and adding to the 6.2 milestone.

Comments on these and other tickets can be added directly on the tickets themselves.

6) Open floor

@annezazu: Call for volunteers to try out a tool called Replay to capture bugs in a more comprehensive way as part of the FSE Outreach Program. If interested, please respond to this post by December 28, 2022.

Props to: @marybaum and @webcommsat for running dev chat, @dpotter05 for the summary, and to @webcommsat and @marybaum for review.

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

Dev Chat summary: Wednesday, November 30, 2022

Here’s a summary of the weekly WordPress developers’ chat for November 30.

1) Welcome

If you’re new to dev chat, you can find out more about this weekly meeting in the handbook.

Meeting facilitators: @marybaum and @webcommsat.

Agenda followed; thanks to @marybaum for preparing it.

Start of the meeting 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/..

Summary from the November 23, 2022 dev chat.

2) Announcements

Slack link.

  • WordPress 3.7 – 4.0 have landed their final versions. Props to everyone who volunteered and to @peterwilsoncc for leading.
  • 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.7 is expected to land a 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). today.
  • Nominations for 2023 Core Team Representatives close this Friday.

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

Slack link.

4) Upcoming releases

Slack link.

a) 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

December is a great time to work on the things you would most like to see land in 6.2.

b) 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.

No updates from the release teams at this time.

5) Components and tickets

Slack link.

a) 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: no major news this week – @sergeybiryukov.

Site Health: nothing new to report – @clorith

Quick/ Bulk Edit Component

  • #54378 @webcommsat: This ticketticket Created for both bug reports and feature development on the bug tracker. could be an enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. if anyone wanted to work on it. This has been raised in scrubs previously.
  • #55549 This ticket has been closed for now after testing.
  • #56137 Raising this ticket as it has come up a couple of times in meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. groups – request to be able to add excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. in Quick Edit.

b) Tickets

  • No other tickets were raised.

6) Open Floor

Slack link.

a) WordPress 6.1 issue #45713

@bernhard-reiter: WordPress 6.1 has an issue with .is-layout-flex. The issue is complicated, and some testers are having trouble reproducing it. Full details are in the chat as it happened.

Props to: @marybaum and @webcommsat for running dev chat, @dpotter05 for the summary, and to @webcommsat and @marybaum for review.

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

WordPress 6.1.1 RC1 is now available

WordPress 6.1.1 Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 (RC1) is available for testing! Some ways you can help test 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.:

  • Use the WordPress Beta Tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
    • As this is a minor RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). release, select the Point ReleaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ to test:
    wp core update https://wordpress.org/wordpress-6.1.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.1.1 RC1 features 28 fixes on Core as well as 18 fixes for the BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor (view PRs merged from November 10th onwards).

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

  • Canonical: Setting a NOT EXISTS tax query in pre_get_posts action triggers a fatal error in wp-includes/canonical.php (#55955)
  • Editor: Massive (potential) performance issues within get_default_block_editor_settings (#56815)
  • Editor: Padding within table cells ignored (#56818)
  • Editor: Creating 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. templates for specific terms are wrongly displayed as not found (#56902)
  • Editor: Separator colors defined using background within theme.json for style variations are ignored (#56903)
  • Editor: Avoid running unnecessary expensive logic around theme.json parsing for classic themes (#56945)
  • Editor: Unable to add blocks on WP 6.1 – “+” button in editor shows up only in certain condition (#56955)
  • Editor: Improve performance of the WP_Theme_JSON class (#56974)
  • Editor: Merge bugfixes from 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/ into Core for WP 6.1.1 (#57038)
  • Editor: Fluid typography fixes for 6.1.1 (#57075)
  • Formatting: Check that the Normalizer class exists in remove_accents() (#56980)
  • General: Update to get_page_by_title in 6.1 changes WHERE clause (#56991)
  • 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.: Fatal error when loading translations early due to a DB error with WPLANG set (#57051)
  • I18N: Always pass $locale to load_textdomain() if we know the localeLocale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English. (#57060)
  • Media: Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. 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. in 6.0.3 (#56855)
  • Media: decoding="async" breaks my site (#56969)
  • Menus: WP 6.1-RC6: menu-item-has-children class is not being applied correctly (#56946)
  • Post, Post Types: WP 6.1 – get_page_by_title(null) returns a page (#57039)
  • Query: WP_Query::the_post causes a type warning when querying for ids, not full post objects (#56948)
  • Query: WP_Query caching discards posts_fields and posts_clauses['fields'] filters. (#57012)
  • Text Changes: Replace instances of “Full site editing” with “Site editor” (#57026)
  • Themes: register_block_core_template_part does WP_Query even on themes that do not support it (#56923)
  • Themes: WP_Theme_JSON_Resolver::get_user_data_from_wp_global_styles call to WP_Query incorrect. (#56900)
  • Themes: Twenty Twenty-Three: visited state of button links use the incorrect text color (#56928)
  • Themes: Reduce usage of wp_get_theme (#57057)
  • Upgrade/Install: Updating plugins with WP6.1 creates .maintenance file and leaves it (#56966)
  • Upgrade/Install: An unupdated Version of Gutenberg Fatally breaks the site on WordPress 6.1 Autoupdate (#56985)
  • Users: cache_users() not defined when calling get_user without field parameter or using all_with_meta or all (#56952)

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

  • Post Featured Image: Fix height/scale overwriting border inline styles (#44213)
  • Fluid typography: add font size constraints (#44993)
  • Allow direct selection of nested Page List block by avoiding dual rendering within block (#45143)
  • Fix popover deprecations (#45195)
  • Components: Refactor ColorPalette tests to @testing-library/react (#44108)
  • Convert the ColorPalette component to TypeScript (#44632)
  • List v2: 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 nested list is 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. (#44822)
  • Link to homeUrl from site editor view menu. (#45475)
  • Table Block: Apply borders and padding on both front end and editor (#45069)
  • Change the order of the pseudo-states in the pseudo selectors array (#45559)
  • Do not look for block variants, if not supporting block-templates (#45362)
  • Restore the empty paragraph inserter (#45542)
  • Cover: Avoid content loss when the templateLock value is all or contentOnly (#45632)
  • List: disable nested list drop zone so dropping list items works (#45321)
  • Switch background color to text color on block separator (#44943)
  • [WP6.1.1] AutoComplete: Revert to event.keyCode to fix IME composition issue (#45704)
  • [WP6.1.1] FormTokenField: Revert to event.keyCode to fix IME composition issue (#45703)
  • Fluid typography: adjust font size min and max rules (#45536)

What’s next?

The developer-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) is now in effect when making changes to the 6.1 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The final release is expected on Tuesday, November 15th, 2022. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #6-1-release-leads channel.

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

The WordPress 6.1.1 release is led by @desrosj, @mamaduka, and @jeffpaul.

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

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

WordPress 6.1 ‘Misha’ Retrospective

With WordPress 6.1 out in the world, it would be very helpful to this and future release squads if all those involved in contributing could take some time to reflect and share our thoughts on the release process to learn, iterate, and make future releases smoother. ✨

Anyone is welcome to participate in this retro, so please take a few moments to fill in the form or leave public feedback in the comments below. The survey is not anonymous if I need to reach out for further clarification, but your email address will not be shared or used for any other purpose.

The form and comments will be open until December 15th, 2022. The results will be reviewed and summarized in a follow-up post in this same blogblog (versus network, site) in January 2023.

Thank you, everyone, for your contribution to this release, and thanks in advance for taking the time to help make future releases even better!


Props to @desrosj for peer review

#6-1 #retrospective

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

WordPress 6.1.1 Planning

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

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


Coming after the WordPress 6.1 release earlier this week, both @desrosj and I are planning to lead a 6.1.1 release for some fast-follow items that came up near the end of the 6.1 release cycle and have bubbled up post-release such that we would like to try and ship before the end-of-year holidays start to pull folks away from contributing. If there is a critical bugfix that has a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing./PR ready, then please look to add those to the 6.1.1 milestone in Trac or the WordPress 6.1.1 Editor Tasks project board in GitHub.

Schedule

The following schedule is what’s currently planned for the release, any additional bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs, release candidates, or other items will be added here as they get scheduled.

Friday, November 4th, 2022 at 13:00 UTCBug Scrub focused on finalizing items for 6.1.1 in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress./GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ (Slack archive)
Thursday, November 10th, 2022 at 17:30 UTCBug Scrub ahead of RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). (Slack archive)
Friday, November 11th, 2022 at 16:00 UTC6.1.1 Release Candidate (Slack archive, ZIP download)
Tuesday, November 15th, 2022 at 17:00 UTC6.1.1 Release Party

Team

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

Release Coordinator: @jeffpaul

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

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

Release Coordination

The #6-1-release-leads channel will continue to be used for all coordination and conversation related to the 6.1.x releases. This matches the pattern of communication that worked well for previous minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. cycles!

Additional 6.1.x Releases

The 6.1.1 release is the final release planned for 2022, a 6.1.2 seems feasible around the end of January but the Core team will want to look to confirm formal 6.1.x Minor Release Leads by then who can help shepherd future minor releases on the 6.1 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". (cc: @audrasjb @marybaum).

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

Dev Chat agenda, November 2, 2022

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

About Dev Chat.

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

1. Welcome

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

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

2. Announcements

WordPress 6.1 “Misha” was released, November 1, 2022
GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 14.5 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). expected November 2, 2022

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

6.1 Release Candidate 5 – October 28, 2022

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

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

A Week in Core – October 31, 2022

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

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

4. Forthcoming releases

Updates from the relevant teams relating to releases.

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

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

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

c) Next major: 6.2

Is there an update on the discussion on earlies?

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

5. Component maintainers updates / tickets / requests for help

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

6. Open Floor

Please add your Open Floor item as a comment.

Thanks to @marybaum for reviewing the agenda.

#6-1#agenda#dev-chat

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