March 29 Dev Chat is canceled in favor of WordPress 6.2 final release party

After a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. with date formats prompted a new code freeze and the delay of the 6.2 release, the release leads decided to cancel this week’s Dev Chat.

Why?

Release parties for major versions tend to run three or more hours. So it’s likely that the 6.2 release won’t have finished by the time dev chat normally starts. Plus, if the release does finish early, lots of usual dev chat attendees will be pretty tired.

Please join the squad for the release of WordPress 6.2 on 2023-03-29 at 17:00 UTC.

The next Dev Chat is 2023-04-05 at 20:00 UTC.

#core, #dev-chat, #meeting

Dev chat Summary, March 22, 2023

1. Welcome and housekeeping

@francina led the chat in the core channel of the Make WordPress Slack.

The agenda — thanks to @webcommsat, has a full list of 6.2 links. Highlighted posts are below.

Last week’s dev chat summary, March 15, 2023 – thanks to @marybaum

2. Announcements

  • Gutenberg 15.4 arrived Wednesday, March 22, 2023 — thanks to @greenshady and @welcher for getting the post out in such a short time after release.
  • WordPress 6.2 RC3 landed on Tuesday, March 21, 2023.
  • Silent RC4 will address a backward compatibility issue (#57967) on March 23. More on the regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. is in this discussion on Slack.

And:

  • The WordPress Developer Blog is out of betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process., and officially launched! Please check it out. You are most welcome to:

3. Highlighted posts

And:

4 Tickets and components

  • The Bulk and Quick Edit component

@francina raised ticketticket Created for both bug reports and feature development on the bug tracker. #11302 “Bulk editing posts should pre-fill fields with the same value / allow for removal”

@oglekler brought up a related ticket: #19859 “Bulk Edit” Missing The Ability To Edit Tags

@azaozz suggested that it is time to make a large update to this component, taking care about bugs and enhancements.

@marybaum said the maintainers, who also include @webcommsat, @oglekler, and @nalininonstopnewsuk, will follow up. (Ed. note: Look for this starting in April, once the current release has landed.)

5. Open floor

WCEU 2023 preparations

@estelaris asked for help answering Interview questions for Make Teams reps about Contributor Day.

Documentation

@estelaris and asked for review and comments on ticket #48998 Documentation Structure Block Editor Handbook

The Developer Blogblog (versus network, site)

@azaozz suggested publishing 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. there as well (right now 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. has only a link in the footer). 

@jeffpaul requested to auto-publish posts in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel and @bph will follow up with it.

A week in Core

@bph suggested renaming ‘A week in Core’ to ‘A week in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.’, because it doesn’t cover 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/ project activity on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, and they are highlighted separately in What’s New in Gutenberg. @francina offered to continue this discussion in the P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. (Ed. note: that is, this very Make/core blog) in the comments section of the last Week in Core.

Broad questions

@sereedmedia drew attention to a marketing ticket with a cornerstone What is WordPress?

@francina: What brought you to check dev chats in the first place? A lively, if brief, discussion followed. Francesca also suggested more discussion next week—and a post on the Core blog, to stimulate asynchronous conversations.

Next week’s dev chat will be Wednesday, March 29, 2023, at 11:00 PM GMT+3 in the Core Slack channel. See you there!

Props to @francina for leading dev chat, to @webcommsat for the agenda preparation, @oglekler for the summary, and @marybaum and @webcommsat for review.

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

Dev Chat Agenda, Wednesday March 22, 2023

The next WordPress Developers Chat will on Wednesday, March 22, 2023 at 20:00 UTC in the core channel of the Make WordPress Slack.

1. Welcome and housekeeping

Dev Chat summary, March 15, 2023 – thanks to @marybaum

The meeting’s scheduled facilitator will be @francina

@oglekler and @webcommsat are on the rota for this week’s meeting summary.
If you would like to volunteer for the summary, do add a comment to this ticketticket Created for both bug reports and feature development on the bug tracker. for @webcommsat.

2. Announcements

WordPress 6.2 RC3

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/ 15.4 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). is scheduled (now available for testing)

3. Highlighted posts

Call for volunteers to help with 6.2 end user docs from the release docs group.

4. Releases

Useful information on the next major WordPress release 6.2.

The schedule release is now only two weeks away on March 28.

Also check the #6-2-release-leads channel for the latest updates.

For information:

  • WordPress 6.2 has branched.

More updates from the Release Squad to come in the meeting.

