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

Devchat agenda, November 30, 2022

1. Welcome

The WordPress Developers’ chat happens every Wednesday in the #core channel of 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. If you’re keeping track, here’s last week’s summary.

2. Announcements

The final versions of WordPress 3.7 – 4.0 have landed with a notice on each that they are no longer supported. Please encourage your users to upgrade to WordPress 6.1.1, running PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 or later.

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 RC1 will land while devchat is happening. More info to come!

Nominations for the 2023 Core team reps will close Friday.

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

From @estelaris, the Docs team is looking for feedback on a second iteration of DevHub’s new look.

From @audrasjb comes the latest A Week in Core.

@azaozz proposes a change to multiline commenting standards.

4. Upcoming releases

The next major is 6.2; the next minor is 6.1.2.

December is a great time to work on the things you would most like to see land in 6.2—before the release cycle ramps up in the new year.

5. Components and tickets

If you’ve got the tickets, the devchat group has the time.

6. Open floor

Add your item to the comments!

#agenda, #dev-chat

Dev Chat summary: Wednesday, November 23, 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.

Agenda followed.

Start of the meeting in the core channel of the Make WordPress Slack.

Summary from November 16, 2022 dev chat.

1) Announcements

Slack link.

  • What’s new in Gutenberg 14.6 has been published.
  • Support will end for WordPress 3.7 – 4.0 on December 1, 2022. The last release party for these versions will be on November 30, 2022. More in the post.
  • The WordPress developer blogblog (versus network, site) is in public 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.. Contributors needed. For more information please contact @bph or join the #core-dev-blog channel in the Make WordPress slack. Update post.
  • The call for nominations for 2023 Core Team Representatives is open until December 2, 2022. Self-nominations are welcomed.
  • DevHub is getting a new look. Feedback from developers needed, particularly on the way documentation has been split and the way 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. changed inside the articles in the code reference. Please comment in Figma or on this post from the documentation team.

2) Blog posts of note

Slack link.

3) Upcoming releases

Slack link.

The next major is 6.2; the next minor is 6.1.2. Look for updates next week.

4) Components and tickets

Slack link.

a) Components

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 needed with onboarding new maintainers. If you’re a maintainer with tips you can share and/or are willing to let someone shadow you, please contact @marybaum

b) Tickets

@helen highlighted ticketticket Created for both bug reports and feature development on the bug tracker. #57187 for people who had particular experience in containers.

5) Open Floor

Slack link.

No issues were discussed.

Props to to @marybaum and @webcommsat for facilitating; to @DavidPotter for the summary, and to @webcommsat and @audrasjb for reviewing; and to @estelaris, @audrasjb, @azaozz, and @sergeybiryukov for participating.

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

Devchat agenda, November 23, 2022

(Update November 23, 2022 – post added to section 3)

1. Welcome

Expect a brief check-in, since the United States is observing Thanksgiving week, and WordPress 6.2 will likely not kick off the pre-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. period before some 2023 planning.

To refresh your memory, here is last week’s summary. Thanks to @dpotter05 for compiling it!

2. Announcements

The project will end support for WordPress 3.7 – 4.0 on December 1. To that end, @peterwilsoncc will lead one last release party for those versions on November 30.

The WordPress developer blogblog (versus network, site) is in public beta! Find out more from @bph and check it out. Also, see how to contribute!

3. Blog posts of note

Got one to share? Post it in the comments.

Update: Nov 23, 2022 by @webcommsat: A Week in Core has been published.

4. Upcoming releases

The next major is 6.2; the next minor is 6.1.2. Look for updates next week.

5. Tickets, components and open floor

In the spirit of the season, please feel free to share something you appreciate either in the comments or in the chat.

See you at 20:00 UTC!

#agenda, #core, #dev-chat

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

Dev chat agenda: Wednesday, November 16, 2022

How did it get to be mid-November already?

Thanks to @webcommsat, @desrosj, and @nalininonstopnewsuk for stepping in on almost no notice when @marybaum was unavailable last week.

1. Welcome

Last week’s summary – props to @webcommsat.

2. Announcements

WordPress 6.1.1 maintenance release has landed!

Nominations are open for 2023 Core Team rep.

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

From @audrasjb, A week in Core.

From @helen, Improving the contributor experience.

And from @jeffpaul last week, the release post for WordPress 6.1.1 RC1.

4. Upcoming releases

The next major is 6.2.

The next minor is 6.1.2.

5. Components and tickets

This is the 6.2 alpha period — time to work on your favorite enhancements. This is also the time in the cycle when the community settles on the main areas of focus for 6.2, based on the product roadmap.

6. Open floor

Got a topic? Add it to the comments.

#agenda, #core, #dev-chat

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

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

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