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.
This post lists 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 sessions dedicated to move things forward towards the next major WordPress release, 6.5, slated for March 26, 2024.
Everyone is welcome to join to help triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. tickets, explore tickets to contribute to by creating patches, writing or conducting tests, providing code reviews, and more. Things to keep in mind:
all features and enhancements should be in the 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. before 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. 1 (February 13, 2024) and most bugs and all strings need to be there before Release Candidaterelease 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 (RC1)
If you are working on 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., it is helpful if you can please plan your contribution to give enough time for other contributors to make suggestions, review and test.
Have a regular component scrub or triage session? PingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.”@audrasjb, @chaion07, @rajinsharwar on Slack to have it added to this page.
Start your own triage sessions
Decide what you want to focus on first.
The 6.5 triage sessions and moving forward these tickets are the priority for the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. team and the release. If you would like to lead sessions for these, they can be arranged and added to this schedule.
However, if you are interested in particular component or user focus, for example, to take care about RTL-tickets, this will be very welcome too.
Could you run a session to scrub old tickets? There are treasures which would benefit from scrubs and more contributors working on them in older tickets.
How to help?
In the core channel on Slack,ping @audrasjb, @chaion07, @rajinsharwar or one of the core team reps on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.
Useful reports and information
More will be added as the development cycle progresses
Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the core handbook.
