Title: Dev Chat Summary, August 10, 2022
Author: Abha Thakor
Published: August 10, 2022
Last modified: August 11, 2022

---

 [  ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/)
11:14 pm _on_ August 10, 2022     
Tags: [6.1 ( 94 )](https://make.wordpress.org/core/tag/6-1/),
[dev chat ( 933 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 981 )](https://make.wordpress.org/core/tag/summary/)

# Dev Chat Summary, August 10, 2022

[Start of the WordPress Developers Chat](https://wordpress.slack.com/archives/C02RQBWTW/p1660161709530859)
in the coreCore Core is the set of software required to run WordPress. The Core 
Development Team builds WordPress. channel on the Make WordPress SlackSlack Slack
is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

The [agenda](http://:%20https://make.wordpress.org/core/2022/08/10/agenda-dev-chat-august-10-2022/)
followed in the meeting, led by [@marybaum](https://profiles.wordpress.org/marybaum/)
and [@webcommsat](https://profiles.wordpress.org/webcommsat/).

## 1. Welcome

A special welcome to those new to Dev Chat and all those who attended the New Contributor
Meeting in core today.

## 2. Announcements

No official announcements or news items this week.

## 3. Blogblog (versus network, site) posts to note

 * [What’s new in Gutenberg 13.8](https://make.wordpress.org/core/2022/08/04/whats-new-in-gutenberg-13-8-3-august/)(
   August 3, 2022)
 * [A Week in Core](https://make.wordpress.org/core/2022/08/09/a-week-in-core-august-8-2022/)(
   August 8, 2022)
 * [Giving FSE a more user-friendly name](https://make.wordpress.org/core/2022/07/27/giving-fse-a-more-user-friendly-name/)–
   this discussion post, from July 27, is still open
 * [Off-forum support requests](https://make.wordpress.org/support/2022/04/off-forum-support-requests/)–
   highlighted in the team reps group this week, this discussion is looking for 
   awareness, discussion, and feedback
 * [Proposal](https://make.wordpress.org/core/2022/08/10/proposal-stop-merging-experimental-apis-from-gutenberg-to-wordpress-core/)
   to stop merging experimental APIs 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/](https://wordpress.org/gutenberg/)
   to WordPress core (August 10, 2022)
 * [@annezazu](https://profiles.wordpress.org/annezazu/) shared this latest call
   for testing facilitators. It is an open call for anyone interested in being part
   of the actual creation of / facilitation of calls for testing to help scale WordPress
   efforts in this area

> [Testing. Testing: Calls for Testing Facilitators](https://make.wordpress.org/test/2022/08/10/testing-testing-calls-for-testing-facilitators/)

 * From Learn WordPress, [a list of materials published in June and July 2022](https://make.wordpress.org/updates/2022/07/15/whats-new-on-learnwp-in-july-2022/).
   
   The Learn team is also looking for some new contributors. Would you like to help
   produce material about what’s new in each release? Please contact [@Courtney](https://wordpress.slack.com/team/U02RQ0375)
   [@Pooja Derashri](https://wordpress.slack.com/team/U84BKHNDU) [@Hauwa Abashiya](https://wordpress.slack.com/team/UD5V51YSD)
   or [@abhanonstopnewsuk](https://wordpress.slack.com/team/U6R2E3Y9Y) (Slack IDs)
   in [#training](https://wordpress.slack.com/archives/C02RW657Q). You’ll also have
   a chance to help with some other, related, collaborative opportunities. 

## 4. Upcoming releases

### **a) 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.1**

[@annezazu](https://profiles.wordpress.org/annezazu/) highlighted:

 * L[atest planning roundup for 6.1](https://make.wordpress.org/core/2022/07/26/wordpress-6-1-planning-roundup-v2/).
   This is a follow-up post for the first WordPress 6.1 Planning Roundup published
   on June 23, 2022
 * [WordPress 6.1 Development Cycle](https://make.wordpress.org/core/6-1/) page 
   has an updated timeline
 * Follow the process as it happens in [#6-1-release-leads](https://wordpress.slack.com/archives/C03LZ88NX6G)
   channel on the Make WordPress Slack
 * More recently, there have been some [great initial discussions around documentation](https://make.wordpress.org/docs/2022/08/10/kick-off-wordpress-6-1-release-docs/).
 * A hallway hangout on August 11, 2022, will [go deep into the Core Editor tech process that anyone can join to learn more.](https://make.wordpress.org/core/2022/08/09/hallway-hangout-editor-tech-lead-role-101/)

[@webcommsat](https://profiles.wordpress.org/webcommsat/): if you are new to Dev
Chat or just starting to follow along the 6.1 release, some useful links:

 * [Development cycle for 6.1](https://make.wordpress.org/core/6-1/)
 * [Bug scrub schedule for 6.1](https://make.wordpress.org/core/2022/08/09/bug-scrub-schedule-for-6-1/)
   now out – anyone can help out or observe and learn more about how to get involved
   with moving tickets forward.
    - As [@marybaum](https://profiles.wordpress.org/marybaum/) and others have highlighted,
      anyone can volunteer to run a bugbug A bug is an error or unexpected result.
      Performance improvements, code optimization, and are considered enhancements,
      not defects. After feature freeze, only bugs are dealt with, with regressions(
      adverse changes from the previous version) being the highest priority. scrub.
      There’s helpful information in the Core Handbook to get you started. If you
      spot something that needs explaining further in the Handbook, do let the release
      squad or the Core reps know too.
 *  - [Bug gardening section in the handbook](https://make.wordpress.org/core/handbook/testing/bug-gardening/)
    - [Leading a bug scrub](https://make.wordpress.org/core/handbook/tutorials/leading-bug-scrubs/)

### b) The next minor is 6.0.2

[@annezazu](https://profiles.wordpress.org/annezazu/):

 * Right now, the people who have volunteered to lead the minors are leaning towards
   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)](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?output_format=md#alpha-beta).(
   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)](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?output_format=md#alpha-beta).)
   on August 23 and final on August 30, 2022, pending confirmation with the security
   team.
 * Shared last week, [link](https://wordpress.slack.com/archives/C035NHLFUSY/p1659115692375019)
   to the public discussion on Slack on 6.0.2. As soon as there are set dates, there
   will be updates in these Slack channels: [#core](https://make.wordpress.org/core/tag/core/),
   [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7), and [#6-0-release-leads](https://wordpress.slack.com/archives/C035NHLFUSY)
   confirming.

[@marybaum](https://profiles.wordpress.org/marybaum/): If you’re new to the process
and want to follow along, discussions about minors live in the release-leads channel
of the major they are part of.

## **5. Ticketticket Created for both bug reports and feature development on the bug tracker. help / Component Maintainers requests**

### **a. Updates or requests from maintainers**

[@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/):

 * **Build/Test Tools:** An effort on adding missing `@covers` tags for WordPress
   unit testunit test Code written to test a small piece of code or functionality
   within a larger application. Everything from themes to WordPress core have a 
   series of unit tests. Also see [regression](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?output_format=md#regression).
   suite has continued. [Ticket #39265](https://core.trac.wordpress.org/ticket/39265)
   for more details.
 * **Date/Time, General, I18Ni18n Internationalization, or the act of writing and
   preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?output_format=md#l10n).
   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](https://profiles.wordpress.org/webcommsat/):

 * **Help/ About component**: [@marybaum](https://profiles.wordpress.org/marybaum/)
   and I have been looking through tickets ready for a scrub next week. We started
   a ticket for the About Page so that it could be included in the milestone. I 
   have set up the folders for images and the About Page materials ready.
 * **Quick/ Bulk Edit** **component:** [@nalininonstopnewsuk](https://profiles.wordpress.org/nalininonstopnewsuk/)
   and I have identified a number of tickets to be included in a scrub and prioritizing
   which ones to move forward based on patches etc.
 * For both components, we will be following up in the next few weeks with some 
   of those who have been helping progress the the tickets.

Other component maintainers were encouraged to share their progress at Dev Chat 
or on the agendas, and as a good way of highlighting the component and if any help
was needed.

If you are new to Dev Chat, you can find out more on the [core blog](https://make.wordpress.org/core/components/)
about components and who the maintainers are, as well as how you can volunteer.

[@costdev](https://profiles.wordpress.org/costdev/)

 * joined as a maintainer for the **Upgrade/Install** component last night, and 
   is looking forward to helping move tickets forward and improve the component.
   Congratulations!

### b. Tickets to highlight for help

 * TracTrac An open source project by Edgewall Software that serves as a bug tracker
   and project management tool for WordPress. Ticket [#56283](https://core.trac.wordpress.org/ticket/56283)–
   [@audrasjb](https://profiles.wordpress.org/audrasjb/) has asked for attention
   on this ticket, pointing out that it needs a consensus.

 * Gutenberg Ticket [#35852](https://core.trac.wordpress.org/ticket/35852) – [@mamaduka](https://profiles.wordpress.org/mamaduka/),
   and the core editor bug scrub from earlier today, would like further testing 
   on this please.

## **6. Open Floor**

No other items were raised.

The next Dev Chat will be on: Wednesday 17 August 2022, at [ 20:00 UTC ](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220810T2000).

_Props to [@webcommsat](https://profiles.wordpress.org/webcommsat/) for the summary,
and to [@marybaum](https://profiles.wordpress.org/marybaum/) and [@costdev](https://profiles.wordpress.org/costdev/)
for reviewing._ 
_Could you write next week’s summary?_

[#6-1](https://make.wordpress.org/core/tag/6-1/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/),
[#summary](https://make.wordpress.org/core/tag/summary/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2022/08/10/dev-chat-summary-august-10-2022/?share=linkedin)

# Post navigation

[← Proposal: Stop merging experimental APIs from Gutenberg to WordPress Core](https://make.wordpress.org/core/2022/08/10/proposal-stop-merging-experimental-apis-from-gutenberg-to-wordpress-core/)

[Editor chat summary: 10 August, 2022 →](https://make.wordpress.org/core/2022/08/15/editor-chat-summary-10-august-2022/)