Dev chat summary, August 25, 2021

@francina led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

The attendees did not add comments to the posts highlighted in the agenda.

Worth mentioning

Thanks to the 21 people who contributed to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. last week, including 5 new contributors! Kudos to the 5 core committers of the week, too.

A Week in Core – August 23, 2021

Announcements

Not in the agenda, but fresh from the press: An Update on the Classic Editor Plugin.

Component maintainers

Build/Test Tools

During a working session, on August 24, 2021, a group of contributors overhauled the PHPUnit documentation for the WordPress unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. suite: https://make.wordpress.org/core/handbook/testing/automated-testing/phpunit/

External libraries

To remove the jQuery Migrate script from Core, the maintainers are waiting on a release from jQuery UIUI User interface. The 1.13.0-alpha.1 version of the library was already released.

Hareesh Pillai pointed the attendees to #52163.

General

#53635 – Work continues on making various compatibility fixes for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1.

Media

There are few fixes planned for 5.8.1, mostly around WebP support and image conversion.

  • The bigger/more complex #53668 is already in 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., more testing appreciated as always.
  • #53667 also is getting checked by @azaozz

Upgrade/Install

  • #51857 is getting close to commit status. A few issues came up in the Site Health and they were documented in the ticketticket Created for both bug reports and feature development on the bug tracker. by @afragen. Related #51928.
  • #15134 has 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. and @pbiron asked for testing. Related #36710.
  • Work on symlinked plugins would be very helpful for many developers, but it’s not a blockerblocker A bug which is so severe that it blocks a release. for 51857. The support has been in place since 4.x but is not “universal” aka there are still some places where the wrong thing happens.

See you next week!

#5-8-x, #5-9, #dev-chat, #summary

Dev chat summary, August 18, 2021

@francina led the chat on this agenda. You can also read the Slack logs.

We welcomed a couple of first-time attendees, always a happy chat when it happens!

Highlighted blogblog (versus network, site) posts

The attendees did not add comments to the posts highlighted in the agenda, but Francesca encouraged everyone to test WordPress 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. with the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. Tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and report bugs.

Worth mentioning

Thanks to the 31 people who contributed to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. last week, including 3 new contributors! Kudos to the 2 core committers of the week, too.

A Week in Core – August 16, 2021

Announcements

@annezazu reminded everyone about an upcoming deadline, to respond to the current call for testing.

@hellofromtonya invited everyone to join the weekly working session where core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. will cover testing docs, 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., open tickets for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 testing, and for recent test modernization. They are announced in the core-test channel in 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/., so keep an eye on them!

Component maintainers

Build/Test Tools

@sergeybiryukov announced that the WordPress test suite is compatible with PHPUnit 8 & 9, and runs tests on PHP 8.1 beta (scheduled for release in November). See tickets #46149 and #53891 for more details.

As some of these test improvements were an unavoidable backward compatibility break for plugins/themes running tests on the WordPress core framework, there is an ongoing discussion about backporting some of these changes to older branches. Two main reasons for backporting:

  • Make WP security releases easier by not having to rewrite the tests that accompany security backports for older PHPUnit versions.
  • Help minimize the impact on the extender community who need to do cross-version testing against older versions of WordPress.

You can check #53911 for more details. Feedback welcome!

General

#53635 – Work continues on making various compatibility fixes for PHP 8.1.

Upgrade/Install

#51857 – Work continues on adding rollback for failed plugin/themes updates. You can also read Upgrade/Install Meeting Notes, August 17.

Open Floor

Christian Herrmann brought up two tickets:

A lively discussion ensued about the state of old tickets that lose momentum. It’s important to keep the conversation alive. Everyone is invited to add comments to tickets, refresh patches, and bring them up during dev-chat or scrubs when they will be scheduled for WordPress 5.9 and beyond.

Francesca also pointed new attendees to some resources that can be helpful if you want to contribute to WordPress.


See you next week!

#5-8-x, #5-9, #dev-chat, #summary

Dev chat summary, August 4, 2021

@francina led the chat on this agenda.

Highlighted blogblog (versus network, site) posts

From @audrasjb, A Week in Core highlights the moving parts of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and recognizes a week’s worth of contributors at a time.

From @notlaura comes a Call for CSS Contributors. If you’ve been looking for a way to sink your teeth into CSSCSS Cascading Style Sheets. Custom Properties (aka CSS variables), this is your chance to learn them well and help land them in Core.

From @sergeybiryukov comes more news on building the auto-updater ecosystem. If you work on themes and plugins, Sergey’s group would very much appreciate your feedback. The group would also like to hear from web hosts, as @ipstenu and a couple of other folks pointed out.

If you haven’t yet read @desrosj‘s post on Consistent Minor-Release Squad Leaders for Each Major 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".: Trial-run Retrospective and 5.8.x Releases, you’ll want to make time for it — the post is getting great reviews.

“Super interesting! … Super insightful!” — @francina

“Yeah. That’s a good read.” — @johnbillion

@francina suggested that if you’re interested in volunteering as a Release LeadRelease Lead The community member ultimately responsible for the Release. or a Release Deputy for the 5.8.x minors, please leave a comment on @desrosj‘s post.

And, from @chanthaboune and her talented production team comes the WP Briefing podcast. It’s on hiatus now, but more episodes will arrive in September. (So you’ve got time to catch up on the ones that have already dropped!)

Component maintainers

Reporting in on Build/Test tools, @sergeybiryukov had several announcements.

Ticketticket Created for both bug reports and feature development on the bug tracker. #52644: when a workflow fails, a message now gets posted to #core. That will make it easier to notice and fix failures in testing, Sergey explained and then thanked @desrosj publicly for his help on this. For details, see the ticket.

Ticket #47381: So that the WordPress Project can use more modern PHPUnit versions, this ticket makes several changes that make it easier to run unit tests against a variety of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher versions:

  • It removes the composer.lock file.
  • The PHPUnit 9.x mock object classes use a custom autoloader.
  • And the tests now always run in Composer.

Sergey thanked @jrf publicly for her work on the changes.

Reporting on General, @sergeybiryukov thanked @jrf again and announced that work has started on a variety of compatibility fixes for PHP 8.1. Details are in Ticket #52644.

Open Floor

@francina started Open Floor with news of a streaming PHP brainstorming, learning and teaching session that happened on Friday, August 30.

If you missed it, it’s up on YouTube. Featuring @jrf, @hellofromtonya, @sergeybiryukov, and @johnbillion, @hellofromtonya described the session as a “working session on modernizing the test suites. Got consensus and an action plan.”

Tonya noted that commits are in process, and @francina asked for ways the community can help.

In Highlighted Posts, @francina had asked @desrosj what encouraging words he had for people who’d like to volunteer with major and minor releases. Now, in Open Floor, she circled back around, and Jonathan pointed out that you don’t have to have any previous experience leading a major or 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. to get involved.

So if you’re interested, please comment. And get involved!

@webcommsat brought two items from Marketing to Open Floor: one on promoting favorite features in WordPress 5.8 and one on search terms for release information. Full details are in the chat here.

Thanks and props to post reviewer @desrosj!

#5-8-x, #5-9, #dev-chat, #summary