Dev Chat Summary, May 18, 2022

Agenda followed for the weekly WordPress Developers Chat which included updates 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.0. The meeting was facilitated by @marybaum and @webcommsat

Start of the meeting in #Core channel on 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/..

2. Announcements

WordPress 6.0 RC3 is available for testing (released May 17, 2022). Since the RC1 release on May 3, 2022, there have been approximately 50 issues resolved in Gutenberg and Trac. Thanks to everyone involved and people who came along to test at the release party.

3. Blogblog (versus network, site) posts of note to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

A Week in Core – May 16, 2022  – thanks to @audrasjb.

What’s New in Gutenberg 13.2 (May 11, 2022.)

New free resources on Learn WordPress published in April 2022. Please help share.

4. Upcoming releases

Next major release: WordPress 6.0

Update

@annezazu : 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). 4 is planned for Friday May 20, 2022, with the Dry Run still slated for May 23, 2022 and the final release for May 24, 2022. Everything is on track, including a 6.0 video.

Update post-dev chat from the release co-ordinators:

You’re invited to the 6.0 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). 4, Dry Run, and Final Release Parties. Each party will aim to be held at 16:00 UTC in #core channel on Slack.

  • RC4 on May 20, 2022 (Friday)
  • Dry Run on May 23, 2022 (Monday)
  • Final Release on May 24, 2022 (Tuesday)

Final Release on May 24, 2022 (Tuesday) will happen 24 hours after the Dry Run completes. This is part of a true 24-hour code freeze. This means it will likely start more around 17:00 UTC assuming all goes well with the dry run. Please check #core and 6.0 release leads slack channel for any updates.

Recap of useful resources on 6.0

We share this expanding list every week in dev chat in the run up to the release, particularly to help those new to dev chat or those coming to find out about the release. If you have items for it, please  let us know on the agenda or during in the meeting.

Early bug schedule for 6.1

Release update relating to Learn WordPress and associated docs

@webcommsat: A cross-team update on where we are with training and Learn WordPress, and mapping this with end user on documentation and other opportunities for the release.

We have completed an extensive review (link to the full update in the #training channel on Slack) on where things are on the Learn WordPress side for 6.0, and will be continuing with the mapping and linking with end user documentation. There are a number of high priority items that need some further assistance for Learn WordPress.

If you are able to help with this, please add a comment in the #training Slack and with what you might be able to help with. We have put together some help for any developers / those familiar with the release who are able to help with this who are new to using the Learn WordPress side.

Thanks to Training, Documentation, Core and wider who have collaborated on this over the last weeks, and in advance as the work continues post release day too.

5. Open Floor

If you are a component maintainer or running 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 and have any updates not already mentioned under 6.0 updates, you can raise them in this section too.

a) Component maintainers – items of note

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

b) WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., June 2, 2022 – core tables.
@desrosj is bringing this together for the core tables at the event. Core will share an update on this hopefully next week. If you can volunteer to help on the day, contact @desrosj.

Props to: @estelaris for writing the summary, @webcommsat  and @marybaum for reviewing.

#6-0, #dev-chat, #summary, #week-in-core

Dev Chat Agenda, May 18, 2022

This weekly WordPress Developers Chat takes place in the #Core channel of the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. on Wednesday May 18, 2022 at 20:00 UTC. All welcome.

1. Welcome

Dev Chat summary from the meeting on May 11, 2022 – thanks to @webcommsat. Could you write a dev chat summary in the future?

2. Announcements

WordPress 6.0 Release Candidate 3 (released May 17, 2022)

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

A Week in Core (May 18, 2022)

What’s New in Gutenberg 13.2 (May 11, 2022)

4. Upcoming releases

Next major: WordPress 6.0

Updates from Release Co-ordinators and members of the squad.

Useful resources

5. Open floor

If you have any items for Open Floor, please add them in the comments below.

If you are a component maintainer and wish to raise a ticketticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.

