Tag Archives: summary

Abha Thakor 8:07 am on September 1, 2022
Tags: , , , summary   

Dev Chat Summary, August 31, 2022

1. Welcome and introduction

The start of the weekly WordPress developers chat meeting in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team channel can be found at this Slack thread.

Meeting agenda preparation and facilitation: @webcommsat and @marybaum. Thanks to everyone who sent in materials or shared tickets.

Meeting summary: @webcommsat. Review: @marybaum, @costdev.

References: Contributor Handbook. Purpose and role of weekly Dev Chat, held on Wednesdays at 20:00 UTC.

2. Announcements

@bph: 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/ 14.0 is in the repo, and a Make Core post is in progress. The performance tests need another look. Props to @desrosj for getting it over the finish line and release leadRelease Lead The community member ultimately responsible for the Release. @onemaggie. Post dev chat – What’s new in Gutenberg 14.01.

3. Blogs posts

Core editor improvement: refining the template creation experience (August 25, 2022)

Post dev chat: A Week in Core (August 31, 2022) thanks to @audrasjb.

4. Upcoming releases

a) The next major is 6.1.

No specific updates from the Release Squad.
Some useful links:
6.1 development cycle
Bug scrub cycle

Other 6.1 related items:
– @pbearne: is keen to get these two filters #56045 and #37930 committed. Action: @davidbaumwald is looking into this. Anyone else able to assist too?

– @jeffpaul: Worth noting that 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. 1 is in less than 3 weeks and historically we’ve tried to ensure features land week prior so ideally any new features/enhancements get in by Friday, September 9, 2022.

– @webcommsat: On an adminadmin (and super admin) task, the roadmap post for 6.1 does not seem to be linked from the development cycle page. Can this be added? The post also refers to a second post to follow, is this expected before Beta 1? Action: Follow-up.

– @webcommsat: A question for the release leads, do we have any update on the pre-release walkthrough date? It was provisionally set for September 13, 2022.
Update Sept 1 in release leads channel: pre-release walkthrough confirmed for September 13, at 16:00 UTC. @jpantani is organizing the event via Zoom. Announcement post to follow.
Action: Add walkthrough on next week’s dev chat agenda for an update.

b) Minor releases
Key links for anyone wanting to know more about the latest minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality., 6.0.2.
WordPress 6.0.2 security and maintenance release
HelpHub page for 6.0.2

@sergeybiryukov: 6.0.2 includes 3 security fixes, 12 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. fixes for core, and 5 bug fixes for the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor. Please update if you haven’t yet.

c) Discussion on early timeframe
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/. discussion highlighted by @jeffpaul: What should be the definition of the early timeframe within a major release cycle?

@clorith: Noting that the early keyword is in the workflow handbook under https://make.wordpress.org/core/handbook/contribute/trac/keywords/, and since it’s aimed specifically at committers, I would presume it’s aimed at committing early.

@davidbaumwald: @jeffpaul and I had a document somewhere that was going to be the prelude to a post about defining early.

@costdev: Just throwing this in as a consideration for the Make post: we might also consider having additional keywords for specificity. e.g. needs-early-decision, etc.

@clorith: In my head, “early discussion” is “discuss as much as you want until a decision is made, if it’s still in the discussion phase, it’s not ready for milestoning”. But that’s something that would likely come out of a make post with feedback I suspect .

@jeffpaul: I think the most important bit will be the timing of what “early” means.
Action: @clorith volunteered to draft a make/core post about it to gather input, and help cement this with a proper definition. Further discussion can be added on that post.


This has a related item on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher.
Ticketticket Created for both bug reports and feature development on the bug tracker. #55603 for discussion. This issue was highlighted at a bug scrub last week. Wider feedback is requested on the approach on the ticket 2nd-opinion php82

@hellofromtonya: The above ticket is something @jrf and I will be working on following up to live working session held recently.

@hellofromtonya: Please note, WordPress Core will not be fully compatible with PHP 8.2 by the time the new PHP version is released. Handling of dynamic properties has a POC but will not be ready in time. The plan is to commit.

5. Components and tickets

