Start of the WordPress Developers Chat meeting on the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Make WordPress 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/. channel.
Summary from previous week
1. Welcome and Housekeeping
A great way to contribute to Core is writing summary posts for the developers chat. If you would like to help, please sign up for 23 February and 2 March 2022 in the comments.
3. Blog (versus network, site) posts of note
4. Upcoming releases
a) WordPress 6.0
Planning for WordPress release 6.0 has started. There are open roles on the 6.0 team (Editor Tech, Triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead, Test Lead, Accessibility 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) Lead), and other volunteers needed so please comment on the post for those with interest/availability. More details on the roadmap for 6.0.
b) WordPress 5.9x
WordPress 5.9.x release team and 5.9.1 schedule (16 February 2022).
There are 45 tickets in the milestone:
- 21 are closed and backported to 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". 5.9
- 6 are reopened for backport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. or for further changes
- 18 are still in progress: some to be moved to the next minor after the meeting
- should be ready to run 5.9.1 tomorrow Thursday planning at 20.00 UTC (time can still change)
5. Open Floor
- @joyously mentioned this issue for an old browser, visiting the .org 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 site.
Her question: should the supported browser list be just for WordPress, or sites made by WordPress (like WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/)? @jeffpaul mentioned that there is answer in terms of browser support on the ticket Created for both bug reports and feature development on the bug tracker., as well as the
browserlist. A discussion followed: view the original in the Slack timeline.
- @costdev raised several areas for 6.0: Requests 2.0, Core Upgrader, Handling filenames in case-(in)sensitive filesystems, a preloader for resources needed during Core upgrades, temporary backup and rollback in the event of plugin update failures, plugin dependencies, test suite improvements. Make posts will promote further discussion and consensus.
Next dev chat
The team publishes an agenda the day before the weekly dev chat. That gives you time to suggest additional own items or links by just leaving a comment. If you would like to help write the dev chat summary for a future meeting, contact the Core Team Reps @marybaum and @audrasjb.
Props to: @marybaum and @webcommsat for facilitating dev chat, @estelaris for writing the summary notes. Thanks to @marybaum and @webcommsat for reviewing the notes.
#5-9-1, #dev-chat, #meeting-notes, #summary, #week-in-core