Thanks to @marybaum and @webcommsat for working on the agenda and meeting planning.

Could you help with the summary from this week’s meeting? Comment below or message CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team reps @marybaum and @audrasjb in the Core Slack channel.

#6-0, #agenda, #dev-chat

Dev Chat Summary, May 11, 2022

Agenda followed for Dev Chat for the weekly WordPress Developers Chat which included updates 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.0. The meeting was facilitated by @marybaum and @webcommsat.

Start of the meeting in #Core Slack

2. Announcements

WordPress 6.0 RC2 is available for testing (released May 10, 2022). Since the RC1 release on May 3, 2022, there have been approximately 40 issues resolved in Gutenberg and Trac. Thanks to everyone involved and people who came along to test at the release party.

Gutenberg 13.2 has landed!

Early bug schedule for 6.1 – thanks @costdev. Note change of day – these will now happen on Thursdays 18:00 UTC and not Mondays.

3. Blogblog (versus network, site) posts of note to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

A Week in Core – May 9, 2022 (published May 11, 2022) – thanks to @audrasjb

Performance Team Meeting Summary, May 10, 2022 – includes some updates on WebP, some POCs needed for the Site Health and Measurement sub groups. At the end of the post, there is a list of areas where help is needed.

Open floor item in the Editor Chat agenda for May 11, 2022 on a discussion around adding a new label to the 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/ repo around issues that impact adoption. The aim would be to have an easier way to see, at a glance, what big issues are impacting the adoption of Gutenberg.

Full Site Editing Program Testing Call 14 – Rallying Recipe Reviewers. Deadline for feedback: 18 May 2022

4. Upcoming releases

Next major release: WordPress 6.0

Updates

Update via @annezazu
No big updates to share on 6.0 — the release squad is really crushing it and things are moving forward as expected. Some quick updates to be safe though:

  • The 6.0 video continues to progress nicely and is on track to ship the day before the release still.
  • Props are in progress thanks to a wonderful effort by @desrosj.
  • A 6.0.1 board has been started so we carry momentum into the point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.https://github.com/orgs/WordPress/projects/31

Thank you to everyone who is making this release possible. Please keep testing and, if you can’t, encourage others to do so. It all helps.

Update via @costdev on bugs scrub and testing side: Monitoring new tickets regularly and things are going well.

6.0 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). 3

6.0 RC3 Release Party on May 17, 2022, 16:00 UTC
Meet in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. As always with releases, there’s a chance this time may change the day of depending on how things are progressing. The time will be communicated across channels (#core-editor#6-0-release-leads, and in #core). All welcome.

The next major 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 before RC3 will be on Thursday May 12, 2022, 21:00 UTC. The full bug scrub schedule for 6.0

Recap of useful resources on 6.0

5. Open Floor

If you are a component maintainer or running a bug scrub and have any updates not already mentioned under 6.0 updates, you can raise them in this section too.

a) Component maintainers – items of note

Update from @sergeybiryukov
Build/Test Tools: The local development environment can now run on Apple M1 machines without requiring local configuration changes. Ticketticket Created for both bug reports and feature development on the bug tracker. #52356 for more details.

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.: An edge case was fixed in the script loader where the dependency order was incorrect for scripts with translations in some cases. Ticket #55628 for more details.

General, Date/Time, Permalinks: No major news this week. 

b) WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/., June 2, 2022 – core tables.
Update from @desrosj: If anyone will be at WCEU Contributor Day and has a specific topic they would like to focus on for the day at the Core tables, please share the topic and a brief one or two sentence description by Friday. I have a few generic topics, but if anyone is looking to lead specific discussions, please send them over!

@marybaum: later in the summer, there will be similar planning for WordCamp US.

c) Rubber duck emoji request! It all happens at dev chat!

d) @clorith brought up Ticket Gutenberg 40316 and the issue of experimental APIs versus backward compatibility. A lively discussion followed, with several suggestions on how to get input from the community at large. (Note from Core Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @marybaum: If you’re new, dev chat is not a forum for making final decisions. But it is a great place to surface topics that warrant wider discussion, and to explore where those conversations should start).