5. Request for help with tickets/ components/ blockers/

If you have a ticket or request to help, please add a comment to the agenda post. Please indicate if you will be attending the meeting live and be able to highlight the issue further if needed.

If you are unable to attend dev chat live, you can add further details of the issue you would like highlighted either in comments, or message CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team reps @webcommsat and @hellofromtonya with the additional information to raise in this week’s meeting for you.

6. Open floor

Items for this agenda item and the previous one are welcome from across time zones. Please add suggestions in comments on this post. Thanks.

Props for agenda preparation @webcommsat, review @hellofromtonya and @marybaum.

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

Dev chat Summary, March 15, 2023

1. Welcome and housekeeping

@francina led the chat. The meeting start on 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/..

The agenda, prepared by @webcommsat, has a full list of 6.2 links, only new links are listed below.

Last week’s dev chat summary, March 8, 2023 – thanks to @ironprogrammer.

2. Announcements

WordPress 6.2 RC 2 landed on Tuesday, March 14, 2023! Please download and test, and remember that in the 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). period:

  • It takes two committers to commit code to the 6.2 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 6.3 branch is open for early tickets, proposals and more
  • There’s a hard string freeze on the 6.2 branch

Gutenberg 15.3 landed Monday, March 13, 2023.

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/ 15.4 is underway.

3. Highlighted posts

@annezazu tells how and why the Navigation section of the Site Editor is gone from 6.2 RC 2.

@audrasjb recaps A week in Core.

@webcommsat adds these new links relating to 6.2:

The 6.2 live product demo Q&A

The 6.2 Field Guide

More developer notes for 6.2

4. Other release-related topics

@johnbillion raised #57916, about 6.2 server-side performance regressions. @hellofromtonya noted the ticketticket Created for both bug reports and feature development on the bug tracker. is about assessing performance and will not generate any late commits to 6.2.

@francina pointed the group to a Slack discussion on debugging tools.

5. Tickets and components

@oglekler raised ticket #23348 as a way to encourage more people to start contributing. A lively discussion followed.

@audrasjb reminded about the Old Trac Ticket Triage sessions..

@howdy_mcgee raised three tickets for early 6.3: #24142, #37255, and #18408.

@costev highlighted that he, @ironprogrammer, and @afragen are working on an update to the WordPress 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. 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 that will add a section where users can report a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. right in the interface.

6. Open floor

No other items were raised.

Next week’s dev chat will be March 22, 2023 at 20:00 UTC in the Core Slack channel. See you there!

Props to @francina for leading dev chat, to @webcommsat for the agenda preparation,
@marybaum for the summary, and @oglekler and @webcommsat for review.

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

Dev Chat Agenda, Wednesday March 15, 2023

The next WordPress Developers Chat will on Wednesday, March 15 2023 at 20:00 UTC in the core channel of the Make WordPress Slack.

1. Welcome and housekeeping

Dev Chat summary, March 8, 2023 – thanks to @ironprogrammer

The meeting is scheduled facilitator will be @francina and @marybaum will draft the meeting summary.
If you would like to volunteer for the summary, add a comment to this ticketticket Created for both bug reports and feature development on the bug tracker. for @webcommsat.

2. Announcements

WordPress 6.2 Release Candidate 2 (March 14, 2023). The schedule release is now only two weeks away on March 28!

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/ 15.4 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). is scheduled.

What’s new in Gutenberg 15.3? (March 13, 2023) – posted by @richtabor. This version tightens up the site editing experience, adds a new “Time to Read” 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., and some Duotone enhancements.

3. Highlighted posts

A Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., March 6-13, 2023 – thanks to @audrasjb

  • 48 commits
  • 62 contributors
  • 47 tickets created
  • 8 tickets reopened
  • 68 tickets closed

And welcome to the five new contributors from this week!

4. Releases

Useful information on the next major WordPress release 6.2:

New links/ key information this week:
6.2 live product demo Q&A – posted by @marybaum
– The 6.2 Field Guide and more Developer Notes for 6.2

WordPress 6.2 has branched.

Also check the #6-2-release-leads channel for the latest updates.

For information:

Any additional updates from the Release Squad will be shared in the meeting.

5. Request for help with tickets/ components/ blockers/

If you have a ticket or request to help, please add a comment to the agenda post. Please indicate if you will be attending the meeting live and be able to highlight the issue further if needed.

If you are unable to attend dev chat live, you can add further details of the issue you would like highlighted either in comments, or message Core Team reps @webcommsat and @hellofromtonya with the additional information to raise in this week’s meeting for you.

