Notes from the weekly WordPress developers chat held in the #core slack 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
Dev Chat summary from April 20, 2022 meeting
The agenda followed for April 27, 2022
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. Blog (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 plugin 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 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 notes Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include:
a description of the change;
the decision that led to this change
a description of how developers are supposed to work with that change.
Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and the Field 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 Trac 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, Core 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 bug 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 ticket 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 branch 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.