Props to: @webcommsat for writing the summary, @marybaum and annezazu for reviewing.

#6-0, #dev-chat, #summary, #week-in-core

Dev Chat Agenda, May 11, 2022

With RC2 and waiting for some posts, this agenda is being published on May 11. Updated in item 4 with the RC3 date and next major 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.

The weekly WordPress developers chat takes place in the #core SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel of Making WordPress at 20:00 UTC

Summary from Dev Chat on May 5, 2022 – thanks to @webcommsat for the notes. Who can do notes for the meeting on May 11?

2. Announcements

WordPress 6.0 RC2 is available for testing (released May 10, 2022).

Gutenberg 13.2 has landed!

3. Blogblog (versus network, site) posts of note to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

A Week in Core – May 9, 2022 (published May 11, 2022)

Performance Team Meeting Summary, May 10, 2022 – includes some updates on WebP, some POCs needed for the Site Health and Measurement sub groups. At the end of the post, there is a list of areas where help is needed.

Open floor item in the Editor Chat agenda for May 11, 2022 on a discussion around adding a new label to the 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/ repo around issues that impact adoption. The aim would be to have an easier way to see, at a glance, what big issues are impacting the adoption of Gutenberg.

Full Site Editing Program Testing Call 14 – Rallying Recipe Reviewers. Deadline for feedback: 18 May 2022

Early 6.1 scrub schedule: Mondays at 18:00 from @costdev

4. Upcoming releases

Next major: WordPress 6.0

Updates from Release Co-coordinators and members of the squad.

6.0 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). 3 Release Party on May 17, 2022 – meet in the #core Slack channel. As always with releases, there’s a chance this time may change the day of depending on how things are progressing. The time will be communicated across channels (#core-editor#6-0-release-leads, and in #core). All welcome.

The next major bug scrub before RC3 will be on Thursday May 12, 2022, 21:00 PM UTC. The full bug scrub schedule for 6.0

5. Open Floor

If you are a component maintainer or running a bug scrub and have any updates not already mentioned under 6.0 updates, you can raise them in this section too.

#agenda, #dev-chat

Summary Dev Chat, May 5, 2022

Link to the start of the meeting on the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds 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/. channel.

Agenda followed for the meeting.

Dev Chat summary from April 27, 2022 meeting – thanks to @webcommsat for doing these.

2. Announcements

WordPress 6.0 Release Candidate 1 (released on May 3, 2022). This was the hard string freeze for the 6.0 and 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". for the release. You can help by taking part in testing and make the release the best it can be. Thank you to everyone who came to the release parties this week.

WordPress 6.0 Beta 4 was released on May 2, 2022. It was not part of the originally published development cycle. It was aimed at providing an opportunity for testing some specific issues that were resolved since 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. 3.

Early focused meetings will take place on Mondays at a revised time of 18:00 UTC. Thanks to @costdev for working on this. These meetings will mean early tickets can get the attention they need, without disrupting devchat/bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrubs. Thanks to @costdev who will be running these meetings. The meetings will focus on:

  • targeting 3-4 tickets per meeting, discussing the proposal/bug
  • updating the ticketticket Created for both bug reports and feature development on the bug tracker. with opinions/findings
  • for some tickets that require investigation, some of the investigation might be possible during the meeting, otherwise we could schedule a date/time for contributors to get together to do any necessary deep-dives (either in chat, or via mob programming)

What’s New in Gutenberg 13.1 (April 27, 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/ 13.1 brings border support to the Columns 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., a number of improvements to the Comments blocks, along with a range of 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) enhancements.

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

A Week in Core – May 2, 2022 – thanks to @audrasjb

Full Site Editing Program Testing Call 14 – Rallying Recipe Reviewers. Deadline for feedback: 18 May 2022

 4. Upcoming releases

Next major: WordPress 6.0

