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 our bug tracker.
We use SlackĀ for real-time communication. Contributors live all over the world, so there are discussions happening at all hours of the day.
Our core development meetings are every Wednesday at 05:00 UTC and 20:00 UTC in the #core channel on Slack. Anyone can join and participate or listen in!
WordPress 5.5 will be the second major release of 2020 and aims to include a navigation menus blockBlockBlock is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., automatic updates for plugins and themes, a block directory, XML sitemaps, lazy loading, and update GutenbergGutenbergThe Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses āblocksā to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ to the latest release version as we continue to focus in 2020 on full site editing via Gutenberg. Matt Mullenweg is the Release LeadRelease LeadThe community member ultimately responsible for the Release., Jake Spurlock is the Release Coordinator, and David Baumwald is returning as TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. PM. Joining the are CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech Sergey Biryukov, Editor Tech Ella van Durpe, Editor Design Michael Arestad, Media Tech Andrew Ozz, AccessibilityAccessibilityAccessibility (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)Ā Tech JB Audras, Documentation Coordinator Justin Ahinon, and the Marketing/Comms Coordinator is Mary Baum. All release decisions will ultimately be this release teamsā to make and communicate while gathering input from the community. There will NOT be a new bundled theme included in 5.5.
Beta 1, begin writing Dev Notesdev noteEach 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 About page, and last chance to merge feature projects. (Slack archive, Zip download)
From this point on, no more commits for any new enhancements or feature requests in this release cycle, only 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. fixes and inline documentation. Work can continue on enhancements/feature requests not completed and committed by this point, and can be picked up for commit again at the start of the WordPress 5.6 development cycle.
Release Candidate 1, publish Field GuideField guideThe 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. with Dev Notes, commit About page, begin drafting release post, and hard string freeze. (Slack archive, Zip download)
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). 3, update About page images, and continue drafting release post. (Slack archive, Zip download)
10 August 2020 (+6d)
Dry run for release of WordPress 5.5 and 24 hour code freeze. (Slack archive)
To get involved in WordPress core development, head on over to TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. and pick a 5.5 ticket. Need help? Check out the Core Contributor Handbook. Get your patches done and submitted as soon as possible, then help find people to test the patches and leave feedback on the ticketticketCreated for both bug reports and feature development on the bug tracker.. Patches for enhancements will not be committed after the dates posted above, so that we can all focus on squashing bugs and deliver the most bug-free WordPress ever.
