Announcements
WordPress 6.5 RC 1 was released on March 5, 2024. Thanks to everyone involved and those who helped test.
Forthcoming Releases
Next major 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.: 6.5
There are several important changes to our normal development process during the RC 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). stage. For more, see this post: WordPress 6.5 Release Candidate Phase.
Please continue to test the 6.5 release. See this list of key features to test, which was published alongside WP 6.5 Beta A 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. 3.
During the meeting, @marybaum confirmed the release team for RC2, scheduled for next Tuesday, March 12, 2024. @akshayar will host, @davidbaumwald will run Mission Control (MC), and @audrasjb will be the committer 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. (with @hellofromtonya as a backup).
Next Gutenberg The 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/ release: 17.9
Gutenberg 17.9 is scheduled for release on March 13 and will include these issues.
Discussion
The discussion topic for today centered on: how can we make it easier to follow the decision process of major decisions across the project? This was originally raised by @marybaum and there is some background discussion here.
The discussion starts here in Slack. There were no clear next steps identified, but a summary of topics raised include:
- We could consider having a way to share more regular status updates for primary features in a release in order to surface key decisions, request feedback, get more visibility of concerns raised, etc.
- When key decisions need to be made, how can we ensure the context is easily accessible?
- We should be careful about not adding more noise to the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team blog (versus network, site) during an already busy release period.
- When key decisions are made, they should be documented in an appropriate place that is easy to reference (e.g., GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/, Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., Core Team blog, etc.)
Highlighted posts
The full list of posts from the last week in Core can be read on the agenda at this link.
Open floor
Due to time, we did not have time for open floor this week.
Props to @mikachan for reviewing.
#6-5, #dev-chat, #summary