Updates from Release Co-coordinators and members of the squad.

@annezazu – Quick run down:

  • A new project board is being considered for 6.0.x releases for Core Editor issues as there are a few that are slated for a point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.. Stay tuned there but know bugs are being handled appropriately and are very much appreciated.
  • Check out this great post from @peterwilsoncc on what this current 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). phase means: https://make.wordpress.org/core/2022/05/04/wordpress-6-0-release-candidate-phase/
  • 6.0 RC 2 is next week on May 10, 2022 and I hope to see you all at the release party! Expect it to be around the same time at 16:00UTC.
  • About page:
    • @marybaum: Well I believe the About Page strings got committed ahead of the hard string freeze, and the rest of that process is going as it has in recent releases.
    • @annezazu: The 6.0 video in progress will also be ready in time for a commit just before the final release. It will be linked in the About Page.
    • @webcommsat: The ticket has some more details.
    • @ryelle: The About page should be pretty much done – any feedback about things looking broken is welcome, but the only changes planned are to add in the correct links.

Some other useful resources on 6.0

A recap of some of the useful resources on 6.0 including 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.!

5. Open floor

Component maintainers

@sergeybiryukov: Build/Test Tools component: Two issues were fixed in the 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. suite:

  • Pass GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ Actions environment variables to the Docker container, so that tests that should only run on 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. don’t unintentionally run on other branches. See ticket #55668 for more details.
  • Update the test for supported versions in the SECURITY.md file so that major versions like 6.0 are handled correctly. See ticket #55667 for more details.

General: The Microsoft IIS configuration file was updated to account for WordPress coding standardsWordPress Coding Standards A collection of PHP_CodeSniffer rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official standards for WordPress Core.. Testing is welcome from anyone running their own local IIS server on Windows. See ticket #53377 for more details.Date/Time, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks: No major news this week.

Other open floor items

  • From the release documentation team, if any component maintainers or committers are still working on dev notes for 6.0 or have not had chance to reply to @bph, please can you let her know.
  • WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe (WCEU) Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. Core Tables, June 2, 2022 – @desrosj would you like to share anything on this today? We can share this in a future week. 

 You’re invited to the 6.0 RC 2 Release Party at 16:00 UTC on May 10, 2022 (click to add to your calendar). Meet in #core and be ready to wave hello, emoji reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/., and help test. As always with releases, there’s a chance this time may change the day of depending on how things are progressing. If the time is changed, it will be communicated across channels (#core-editor#6-0-release-leads, and in #core). Hope to see you there!

Props to @webcommsat for the summary, @marybaum and @annezazu for reviewing

#6-0, #dev-chat, #summary

Dev Chat Agenda, May 4, 2022

This weekly WordPress Developers Chat takes place in the #Core channel of the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. on Wednesday May 4, 2022 at 20:00 UTC. All welcome.

1. Welcome

Dev Chat summary from the meeting on April 27, 2022 – @webcommsat

2. Announcements

WordPress 6.0 Release Candidate 1 (released on May 3, 2022). This was the hard string freeze for the 6.0 and 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". for the release.

WordPress 6.0 Beta 4 (released on May 2, 2022).

Early focused meetings will take place on Mondays at a revised time of 18:00 UTC.

What’s New in Gutenberg 13.1 (April 27, 2022).

3. Blogblog (versus network, site) posts of note to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

Key links for 6.0 and updates from the squad will be in the agenda item 4, after these blog posts.

A Week in Core – May 2, 2022

Full Site Editing (FSE) Outreach Program Testing Call 14: Rallying Recipe Reviewers (April 28, 2022). Leave feedback by May 18, 2022

Any others?

4. Upcoming releases

Next major: WordPress 6.0

Updates from Release Co-ordinators and members of the squad.

Useful resources/ calls for testing

5. Open floor

If you have any items for Open Floor, please add them in the comments below.

If you are a component maintainer and wish to raise a ticketticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.

