The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
Thanks to the 21 contributors of the past week, including 4 new contributors! Kudos to the 3 coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.
Next minor releaseMinor ReleaseA 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.(s)
Please note that 5.8.2 was deferred due to the lack of ready-to-ship tickets.
Reminder: @desrosj and @circlecube are co-leading the 5.8.x releases. The 5.8.x point releases are coordinated in the #5-8-release-leadsSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. This channel is public and will be archived once 5.9 is released.
Next major releasemajor releaseA 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.
Concerning the next major release —WordPress 5.9— a planning roundup was published some weeks ago.
@kjellr introduced the new bundled theme on Make/Core right before the devchat.
As usual, there is a public repository on GitHub so feel free to help testing the theme, and to contribute to this cool project
@chanthaboune wanted to clarify that the go/no go date was moved to October 14. It’s just for scheduling conflicts, there is not any worry over the release.
@audrasjb will run another bugbugA 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 on Thursday October 7, 2021 at 20:00 UTC.
Reminder: everyone is welcome to run a bug scrub on the #core Slack channel. If you are interested, please read this handbook post: Leading bug scrubs and get in touch with @audrasjb or @francina for details.
Last week, PHPUnit tests started failing on PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 5.6 due to a combination of an older OpenSSL version and the DST Root CA X3 certificate that expired on September 30, 2021. This is now resolved by running the tests on the latest patchpatchA 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. version of PHP 5.6 (5.6.40 at the moment), instead of 5.6.20. See ticketticketCreated for both bug reports and feature development on the bug tracker.#54223 for more details.
HTTPHTTPHTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands.APIAPIAn 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. – @sergeybiryukov
The expired DST Root CA X3 certificate is now removed from the WP core certificate bundle to resolve issues with OpenSSL 1.0.2. See ticket #54207 for more details.
CustomizerCustomizerTool 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. – @dlh
The Customize component could use a designer’s eye on #54211.
There have been issues with pluginPluginA 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 installation/upgrade failures in plugins that have a large number of files. See #51857 (see comment 128 and below) and #54166.
@afragen thinks he have a solution in this pull request and would love some more testing and hopefully an early commit if appropriate.
Also, there are 2 different PRs for #22316 that take different approaches: PR1547 and PR1724.
It would be great to get feedback on which approach is preferred and work on getting that committed. Please test both and leave feedback.
@audrasjb noted that both PRs have detailed testing instructions. They are easy to test and any feedback is welcome.
The three tickets marked early about jQuery updates (37110, #51812, #52163) are almost ready to ship, so there are RCrelease candidateOne 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).’s in for testing at least.
Open Floor
@annezazu wanted to encourage everyone to attend the Pattern Party call for testing for the #fse-outreach-experiment. All are welcome to join in and she is always open to feedback to make participating even easier.
Thanks to the 23 contributors of the past week, including 4 new contributors! Kudos to the 5 coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.
Next minor releaseMinor ReleaseA 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.(s)
The 5.8.x point releases are coordinated in the #5-8-release-leadsSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. This channel is public and will be archived once 5.9 is released.
@costdev pointed out that a patchpatchA 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. for ticketticketCreated for both bug reports and feature development on the bug tracker. #53801 leads to a change in both Core and in the @wordpress/widgets package and asked for advices for how to ensure that any changes are committed at the same time to minimise issues on either end. @audrasjb answered that there is already an issue for this ticket in the 5.8.2 Gutenberg project board.
Next major releasemajor releaseA 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.
Concerning the next major release —WordPress 5.9— a planning roundup was published a couple weeks ago.
@audrasjb ran a first bugbugA 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 last week to review the tickets marked early. He will run another one on Thursday September 30, 2019 at 20:00 UTC.
Reminder: everyone is welcome to run a bug scrub on the #core Slack channel. If you are interested, please read this handbook post: Leading bug scrubs and get in touch with @audrasjb or @francina for details.
Also, @audrasjb silently scrubbed the Future Release queue and moved a dozen of tickets (in various components) to 5.9, with refreshed patches when needed. Most of them are ready and waiting for review/commit.
PHPUnit 9.5.10 and 8.5.21 were released with a breaking change: PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher deprecations are no longer converted to exceptions by default (convertDeprecationsToExceptions="true" can be configured to enable this). See changeset [51871] and ticket #54183 for more details.
This is also included in the Changes to the WordPress Core PHP Test Suitedev notedev noteEach 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., which is highly recommended to read as it includes other important changes for pluginPluginA 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 theme authors using the WordPress Core test framework as a basis for their integration tests.
@joyously asked if it is supposed to handle initial installation or deactivation and uninstall also? @audrasjb answered that it only handles initial installation, because a dependency could exists without the “base” plugin.
@joyously asked what value does this enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. add to the existing implementation. @clorith answered that It surfaces which plugins would enhance (or enable) functionality, so yes it has value. @audrasjb added that it standardizes a process which currently has many different implementations.
@afragen encouraged testers to install the PR, add a test plugin with a couple of dot org plugin slugs in a comma separated list in the Required PluginsheaderHeaderThe 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.. Removing or changing the header name will deactivate those dependencies from being displayed.
@costdev noted that the Administration component doesn’t have a maintainer currently listed. He asked for a review of #53152. @sergeybiryukov moved it to milestone 5.9.
@pbearne asked for a review of #54020. He’s available to make a simpler patch if needed.
Thanks to the 42 contributors of the past week, including 7 new contributors! Kudos to the 4 coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too.
Next minor releaseMinor ReleaseA 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.(s)
They will publish a schedule for 5.8.2 and –if needed– 5.8.3 on September 23.
Next major releasemajor releaseA 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.
Concerning the next major release —WordPress 5.9— a planning roundup was published a couple weeks ago.
@audrasjb proposed to start to schedule bugbugA 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 for the milestone. He will run the first scrub of 5.9 on Thursday September 23, 2019 at 20:00 UTC.
Reminder: everyone is welcome to run a bug scrub on the #coreSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel. If you are interested, please read this handbook post: Leading bug scrubs. And yes, that’s a call for volunteers 🙂 Please add a comment below if you want to help.
For 5.9, @hellofromtonya pointed out that it would be nice to try to also plan some APAC-friendly bug scrubs when possible.
Some changes were implemented to make the PHPUnit Polyfills loading more flexible and improve the related messaging. See changesets 51810-51813 and ticketticketCreated for both bug reports and feature development on the bug tracker.#46149 for more details.
The PHPUnit Polyfills package and related test infrastructure changes are now backported to a few older branches (WP 5.8 to 5.2). This makes it easier for developers to continue testing on multiple versions of WordPress while adding tests for newer versions of PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher, which require more modern PHPUnit practices. See changesets 51838-51840, 51843-51846 and ticket #53911 for more details.
Work is now complete on Modernizing to the Latest PHPUnit version. Dev notedev noteEach 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. is being reviewed and plan is to publish on Monday.
PHP 8.1: work is nearly complete, i.e. identified through tests. Will be shifting shortly into community feedback and open call for contributions to identify and help fix compatibility issues.
A translator comment was added to clarify the “BlockBlockBlock 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.HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.” string in the Block widgetWidgetA WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. settings form. This should reduce confusion for Polyglots translating the string.
The attendees did not add comments to the posts highlighted in the agenda.
Worth mentioning
Thanks to the 61 contributors of the past week, including 7 new contributors! Kudos to the 7 coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. committers of the week, too
WordPress 5.8.1 release team ran into an issue with GitHubGitHubGitHub 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/ that required a chunk of manual work. WordPress 5.8.1 went out few hours after the chat.
The Polyglots TeamPolyglots TeamPolyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. is currently organizing the 2021 edition of the WordPress Translation Days.
Work on the jquery upgrade is rolling on now, @azaozz is working on the PR
Component maintainers
Build/Test Tools
Work has continued on adding missing @covers tags to unit tests for more accurate coverage. See ticketticketCreated for both bug reports and feature development on the bug tracker.#39265 for more details.
General
Work has continued on:
#51553 – Fixing parameter name mismatches for parent/child classes for PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 named parameter support.
The attendees did not add comments to the posts highlighted in the agenda.
Worth mentioning
Thanks to the 34 people who contributed to WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. on TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. last week, including 2 new contributors! Kudos to the 8 core committers of the week, too
WordPress 5.8.1 RCrelease candidateOne 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 was released right before the dev-chat.
@webcommsat announced that the 6th edition of WordPress TranslationtranslationThe process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. Day has started on September 1st and will run through the whole month: you can check the dedicated website.
@annezazu reported that a proof of concept for a migrationMigrationMoving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. to Playwright was shared during the core editor meeting and well received thus far.
Tonya noted that the Test team is working on updating the local testing docs in the handbook to include not only wp-env but also multiple workflow alternatives.
Empower everyone to contribute!
Tonya Mork
Component maintainers
Build/Test Tools
Work continues on improving the PHPUnit test suite and PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 fixes.
Help/About
@webcommsat and @marybaum are meeting to plan ahead for WordPress 5.9 and what are the implications of auto-updates on the About page.
The Rollback Update Failurefeature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. now has similar function as the proposed PR1492 for #51857. @sergeybiryukov is reviewing an issue with servers that disable disk_free_space()
Open Floor
Tonya brought up #53450 and asked for feedback. Two committers added positive comments so it looks like it’s a good candidate for WordPress 5.9.
Abha reminded everyone about the resources and links that the Marketing team created to promote multiple Make teams.
Michale Rehnert asked about how to set up a Docker container for contributing purposes. @helen suggested two resources:
The attendees did not add comments to the posts highlighted in the agenda.
Worth mentioning
Thanks to the 21 people who contributed to WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. on TracTracAn 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.
During a working session, on August 24, 2021, a group of contributors overhauled the PHPUnit documentation for the WordPress unit testunit testCode 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 UIUIUser interface. The 1.13.0-alpha.1 version of the library was already released.
#53635 – Work continues on making various compatibility fixes for PHPPHPThe 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 trunktrunkA 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.
#51857 is getting close to commit status. A few issues came up in the Site Health and they were documented in the ticketticketCreated for both bug reports and feature development on the bug tracker. by @afragen. Related #51928.
#15134 has a patchpatchA 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 blockerblockerA 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.
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 trunktrunkA 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 BetaBetaA 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 pluginPluginA 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 CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. on TracTracAn 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.
@hellofromtonya invited everyone to join the weekly working session where core contributorsCore ContributorsCore 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 noteEach 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., open tickets for PHPPHPThe 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 SlackSlackSlack 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.
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.
From @audrasjb, A Week in Core highlights the moving parts of CoreCoreCore 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 CSSCSSCascading 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 BranchbranchA 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 LeadThe 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.
TicketticketCreated 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 PHPPHPThe 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.
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 ReleaseA 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.