6. Open floor

Items for this agenda item and the previous one are welcome from across time zones. Please add suggestions in comments on this post. Thanks.

Props for agenda preparation @webcommsat, and review @hellofromtonya.

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

Dev Chat Summary, March 8, 2023

The WordPress Developers Chat meeting took place on March 8, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Are you interested in helping draft Dev Chat summaries? You can volunteer to be added to the rotation, either during the meeting or by contacting abhanonstopnewsuk on the Make Slack.

Announcements

  • WordPress 6.2 Beta 5 is available to download and test. Thanks to everyone who was involved and tested for 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. 5.
  • WordPress 6.2 Release Candidate 1 has been postponed to March 9, 2023 at 17:00 UTC.

Highlighted Posts

Between February 27 and March 6, 2023, there was some great work again on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:

  • 45 commits
  • 79 contributors
  • 63 tickets created
  • 12 tickets reopened
  • 61 tickets closed
  • and 5 new contributors!
  • Please refer to Developer Notes for 6.2 for all the new 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. released this week. It has been a very busy time for the release documentation team, so a big thanks to everyone who has helped write, review, edit, administer 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/, or anything else related to these important communications.
  • The 6.2 Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. is expected to be published soon. Shout out to @bph, @milana_cap, @webcommsat, and @femkreations, the documentation release group, and to all those who made contributions.

Release Update

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

These links contain great reading material and helpful information for anyone wanting to get more involved in the release — make sure to check out the new (⭐️) items:

Also check the #6-2-release-leads channel for the latest updates.

If you would like to get involved with testing, check out the 6.2 call for testing post to get started.

Read about important accessibility improvements in this post from @annezazu, @joedolson, and @alexstine. Thank you to everyone on the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team and the many other contributors who support this work.

The WordPress 6.2 preview gives focus to highlights in the release for anyone who missed the live demo or would like a recap.

Release Squad Updates

@jeffpaul asked how things look for RC1, and @webcommsat and @audrasjb confirmed that while the regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in Trac #57630 was being evaluated, no additional delays were anticipated.

Requests for Help with Tickets/Blockers

@ndiego requested a call out for Gutenberg PR 48731, to address an issue from Beta 4. While developers are confident with the fix, more testing is requested — specifically to confirm that no “white screens” are seen in the editor or when using the browser Back button. Nick also asked emphasized the need for more general testing in the site editor.

@sergeybiryukov provided updates on the Build/Test Tools component:

@sergeybiryukov noted there were no updates for the 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., or Permalinks components.

Open Floor

@ironprogrammer brought up Trac #57891, requesting confirmation of the issue from other contributors. Brian confirmed to @ndiego that the issue applied to trunk, and not Beta 5. @petitphp reproduced the issue and provided a test report.

@sergeybiryukov and @webcommsat highlighted previous interest in running new contributor meetings in different time zones, including APAC-friendly. @sergeybiryukov shared information to help those interested: the guidelines and script link in the handbook for running such meetings. Further discussion on frequency and time(s) will be discussed amongst volunteers after the work on the current release.

@hellofromtonya asked for additional testing and investigation of Trac #57630, a regression or 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. related to child themes that use parent template parts.

Next Meeting

The next meeting will be on March 15, 2023 at 20:00 UTC.

As a reminder, in many countries Daylight Saving starts the second Sunday of March, i.e. March 12, so your local meeting start time may be different.

Props to @webcommsat for running the meeting, and to @ironprogrammer for the summary. Review by @webcommsat.

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

Dev Chat Agenda, March 8, 2023

The next WordPress Developers Chat will on Wednesday March 8, 2023 at 20:00 UTC in the core channel of the Make WordPress Slack.

Note: the 6.2 RC1 release party for will now be on March 8, approximately from 17:00 UTC. Please check for updates in the #6-2-release-leads on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

1. Welcome and notices

Dev Chat summary, March 1, 2023 – thanks to @ironprogrammer

2. Announcements

WordPress 6.2 Beta 5 – available to download and test

WordPress 6.2 Release Candidate 1 is postponed March 9, around 17:00 UTC.

3. Highlighted posts

A Week in Core – March 6, 2023 – thanks to @audrasjb

Developer Notes for 6.2 – check out all the new 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.. The Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. is expected to be published soon.

4. Release update

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.2
6.2 development cycle
6.2 bug scrub schedule
Roadmap to 6.2
Help Test WordPress 6.2

