{"id":116157,"date":"2024-10-30T22:10:45","date_gmt":"2024-10-30T22:10:45","guid":{"rendered":"https:\/\/make.wordpress.org\/core\/?p=116157"},"modified":"2024-10-30T22:10:45","modified_gmt":"2024-10-30T22:10:45","slug":"summary-dev-chat-october-30-2024","status":"publish","type":"post","link":"https:\/\/make.wordpress.org\/core\/2024\/10\/30\/summary-dev-chat-october-30-2024\/","title":{"rendered":"Summary, Dev Chat, October 30, 2024"},"content":{"rendered":"

Start<\/a>\u00a0of the meeting in\u00a0SlackSlack<\/span> Slack is a Collaborative Group Chat Platform https:\/\/slack.com\/<\/a>. The WordPress community has its own Slack Channel at https:\/\/make.wordpress.org\/chat\/<\/a><\/span><\/span><\/span>, facilitated by @<\/span>joemcgill<\/a>. \ud83d\udd17 Agenda post<\/a>.<\/p>\n\n\n\n

\n

Announcements<\/h2>\n\n\n\n

WordPress 6.7 RC 2<\/a>\u00a0was released on October 29. Thank you to everyone who contributed to this release and attended the release party!<\/p>\n\n\n\n

Forthcoming releases<\/h2>\n\n\n\n

Next\u00a0major releasemajor release<\/span> 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.<\/span><\/span><\/span>: 6.7<\/h3>\n\n\n\n

We are currently in the\u00a0WordPress 6.7 release cycle<\/a>. WordPress 6.7 RCrelease candidate<\/span> 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)<\/a>.<\/span><\/span><\/span> 3 is scheduled for Tuesday, November 5. For specific release times, review\u00a0the release party schedule post<\/a>.<\/p>\n\n\n\n

There are a few open issues on the\u00a0next major report<\/a>. @<\/span>peterwilsoncc<\/a> mentioned that @adamsilverstein<\/a>\u00a0and\u00a0@azaozz<\/a>\u00a0have been working on some fixes for HEIC images that have been committed to trunktrunk<\/span> A 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.<\/span><\/span><\/span> (#62272<\/a>\u00a0and\u00a0#62305<\/a>). Most other items are tasks to make sure the old files list is updated, editor commits, etc.<\/p>\n\n\n\n

#61094<\/a>\u00a0was also recently reopened, which should hopefully be quick to review.<\/p>\n<\/div>\n\n\n\n

\n

Next maintenance release<\/h3>\n\n\n\n

There are no maintenance releases planned at this time.<\/p>\n\n\n\n

Next\u00a0GutenbergGutenberg<\/span> 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 \u2018blocks\u2019 to add richness rather than shortcodes, custom HTML etc.\rhttps:\/\/wordpress.org\/gutenberg\/<\/a><\/span><\/span><\/span>\u00a0release: 19.6<\/h3>\n\n\n\n

The next Gutenberg release will be 19.6, scheduled for November 6.<\/p>\n<\/div>\n\n\n\n

\n

Discussion<\/h2>\n\n\n\n

@<\/span>poena<\/a> gave an update on TT5:<\/p>\n\n\n\n

\n

There are still text string changes that needs approval from the Polyglots teamPolyglots Team<\/span> Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https:\/\/make.wordpress.org\/polyglots\/teams\/<\/a><\/span><\/span><\/span> since we are past the string freeze in 6.7. Because of that, the string changes did not make it into RC2. It seems unclear how to get the approval or who can give it.<\/p>\n\n\n\n

There are still changes being made to how some colors are applied, both to improve the user experience and the color contrast ratios.<\/p>\n<\/blockquote>\n\n\n\n

After Dev Chat, @<\/span>audrasjb<\/a> helped to approve and commit the string changesets for TT5.<\/p>\n\n\n\n

@<\/span>joemcgill<\/a> raised: Seems like last release, there was a lot of last minute coordination around marketing efforts to unify content between the about page and a standalone site for the release. Any idea how those efforts are coming along this release?<\/p>\n\n\n\n

@<\/span>ryelle<\/a> confirmed that this should be all good; the content for the About page is the same as the release page, and was finalized with RC1. Tracking the\u00a0wp.org<\/a>\u00a0release page is here:\u00a0https:\/\/github.com\/WordPress\/wporg-main-2022\/issues\/506<\/a>.<\/p>\n\n\n\n

Open Floor<\/h2>\n\n\n\n

@<\/span>joemcgill<\/a> asked: I\u2019d like to get some input about when we should consider moving these Dev Chat times back to the original time, before we changed it for this release cycle. I still think that this time shift was a good idea to enable more of the release squad to attend. However, the impact has definitely been lower engagement.<\/p>\n\n\n\n

It was discussed that the earliest date to move back to the original time of 20:00 UTC would be November 20, after the 6.7 release, just in case there is some early follow-up that needs input from release squad Tech Leads that would otherwise not be able to attend.<\/p>\n\n\n\n

Props to\u00a0<\/em>@<\/span>joemcgill<\/a> for proofreading.<\/em><\/p>\n<\/div>\n

#<\/span>6-7<\/a>, #<\/span>core<\/a>, #<\/span>dev-chat<\/a>, #<\/span>summary<\/a><\/p>