Could you help with writing the summary from dev chat for a future meeting? Comment below or message core team reps @marybaum and @audrasjb in the Core Slack channel.

Props to: @webcommsat and @marybaum for working on items for the agenda.

#6-0, #agenda, #dev-chat

Dev Chat Summary, April 27, 2022

Notes from the weekly WordPress developers chat held in the #core 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/. of Making WordPress.

Start of the meeting in Slack

1. Welcome

Dev Chat summary from April 20, 2022 meeting

The agenda followed for April 27, 2022

2. Announcements

WordPress 6.0 Beta 3 released on April 26, 2022. This represented the soft string freeze for this release.

Status of Webfonts API for inclusion in WordPress 6.0 (April 22, 2022)

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

A Week in Core – April 25, 2022 – thanks to @audrasjb

An update on Preferred Languages Project – thanks to @swissspidy for the post (April 27, 2022) on 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 plans for users to be able to select multiple preferred languages in settings. The post includes a call for contributions to development and testing. For background, more than half of all WordPress sites in the world use a language other than US English.

Exploration to enable better dev and visitor experiences with blocks (April 27, 2022)

4. Upcoming releases

Next major: WordPress 6.0

Updates from Release Co-coordinators and members of the squad.

a) @annezazu: from the co-release coordinator side, 6.0 is moving along with Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 planned for next week:

  • some questions around the post comments query blocks work to resolve this week
  • lots of excellent work around preparing 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 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. and 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. by the docs folks
  • the modified and private approach for webfonts API has shipped in beta 3: I will leave a comment on that post for good measure as an update.

b) @costdev: For those who haven’t seen it yet, there is a new TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. keyword, changes-requested. Slack reference

c) Shared by @dansoschin as an update on the about page for 6.0, earlier in the marketing meeting:

  • there’s work on a short video overview to accompany the release, to drop on release day
  • the About Page, which is part of the release package, will be more-or-less finalized in copy form and design form at the end of this week. The purpose of this file, as currently established, is to provide a brief update of what’s in the release and provide links to resources where you can find more information.

d) Update via @abhanonstopnewsuk: she is collecting information to share with Documentation, Training, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on what extra information/ steps would be useful for non-devs to take part in testing the release. 

Some other useful resources on 6.0

5. Open floor

a) @costdev: As we approach RC1 and branching off for 6.1, I wanted to propose an early focused meeting on Mondays.

This would be similar to 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, but instead of trying to get through as many tickets as possible, it would be about targeting 3-4 tickets per meeting, discussing the proposal/bug, and updating the ticketticket Created for both bug reports and feature development on the bug tracker. with opinions/findings. For some tickets that require investigation, some of the investigation might be possible during the meeting, otherwise we could schedule a date/time for contributors to get together to do any necessary deep-dives (either in chat, or via mob programming). This would allow for early tickets to get the attention they need, without disrupting dev chat/bug scrubs. I’m happy to run these meetings.

What does everyone think?

  • comments from the meeting were largely in agreement with the idea of this meeting
  • this would clash with the current About Page/ Help Page and Quick Edit/ Bulk Edit regular scrub, which maintainers would look at the options to move to another time slot.
  • @costdev: is happy to start them as soon as we 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". for 6.1 then and I’ll see about getting them set up as recurring at that stage. Update: alternative date for the early-focused meeting, Mondays 18:00 UTC

b) @webcommsat: From the release documentation team, we are reaching out to component maintainers about dev notes for 6.0. Please look out for a message from @bph.
@bph: thanked maintainers who had already replied.

c) @marybaum: Dev Chat summary volunteers needed to help with compiling items for the agenda and drafting the summary. @webcommsat has kindly been persuaded to do the dev chat summary again this week. Please do think about volunteering for a future week.

Props to: @webcommsat for dev chat summary and @marybaum and @costdev for review.

#6-0, #dev-chat, #summary

Dev Chat Agenda, April 27, 2022

