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.

marybaum 11:47 pm on November 15, 2022
Tags: agenda ( 996 ), core ( 562 ), dev chat ( 714 )

Dev chat agenda: Wednesday, November 16, 2022

How did it get to be mid-November already?

Thanks to @webcommsat, @desrosj, and @nalininonstopnewsuk for stepping in on almost no notice when @marybaum was unavailable last week.

1. Welcome

Last week’s summary – props to @webcommsat.

2. Announcements

WordPress 6.1.1 maintenance release has landed!

Nominations are open for 2023 Core Team rep.

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

From @audrasjb, A week in Core.

From @helen, Improving the contributor experience.

And from @jeffpaul last week, the release post for WordPress 6.1.1 RC1.

4. Upcoming releases

The next major is 6.2.

The next minor is 6.1.2.

5. Components and tickets

This is the 6.2 alpha period — time to work on your favorite enhancements. This is also the time in the cycle when the community settles on the main areas of focus for 6.2, based on the product roadmap.

6. Open floor

Got a topic? Add it to the comments.

#agenda, #core, #dev-chat

Earle Davies 12:28 am on November 16, 2022

I have a question/clarification for the open floor: are we allowed to remove existing functions, aka breaking changes during RCrelease 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). for a 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.? It’s my understanding the RC should only be for regressions and fixes found and not introduce new functionality or breaking functionality. https://core.trac.wordpress.org/changeset/54682 this commit released incredibly late in the cycle (RC 3 of WP 6.1) removed the function reset() and caused all sites with the WordPress Multilingual (WPML) 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 to fatal error when updating to WP 6.1. If removing functions is allowed during RC we should discuss making this disallowed as it serves no good purpose as it puts undue strain on everyone having to test against it. If this isn’t allowed I would suggest looking at the timeline of the commits and the 2 committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign off to understand why it was approved when we need approvals from multiple committers.

Comments are closed.

s: search
c: compose new post
r: reply
e: edit
t: go to top
j: go to the next post or comment
k: go to the previous post or comment
o: toggle comment visibility
esc: cancel edit post or comment