Are you a component maintainer? Shepherding a ticket? Beta 1 is four weeks away, scheduled for September 20, 2022.

@sergeybiryukov:

General: Code modernization efforts have continued on preparing WordPress core for PHP 8.2. Thanks @jrf, @antonvlasenko, @costdev, and everyone testing the PHP 8.2 PRs! Ticket #56033 for more details.

@clorith

Site Health has been making strides this past week with a few tickets going in (and a few being gardened and closed as no longer relevant, or non-reproducible).

@webcommsat: Just a reminder to our other component maintainers, please do share your updates and any help you need. You can add these asynchronously to the dev chat agenda or to the Summary on the Make/ Core blogblog (versus network, site). You can also raise any tickets that you would like to highlight for help, especially if they are planned for the next release.

6. Open Floor

– Topic description core Slack channel. Action: agreed to add Dev Chat date and time.

Props to @webcommsat for the dev chat summary and @marybaum and @costdev for review, and to those who facilitated the meeting.

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

Abha Thakor 2:30 am on August 31, 2022
Tags: , , , , summary   

Summary, Dev Chat, August 24, 2022

These are the notes from the weekly WordPress developers chat held on Wednesday August 24, 2022.

1. Welcome and introduction

2. Announcements

WordPress 6.0.2 RC 1 has landed! Please download and test.

3. Blogblog (versus network, site) posts

This is not all the posts published on the core blog during the last week, but major items highlighted for comment or queries.

A week in core (published August 25, 2022) – thank you @audrasjb

Feedback by September 9, 2022 is requested on a new system for updating HTML attributes.

The 16th Full Site Editing Call for Testing is still open. This features a simpler testing exercise. Deadline is September 2, 2022. Thanks @annezazu for the update.

4. Upcoming releases

a) The next major is 6.1.

@marybaum shared that @priethor has asked for green-yellow-red lights looking ahead to 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. release and almost all green were reported in the #6-1-release-leads channel.
No other updates were received on the agenda or during the meeting from the squad.

b) The next minor is 6.0.2.
The Release Candidate (RC1) is out.

Update via @sergeybiryukov

5. Components and tickets

This section is for updates from component maintainer or anyone shepherding a ticketticket Created for both bug reports and feature development on the bug tracker.. Beta 1 is five weeks away, so the time is ripe!

Updates from @sergeybiryukov for Build/Test Tools, Database, General, Themes, Date/ Time components

Build/Test Tools

As of yesterday, PHPUnit test runs 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/ Actions include PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.2, though addressing compatibility issues is still a work in progress. PHP 8.2 is expected to be released at the end of November 2022. Thanks @jrf.

More details at: Ticket #56009 Prepare for PHP 8.2

Compatibility with the recent versions of MariaDB (10.6+) and MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. (8.0+) was improved. With these and some other changes, specifically skipping tests for non-implemented REST API methods, most of the test runs from various hosting environments on the Host Test Results page successfully pass now, except for PHP 8.2.0alpha2 for now.

More details at: Tickets #51740 and #53623

Database

General: Code modernization efforts have continued on preparing WordPress core for PHP 8.2.

Thanks @jrf and @antonvlasenko.

More details at: Ticket #56033 PHP 8.2 explicitly declare all known properties

Themes

  • A 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. Themes filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. is now available on the Add Themes screen, to match a similar filter in the WordPress.org Theme Directory. Thanks @luminuu and @audrasjb.
    Ticket #56283 Add “Block theme” filter under “Add themes” for more details.
  • The support for Update URI theme headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. was added to core. This allows third-party themes to avoid accidentally being overwritten with an update of a theme of a similar name from the WordPress.org Theme Directory. Thanks @dd32, @meloniq, @costdev
  • Changeset [53933] and ticket #14179 for more details.

Thanks everyone who contributed to those tickets! 

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. components

Permalinks: No major news this week.

Site Health component

@clorith:

  • Tickets #54508 (add more information to site health message) & #54617 (add more details when site health checks fail) could benefit from copy review; @webcommsat and @marybaum will follow up.

Updates on Help/About and Bulk/ Quick Edit components

@marybaum: We moved one ticket on: #56210.