WordPress 6.2 Accessibility improvements
Dev Notes for 6.2 (link above in the ‘Highlighted Posts’ section of the agenda)

WordPress 6.2 Preview post

Check the #6-2-release-leads channel for latest updates.

5. Requests for help with tickets/ blockers

Priority will be given to items associated with the 6.2 release. Please add items for the meeting in comments below.

@ndiego request for callout for #48731. This PR addresses an issue identified after BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 4. It is thought the PR thoroughly fixes the issues, but more testing would be helpful.

General testing of the Site Editor requested as a primary focus.

6. Open floor

If you have an item you would like to be raised in this section of the meeting, you can add the topic in the comments below.

If you can not attend the meeting, as a global project, asynchronous updates are welcome. You can add these into the comments section.

Agenda prep @webcommsat, thanks to @costdev for review.

#agenda, #dev-chat

Dev Chat Summary, March 1, 2023

The WordPress Developers Chat meeting took place on March 1, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Are you interested in helping draft Dev Chat summaries? You can volunteer to be added to the rotation, either during the meeting or by contacting on the Make Slack abhanonstopnewsuk

Announcements

  • WordPress 6.2 Beta 4 went live earlier today and is now available to download and test. Thanks to everyone who contributed to it, including the release party facilitators and all the testers.
  • The current target for the final release is March 28, 2023, less than four weeks away.

Highlighted Posts

Changes in TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between February 20 and February 27, 2023 show some great statistics:

  • 45 commits
  • 103 contributors
  • 50 tickets created
  • 7 tickets reopened
  • 64 tickets closed
  • and 21 new contributors!
  • What’s New in Gutenberg 15.2 is out, with accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and template editing experience improvements, as well as additional 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. control support.
  • The WordPress Roadmap page has been updated with additional bullet points that will appear under APIs and Block theme dev tools.
  • The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-Performance team has published a Core Performance Team Roadmap.

Release Update

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

Below are some links for anyone new or wanting to get more involved in the release.

Check the #6-2-release-leads channel for the latest updates.

A live WordPress 6.2 demo will take place Thursday, 2 March 2023 at 17:00 UTC. Find more details on the 6.2 Live Product Demo post.

Open ticketticket Created for both bug reports and feature development on the bug tracker. update for 6.2

@costdev noted that 34 tickets remain in the 6.2 milestone (query used). The remaining tickets relate to  Build/Test Tools, docs-only, test-only, gutenberg-merge, or the About page, and will be scrubbed in coming days.

With the release of BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 4, @hellofromtonya reminded the team that if a regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. or issue comes up before 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). 1, then another beta may be necessary. She also noted that the 6.3 (alpha) milestone begins when trunk is branched at RC 1.

Invitation to contributors to help test releases during the development cycle, and to watch for the release party schedule in the #6-2-release-leads channel.

Requests for Help with Tickets/Blockers

Remaining tickets in 6.2 milestone

@azaozz confirmed that there were no core code changes in the remaining tickets.

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.

@webcommsat highlighted the work progressing on dev notes related to 6.2. @bph noted that in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ everything is almost done. @milana_cap noted that Documentation tasks have all been assigned.

@audrasjb provided a link to the WP 6.2 Documentation tracker, and @milana_cap confirmed that each item has been covered.

Open Floor

From the Agenda

@miguelsansegundo raised Trac ticket #56908: The result of locate_block_template function might be wrong prior to the meeting. Given the lack of recent activity, @hellofromtonya suggested it be tested in Gutenberg first, else it could be moved to the 6.3 milestone.

Roadmap Phase 4: Multi-lingual

@pbiron asked if there was any existing documentation or discussion about what the roadmap’s multi-lingual support feature might look like. @jeffpaul recalled Matt’s discussion of this feature at WCEU 2022 (starts around the 10:00 minute mark), and that more detail around Phase 3 (Collaboration) would need to come first.

@audrasjb asked if the feature, built in Gutenberg first, would support taxonomies (used in other multi-lingual plugins), and @azaozz asserted that it should be a “core project” and work with everything.

Following his original question, @pbiron asked when work on Phase 4 might start. @jeffpaul speculated that if Phase 3 runs through 2024, that Phase 4 might start in 2025. He further cautioned against starting too soon to avoid significant rework, depending on how Phase 3 comes together. @azaozz indicated that Phase 3 may be shorter than estimated, since much of the “infrastructure” in the editor has been prepared for the collaboration phase.