This has been published later than normal due to the availability of contributors. Thank you for understanding.

This weekly meeting takes place in the #Core channel of the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. on Wednesday April 27, 2022 at 20:00 UTC. All welcome.

1. Welcome

Dev Chat summary from April 20, 2022 meeting

2. Announcements

WordPress 6.0 Beta 3 released on April 26, 2022. This represented the soft string freeze for this release.

Status of Webfonts API for inclusion in WordPress 6.0 (April 22, 2022)

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

A Week in Core – April 25, 2022 – thanks to @audrasjb

An update on Preferred Languages Project – thanks to @swissspidy for the post (April 27, 2022) on 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 plans for users to be able to select multiple preferred languages in settings. The post includes a call for contributions to development and testing. For background, more than half of all WordPress sites in the world use a language other than US English.

4. Upcoming releases

Next major: WordPress 6.0

Updates from Release Co-coordinators and members of the squad.

Useful resources/ calls for testing

5. Open floor

If you have any items for Open Floor, please add them in the comments below.

If you are a component maintainer and wish to raise a ticketticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.

Could you help with the summary from this week’s meeting? Comment below or message @marybaum and @audrasjb in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Slack channel.

Props to: @webcommsat and @marybaum for working on the agenda and @desrosj for review.

#6-0, #agenda, #dev-chat

Dev Chat Summary, April 20, 2022

Updates: new web link added to section 4 relating to the status of webfonts APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways..

Notes from the weekly WordPress Developer Chat held in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel 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/..
Start of the meeting in Slack

1. Welcome

Interested in Core development? This is the meeting to join, and you are more than welcome. Add your posts and items for open floor to the published agenda, which goes out a day ahead of the meeting.

Agenda for the meeting on April 20, 2022

Dev Chat summary, from the meeting on April 13, 2022

2. Announcements

a) WordPress Beta 2 landed on April 19. 2022. Please download and test! But do remember that this version of the WordPress software is under development. So you won’t want to test it on a production siteProduction Site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing.. If you came to the release party, thanks very much for contributing your time and energy.

b) The speaker deadline for WordCamp US has been extended to April 25, 2022.

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

A Week in Core, from @audrasjb (April 18, 2022)

What’s New in Gutenberg 13.0 (April 14, 2022)

How you can help test 6.0

The deadline for feedback for the latest FSE program testing call is April 21, 2022. FSE Program Testing call #13: Authoring an Author template

4. Upcoming releases

4a. Next major: 6.0

6.0 Development Cycle

Update on behalf of the release squad by @annezazu:
A big thank you to everyone who continues to help make this release happen. It’s always felt really humbling to be a part of but, for some reason today, that feeling is very magnified. 
Updates:

  • all are welcome to join the 6.0 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. 3 Release Party at April 26 2022 at 16:00 UTC in the core channel on the Make WordPress Slack
  • The best way to help is to test — a rundown of how to do so.
  • Over the last week, tons of discussions and efforts have been thrown behind the Webfonts API effort. Everyone involved deserves big props. For clarity, this API is NOT in Beta 1 or 2. Expect a Make Core post in the coming days with a status update: the people with their hands in the code are looking at several pathways forward, including not having it in the release at all.
    Update: post on Status of webfonts API for WordPress 6.0 inclusion (published April 22, 2022)
  • A post is coming shortly around the various 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 coming to 6.0. Stay tuned and get excited! (This was published after dev chat – Accessibility improvements in 6.0. Thanks to @joedolson, @alexstine and @annezazu for collaborating on this post.)
  • Other features related to the release are evolving as the beta process proceeds, including removing block edit locking from the reusable block (just the ability to lock the option to edit) and various decisions for the comments blocks work.

Update from @costdev relating to core triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.

