Title: Summary, Dev Chat, November 6, 2024 Author: Sarah Norris Published: November 6, 2024 --- [ ](https://profiles.wordpress.org/mikachan/) [Sarah Norris](https://profiles.wordpress.org/mikachan/) 1:06 pm _on_ November 6, 2024 Tags: [6-7 ( 75 )](https://make.wordpress.org/core/tag/6-7/), [core ( 756 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 932 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 980 )](https://make.wordpress.org/core/tag/summary/)    # Summary, Dev Chat, November 6, 2024 [Start](https://wordpress.slack.com/archives/C02RQBWTW/p1730855037471489) of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/), facilitated by [@joemcgill](https://profiles.wordpress.org/joemcgill/). 🔗 [Agenda post](https://make.wordpress.org/core/2024/11/05/agenda-dev-chat-november-6-2024/). ## Announcements [WordPress 6.7 RC 3 has been released](https://wordpress.org/news/2024/11/wordpress-6-7-release-candidate-3/). Thanks to everyone who participated in the release party. ## 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](https://make.wordpress.org/core/6-7/). WordPress 6.7 dry run is scheduled for Monday, November 11, with the full release scheduled for Tuesday, November 12. For specific release times, review [the release party schedule post](https://make.wordpress.org/core/2024/09/24/wordpress-6-7-release-party-schedule/). There are a couple more items that need to be backported since RCrelease candidate 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)](https://make.wordpress.org/core/2024/11/06/summary-dev-chat-november-6-2024/?output_format=md#alpha-beta). 3, such as [62305](https://core.trac.wordpress.org/ticket/62305). [62061](https://core.trac.wordpress.org/ticket/62061) also needs a dev notedev note Each 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, and 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. which includes a list of changes that were made during this release related to improving PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.4 support, which [@desrosj](https://profiles.wordpress.org/desrosj/) and [@marybaum](https://profiles.wordpress.org/marybaum/) offered to help with. ### Next maintenance release There are no maintenance releases planned at this time. ### Next 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/](https://wordpress.org/gutenberg/)󠁿 release: 19.6 The next Gutenberg release will be 19.6, scheduled for November 6. ## Discussion [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) [has requested](https://wordpress.slack.com/archives/C07BTF54N68/p1730760018785739) that we follow up the the following list of items during Dev Chat, if they have not already been resolved by then: > * Status of TT5 (cc [@poena](https://profiles.wordpress.org/poena/) [@juanfra](https://profiles.wordpress.org/juanfra/)), > will need to be async due to timezones > * Status of GB packages (cc [@get_dave](https://profiles.wordpress.org/get_dave/) > [@kevin940726](https://profiles.wordpress.org/kevin940726/)) > * Following tracTrac An open source project by Edgewall Software that serves > as a bug tracker and project management tool for WordPress. tickets need 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. sign-off for backportbackport A port is when code from one branch( > or trunk) is merged into another branch or trunk. Some changes in WordPress > point releases are the result of backporting code from trunk to the release > branch. > - [r59325](https://core.trac.wordpress.org/changeset/59325) for [61094](https://core.trac.wordpress.org/ticket/61094) > - [62272](https://core.trac.wordpress.org/ticket/62272) and [62305](https://core.trac.wordpress.org/ticket/62305)( > per [@azaozz](https://profiles.wordpress.org/azaozz/) [here](https://wordpress.slack.com/archives/C07BTF54N68/p1730745708999459)) > - [r59329](https://core.trac.wordpress.org/changeset/59329) for [61961](https://core.trac.wordpress.org/ticket/61961#comment:40)( > about page images) [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) confirmed that most of the backports in that list are complete: [#62305](https://core.trac.wordpress.org/ticket/62305) is the only one remaining. [@get_dave](https://profiles.wordpress.org/get_dave/) reported packages were done. [@joemcgill](https://profiles.wordpress.org/joemcgill/) noted there are some remaining commits for Twenty Twenty-Five to come in. As there are several commits landing after RC 3, there is a plan to do a silent RC 4 ahead of the dry run next week, likely on November 7. ## Open Floor [@justlevine](https://profiles.wordpress.org/justlevine/) requested some feedback on the following: > Id love to get some eyes/feedback on the PHPStan config over on [https://core.trac.wordpress.org/ticket/61175](https://core.trac.wordpress.org/ticket/61175). > The errors detected there have already resulted in a handful of merged PRs (via > [https://core.trac.wordpress.org/ticket/52217](https://core.trac.wordpress.org/ticket/52217)) > including a bugfix in 6.7, so already showing its worth. [@desrosj](https://profiles.wordpress.org/desrosj/) offered to help progress these. _Props to _[@joemcgill](https://profiles.wordpress.org/joemcgill/) _for proofreading._ [#6-7](https://make.wordpress.org/core/tag/6-7/), [#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2024/11/06/summary-dev-chat-november-6-2024/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2024/11/06/summary-dev-chat-november-6-2024/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2024/11/06/summary-dev-chat-november-6-2024/?share=bluesky) * [ X ](https://make.wordpress.org/core/2024/11/06/summary-dev-chat-november-6-2024/?share=x) * [ Facebook ](https://make.wordpress.org/core/2024/11/06/summary-dev-chat-november-6-2024/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2024/11/06/summary-dev-chat-november-6-2024/?share=linkedin) # Post navigation [← Performance Chat Summary: 5 November 2024](https://make.wordpress.org/core/2024/11/06/performance-chat-summary-05-november-2024/) [What’s new in Gutenberg 19.6? (6 Nov) →](https://make.wordpress.org/core/2024/11/06/whats-new-in-gutenberg-15-9-31-may-2-2/)