Thanks @webcommsat @ogleckler @nalininonstopnews and @sergeybiryukov for comments / discussion on components in these two components. Thanks for the commit @audrasjb.

@nalininonstopnewsuk:

Quick Edit/ Bulk edit – on the next few Mondays we will continue to look at some of the tickets and doing some triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.. We did some exploration on one particular ticket this last week. We will bring it to a bigger scrub potentially after that depending on progress.

As Mary had lost her internet connection, @nalininonstopnewsuk added: Thank you everyone for sharing. Dev chat is a good place for component maintainers to be able to share progress on their tickets and highlight any issues. You can let the core team reps know if you need some assistance too. 

As a newer maintainer, I appreciate the outreach from the team reps and from documentation at releases time. Dev chat also helps get more people to look at a specific point in an issue if needed. Just putting in my thoughts. @marybaum: Very valuable! Thanks so much.

Upgrade/ Install component

@costdev: Upgrade/Install: While we’ve had reviews from individual committers who happen to be on the Security, Docs and Polyglots teams, we’d like to make an official request to these teams here in dev chat and in their respective channels to review the Rollback Update Failure feature plugin for any potential issues.

No further update from maintainers nor tickets. Thanks everyone who has added tickets above.

6. Open Floor

@marybaum: We are going to talk about dev chat at 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. US 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/..

There were no other items added to the agenda today apart from the links we have already shared. Nothing else was raised.

@marybaum: Also huge thanks, Nalini, for stepping in and helping lead this chat today! Thanks and for the info you have sent across on some words for the glossary relating to the handbook Nalini. @nalininonstopnewsuk: Thank you for the handbook link about what dev chat does and its purpose. It is very interesting and useful.

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

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

Estela Rueda 8:56 pm on May 25, 2022
Tags: , , , summary   

Dev Chat Summary, May 25, 2022

Agenda followed for the weekly WordPress Developers Chat. The meeting was facilitated by @annezazu.

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 “Arturo” was released yesterday! Big props to all involved.
  • The dry run for the WordPress 6.0 Release took place on May 23, followed by a 24-hour code freeze.
  • WordPress 6.0 RC4 was released over the last week on May 20, 2022.

If you haven’t seen it yet, here is a great video covering the latest release:

If anyone is wondering how that amazing video was made, it is a combination of Figma storyboards and motion design in After Effects.

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

  • 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.3 is in the process of being released today as we speak.
  • The latest core editor improvement post on container blocks and 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. locking shows off some new features to explore with row/stack/group.
  • A recap of the latest hallway hangout happened this morning on FSE topics and might be of interest to folks here.

Next week, there will be a doubled up version of “This week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.” too.

4. Upcoming releases

With 6.0 just out the door, the focus turns to both 6.0.x and 6.1. Initial steps have been taken following the post release items in the handbook so stay tuned for more! Currently, a project board is open for 6.0.1 in case anyone likes to follow the details: https://github.com/orgs/WordPress/projects/31

There is only one reported issue so far and @annezazu, as co-release coordinator will be checking with other teams for any other issues reported with 6.0.

5. Component maintainers

Build/Test Tools reported by @sergeybiryukov:

  • 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/ Action Slack notifications now link to a specific run attempt. This makes it easier for someone to see the proper context of a specific notification in case of failure. See ticketticket Created for both bug reports and feature development on the bug tracker. #55652 for more details. Thanks @desrosj! 
  • Some instabilities (test leaks) were fixed in unit tests for comments. See ticket #54725 for more details. Thanks @hellofromtonya! 
  • General: The recommended minimum version for MariaDB was bumped to 10.3. See ticket #55791 for more details. Thanks @hellofromtonya, again! 
  • 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

Update/install reported by @afragen

Sitemaps component reported by @pbiron:

  • There is one ticket ready to commit for 6.1, #55633

6. Open floor

@audrasjb prepared some great stats on WordPress 6.0 contributors.

@hifidesign brought up a PR that documents pretty big 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. w/r/t to unnecessary duotone code being added to non-FSE themes #38299 and @annezazu mentioned that all of the work is being tracked in that ticket for anyone to follow up.