@oglekler noted that multi-lingual plugins are complicated, and that the functionality should be native to WordPress. @azaozz agreed, suggesting they might become less complicated once core supports the feature.

@clorith pointed out that there are older multi-lingual experiment PRs in Gutenberg, but that they are rudimentary and don’t necessarily hint at the final feature’s implementation. @pbiron wondered if there was a label for such items, but @clorith didn’t recall.

Call for Documentation and Maintainers

@bph provided a list of tickets (grouped by component) in the 6.2 milestone that don’t have maintainers, where documentation coverage may be incomplete. Here is the list:

She called on contributors to point out any needed Dev Notes, short dev mentions, or Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. one-liners to the Documentation team through the Outreach to component maintainers tracker on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.

@webcommsat also provided a handbook link to help those interested: What it means to be a component maintainer.

The next meeting will be on March 8, 2023 at 20:00 UTC.

Props to @webcommsat for running the meeting, and to @ironprogrammer for the summary. Review by @webcommsat.

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

Dev Chat Summary, February 22, 2023

The WordPress Developers Chat meeting took place on February 22, 2023 at 20:00 UTC in the core channel of Make WordPress Slack.

Key Links

Are you interested in helping draft Dev Chat summaries? You can volunteer to be added to the rotation, either during the meeting or by contacting @abhanonstopnewsuk on Slack.

Highlighted Posts

Between February 13 and February 20, 2023, there were on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:

  • 58 commits
  • 88 contributors
  • 74 tickets created
  • 10 tickets reopened
  • 69 tickets closed
  • 14 new contributors 🎉
  • Read about this Marketing experiment about post announcements, which intentionally posts only the first 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., 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)., and general release announcements to News, and intermittent beta/RC posts to Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

Help – Tickets/Components

Remaining Tickets in 6.2 Milestone

@johnbillion reminded the team that there were 95 open tickets to go (query used).

@costdev asked maintainers and contributors to assist triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. efforts by moving into Future Release any tickets they know will not make it into the 6.2 milestone.

Considering the high count, and being only a week away from Beta 4, @francina asked if release leads were comfortable with this many bugs. @hellofromtonya pointed out that only 57 of the tickets were defects (query used), and that any outstanding items would be punted by RC1.

@jeffpaul asked for confirmation if regressions introduced during 6.2 could remain open into RC, and @hellofromtonya confirmed, though could cause a delay (prescience?)

Open Floor

About Page

@francina asked for an About Page status update (#57477: About Page – 6.2 Release), and @jpantani noted that the draft document was still open for general feedback through the week. The document will be closed to changes on March 3, 2023 at 23:59 UTC.

Live Product Demo

@jpantani also mentioned the planned 6.2 Live Product Demo scheduled for March 2, 2023 at 17:00 UTC.

Props to: @ironprogrammer for the summary, and @webcommsat for review and agenda preparation,
and @francina for facilitating the meeting.

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

Dev Chat Agenda, March 1, 2023

The next WordPress Developers Chat will on Wednesday March 1, 2023 at 20:00 UTC in the core channel of the Make WordPress Slack.

Note: the release party for 6.2 Beta 4 will now be on March 1, approximately from 17:00 UTC. Please check for updates in the #6-2-release-leads on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

1. Welcome and notices

Dev Chat summary (link to follow)

2. Announcements

6.2 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 4 is due to be released prior to dev chat.

3. Highlighted posts

What’s New in Gutenberg 15.2 – Read how the template editing experience has been improved, accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) improvements and additional control support for blocks. Posted by @daisyo

A Week in Core, February 20 to 27, 2023 – thanks to @audrasjb

Core Performance Team Roadmap published

4. Release update

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.2
6.2 development cycle
6.2 bug scrub schedule
Roadmap to 6.2
Help Test WordPress 6.2

Check the #6-2-release-leads channel for latest updates.

A 6.2 live demo will take place be on Thursday, 2 March 2023 at 17:00 GMT. More details on the 6.2 live product demo – posted by @jpantani

The release squad will be able to share any 6.2 updates in dev chat or async on this post.

5. Requests for help with tickets/ blockers

Priority will be given to items associated with the 6.2 release. Please add items for the meeting in comments below.

6. Open floor

If you have an item you would like to be raised in this section of the meeting, you can add the topic in the comments below.

If you can not attend the meeting, as a global project, asynchronous updates are welcome. You can add these into the comments section.

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