Dev Chat summary: Wednesday, December 21, 2022

Welcome!

The WordPress coreCore Core 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 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

If you’re new to dev chat, you can find out more about this weekly meeting in the handbook. (calendar)

This meeting was held on 8:00 pm UTC. The next dev chat will be on January 4, 2023 at 8:00 pm UTC. Note: there will not be a dev chat on December 28, 2022.

1) Welcome

Meeting facilitator: @marybaum.

Agenda followed; thanks to @webcommsat for preparing it.

Start of the meeting in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel of the Make WordPress Slack.

Summary from the December 14, 2022 dev chat.

2) Announcements

2022 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 welcomes incoming 2023 core team reps @hellofromtonya and @webcommsat.
The 2022 State of the Word video is now available on youtube.

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

4) Upcoming releases

a) 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. is 6.2

6.2 is expected to land in March according to the State of the Word address.

b) The next 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. is 6.1.2

5) Components and tickets

a) Components

No issues were raised.

b) Tickets assistance / highlight

No tickets were raised.

6) Open floor

@robinwpdeveloper notes the new core contributors meeting that happens every other Wednesday at 19:00 UTC (calendar) to help new 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. get started is scheduled at a time that makes it difficult for people in APAC time zones to attend. He proposes there be a new core contributor meeting scheduled on the first Wednesday each month at 5:00 UTC. Please comment on this post with feedback.

From the Core team: Props to our 2022 core team reps @audrasjb and @marybaum! 2022 was a challenging year and was made possible thanks to the wonderful examples you’ve set in leadership, kindness, and inclusivity. Thank you for everything you’ve done and continue to do to make the WordPress project flourish.

Props to: @marybaum for running dev chat, @dpotter05 for the summary, and to @webcommsat and @marybaum for review.

#6-1, #6-2, #core, #dev-chat, #summary