@afragen has a list of tickets that need a committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. review:

@pbironmentioned that the non-direct filesystem classes are difficult to test because it is often hard to set up a testing environment to test them. There is a proposal on the works to do a review/improvements of the various WP-Filesystem classes.

Props to: @estelaris for writing the summary and @annezazu for reviewing.

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

Estela Rueda 7:42 pm on May 19, 2022
Tags: , , , summary   

Dev Chat Summary, May 18, 2022

Update May 23, 2022 @webcommsat: the 6.0 Release Party will take place on May 24, 2022 at about 18:30 in the #core channel of 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/.. Find out more about what happens on the day and join in the testing.

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 Slack.

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, @marybaum and @annezazu for reviewing.

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

Abha Thakor 6:18 pm on May 11, 2022
Tags: , , summary,   

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

Abha Thakor 11:38 pm on May 6, 2022
Tags: , , , summary   

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 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 The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards.. 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

Abha Thakor 10:17 pm on April 27, 2022
Tags: , , , summary   

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, 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. 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

Abha Thakor 2:56 pm on April 22, 2022
Tags: , , summary   

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

marybaum 3:09 pm on April 14, 2022
Tags: , , summary   

Dev Chat summary, April 13, 2022

@marybaum and @webcommsat facilitated the WordPress Developers Chat on this agenda. You can o read the full meeting on the Make WordPress Slack.

Announcements

WordPress 6.0 Beta 1 landed on Tuesday, April 12. Please download and test!

Blogblog (versus network, site) posts of note

Followup on WebP by default proposal (April 12, 2022): The Performance Team will be reassessing this proposal to consider the feedback.

A Week in Core (April 11, 2022) – thanks to @audrasjb

Help wanted: Test WordPress 6.0 (April 12, 2022) – thanks @ironprogrammer

Help test the comments blocks for 6.0 – thanks @juanmaguitar

 More answers to round four of questions on the Full Site Editing (FSE) program. You can find answers from all the question rounds at fse-answers, from @annezazu

A new post on Core styles and customizations: the next steps, from @ramonopoly

Upcoming releases: 6.0

(Ed. note: 5.9.3 was the last maintenance update for 5.9, and there will likely only be security updates from here out. The CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team only talks about those after the fact.)

@annezazu reported in with a list of highlights:

  • Backporting PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes is complete: https://github.com/WordPress/gutenberg/issues/39889
  • There are loads of experimental APIs to address: https://github.com/WordPress/gutenberg/issues/40316
  • 15 out of 42 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. are drafted: https://github.com/WordPress/gutenberg/issues/39654

Anne also highlighted the WebP project post above.

@webcommsat reported in for Docs and the About page:

The three Release Documentation Leads are working closely with Learn WordPress to find places to collaborate, so users hear similar terms and get the idea that they mean somewhat similar things.

On the About page, the component scrub on the next several Mondays (Help/About, 20:00 UTC 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) will focus almost exclusively on that task. You can follow the action asynchronously on the ticket; to join the fun, come to the Monday scrubs!

6.0 walkthrough on April 7. If you missed this, the walkthrough itself is now up on WordPress TV.

6.0 bug-scrubs schedule.