Regarding 6.0 Core Triage, Beta 3 is on the horizon—that is also soft string freeze. Get your patches uploaded or refreshed and pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” component maintainers, committers, the relevant teams (Copy/Marketing, Docs, Accessibility, CSSCSS Cascading Style Sheets., Test Team, etc) or feel free to ping him @costdev) here or on 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 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/ (same username) if you need some extra eyes on your ticketticket Created for both bug reports and feature development on the bug tracker./patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. Let’s land them in 6.0.

@webcommsat: You can still join the Bug Scrubs for 6.0 – dates are on the bug schedule.

Suggestion for a handbook page for contributors new to testing during a release party. @marybaum checked, and there is not a page already. Suggested one to add to a to-do list.

5. Open Floor

a) Blog – core team activity

@audrasjb: shared a blog post from a contributor @mte90, who put together some meaningful insights about core team activity. He also offered his analysis of the “ticket queue problem” and shared his thoughts on it. Suggestions for actionable items included:

  • Create a Mentor/Reviewer role, that has duty, but is able/skilled to review the patch or help the patch author to finish it, ready to be reviewed by Component Maintainers
  • Improve the Bug triage team with other people to have less tickets to be handled by Component maintainers (when a component is assigned)
  • During WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. at the core table get people working on triage, as developers/veterans are required

Discussion in dev chat about core tables at contributor events at WordCamps continuing to focus on triage, encouraging more camps to do these kind of events.

But Camps will also need experienced devs familiar with triage and able to help take tickets forward, so the goal is not just increasing the number of people involved in isolation.

@webcommsat: Contributor days or events can be standalone events too – there have been some really good examples run by a local or grouped WordPress communities where they have focused on tickets on a particular theme. It does not necessarily mean the tickets they focus on get looked at again on trac immediately or even soon. Firms can also run events in-house or hold regular sessions as part of Five for the Future too. There are lots of chats already happening in the wider community about these kinds of contributor events, and coming to teams with requests of what to focus on. WordCamp Europe Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. in June could be a good triage opportunity.

@costdev: Might be worth either having more regular scrubs or some mob triaging streams/similar to help get through a bunch of the older tickets, especially those that needs-testing and such. These scrubs can also work well to show new contributors how things work.

@audrasjb: We can definitely try some new things, like a “Triage Week event” once a year (better name welcome. In French, we have a word for that kind of “event”:“nettoyage de printemps” (“spring cleaning” or “spring-clean”.

b) Trac tickets

@jeffpaul: Highlighted Trac Ticket #55377 on the crop area display in CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. when cropping a large site logo. This is a recently opened defect looking for feedback on the potential approach before time is spent on a patch. @costdev to review; needs some checks against existing tickets/ a reproduction report and some other changes before looking at the approach.

c) Next meeting

Wednesday April 27, 2022 at 20:00 UTC

Can you help write the summary from dev chat next week? We are short on volunteers at the moment, and you can get help doing it. Contact core team reps @marybaum and @audrasjb.

Props to @marybaum and @webcommsat for facilitating dev chat, to @webcommsat for writing the summary, and to @marybaum, @annezazu and others for reviewing it.

#6-0, #dev-chat, #summary

Dev Chat Agenda, May 11, 2022

This weekly WordPress Developers Chat takes place in the #Core channel of the Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. on Wednesday May 11, 2022 at 20:00 UTC. All welcome.

1. Welcome

Dev Chat summary, from the meeting on May 4, 2022

2. Announcements

WordPress 6.0 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). 2 is available (released May 10, 2022)

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

A Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. (May 9, 2022)

4. Upcoming releases

Next major: WordPress 6.0

Updates from Release coordinators and members of the squad.

Useful resources/ calls for testing

5. Open floor

If you have an item for Open Floor, please add it in the comments below.

If you are a component maintainer and wish to raise a ticketticket Created for both bug reports and feature development on the bug tracker. in dev chat or give an update, you can also add information in the comments section.

Thanks to @webcommsat and @marybaum for working on the agenda.

Could you help with the summary from this week’s meeting? Comment below or message @marybaum and @audrasjb in the Core Slack channel.

#6-0, #agenda, #dev-chat