Summary, Dev Chat, August 14, 2024

Announcements

GutenbergGutenberg 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/ 19.0 was released earlier today 🎉 You can read the release post here.

The WordPress 6.7 release squad was announced just before this meeting! You can find the list of squad members here.

Forthcoming Releases

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.: 6.7

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBeta 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. 1 is scheduled for Tuesday, October 1.

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.: 6.6.2

The next maintenance release will be 6.6.2. @hellofromtonya shared in the meeting that the release date may be delayed by a few weeks to early September to address all of the CSSCSS Cascading Style Sheets. specificity issues being tracked in this Gutenberg issue. Once a date is confirmed, Tonya will post an update on the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. site.

Next Gutenberg release: 19.1

The next Gutenberg release will be 19.1, scheduled for August 28.

Discussion

Update on changing the Dev Chat time for 6.7 – Now that the release squad for 6.7 has been announced, @joemcgill is going to give them an opportunity for feedback on the original post, and then confirm an updated Dev Chat time starting next week. Currently, Wednesday, Aug. 21 at 1:00 UTC is looking likely.

@karmatosed reminded that we should make sure to post agendas maybe day before and ask those not attending due to time zone to get their updates added. It will need to be a habit for some.

@clorith suggested some ideas for automating the agendas to make it easier to publish at a consistent time each week.

Open Floor

@dmsnell is asking for additional feedback on #61864. To summarize:

[this] fixes old commits and errors caused by our subversion-to-git process, as noted in the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker.. For example, a number of contributors are stuck with corrupted names because the conversion script double-UTF-8 encodes text from the WordPress.org profiles.

it’s a one-off thing I proposed, but in the future allows each contributor to have control over their own representation. we don’t have to maintain it because we simply haven’t been maintaining this stuff at all. it doesn’t particularly go out of date, but a 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. may change their name and not update the file. it’s their option to do so or not

if there’s no problem there’s no need to be added to the list. for example, I have no commits from the time a GUID was added as the email domain, and I haven’t changed my name. so I’m not in the list. only people who have commits from multiple identities and people whose names have been corrupted by the conversion are in the list right now.

Props to @mikachan for proofreading.