(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: The triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. leads for 6.0 are @costdev and @chaion07, but you, dear reader, can lead 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, too, and scrub only the tickets you care about. You don’t need any special privileges or standing — just contact the leads to get on the schedule. Once you’ve held your scrub, you will have earned a mention in the 6.0 credits.

Open Floor

@annezazu reminded the group of the latest FSE Program Outreach call, which is due April 21, 2022.

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 2022

@webcommsat asked if anyone was working on items for the Core tables at WordCamp Europe Contributor Day, June 2, 2022

@adamsilverstein raised that volunteers were still needed to facilitate the Core table(s) at WordCamp Europe’s 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/..

After some discussion, @desrosj volunteered to organize tables for Core and Core-JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors., and to get together with the Getting-Started folks, if any, on a table where attendees can learn to set up a local WordPress environment. @marybaum volunteered to help with collateral materials, and @annezazu volunteered to add some FSE content.

Props to: @webcommsat for the agenda, @marybaum and @webcommsat for leading the meeting, @marybaum for writing the summary, and @webcommsat and release squad members for review.

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

Tyler Weitzman 8:59 am on April 9, 2022
Tags: , , , , summary   

Dev Chat Summary, April 6, 2022

1. Welcome

The agenda followed in this week’s WordPress developer chat meeting.

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. 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/..

Meeting facilitated by @marybaum and @webcommsat.

2. Announcements

WordPress 5.9.3 release is out! (April 5, 2022)

If you missed the WordPress 6.0 walkthrough, you can watch the video, read the transcript and the chat discussion all on the recap. This was a casual, guided walkthrough of many new features that are planned for WordPress 6.0,, and things that are likely to be released thereafter. Props to all involved.

3. Blogblog (versus network, site) posts for dev chat awareness

Thanks to everyone who has contributed and given their time to these posts and events.

4. Updates on the 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.0

Bug Scrub schedule for 6.0 list, which is regularly updated. Help the components maintainers and all those involved in progressing tickets by joining them on 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. You can also volunteer to run a bug scrub on the specific tickets you care about!

Update from @annezazu for the release co-ordinators:

  • currently no known blocking issues for the release. Things are proceeding as expected.
  • all issues related to the walkthrough have been opened or confirmed already filed. There is work underway around how best to integrate it into the current process.
  • Gutenberg 13.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). (the last Gutenberg release for inclusion in 6.0) was pushed by a few days to Friday, April 8 to allow for more time for PRs ahead of feature freeze/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. 1
  • the Core Editor Tech leads are feeling solid about coordinating backporting PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes and on the 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. front
  • two new release squad members to help make this release a success: @ndiego stepped into the Core Editor Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. lead role and @ironprogrammer stepped into co-lead the Test role for the squad
  • a post is in progress/underway around specific features to help test in the lead up to 6.0. This will include items like comments loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop., cover 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. as featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. PR, 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., and more

    Confirmed, post dev chat:
    – 6.0 Beta 1 Release Party at April 12, 2022, at 18:00 UTC

5. Open Floor

  • @afragen: needs feedback for the Plugin Dependencies feature project, aiming for 6.1. More design feedback requested, thanks to @paaljoachim for review so far.
  • Trac Ticket 55344 raised by @josklever. @adamsilverstein confirmed the issue, it needs a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to lazy load hidden widgets, and tests, in order to move forward.
  • @tylerwe: asked about potential options to integrate a text-to-speech into WordPress core for better #accessibility

Potential next steps in the discussion: (1) starting place with a 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 submission and check the Plugin Developer Handbook, (2) to aim for a WordPress core integration, it has to be entirely open-source and GPLGPL GNU General Public License. Also see copyright license. compatible, (3) bring discussion to an #accessibility meeting, (4) licensing questions, (5) provide more details on a Make post for feedback. Post dev chat: Tyler thanked @jeffpaul for further offline discussions about a potential plugin.

  • The Learn WordPress Social Learning MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. has block theme discussions around different parts of theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.. @daisyo welcomed anyone interested to join.
  • @webcommsat: WordCamp Europe 2022 Contributor Day, June 2, 2022 – if anyone would be interesting in volunteering to help at the core tables, please contact the Core Team Reps @marybaum and @audrasjb. Is anyone already preparing items which could be used from any of the core areas? If so, please can you let them know. Previously core has had a significant presence at WCEU contributor days, broken up into its different areas.
  • Event confirmed post dev chat from @marybaum and @nalininonstopnewsuk:
    Bug scrubs for the Quick/ Bulk Edit component and the About / Help Page component will be on April 11 2022, at 20:00 UTC The scrub will include discussion on the messaging strategy for the 6.0 About Page. All welcome to join.

Next Dev Chat meeting: April 13, 2022, 20:00 UTC in the Core Slack channel.

Props to: @marybaum and @webcommsat for facilitating the meeting, @tylerwe and @webcommsat for the dev chat summary, and @marybaum, @costdev, and @annezazu for the review.

Could you volunteer next week for the summary?

#5-9-3, #6-0, #dev-chat, #summary