Recap: WordPress 6.7 “Rollins” Retrospective

[Editor’s note: This survey was only answered by 3 people, only 2 of which were on the release squad. It’s useful as seeing three people’s distinct opinion, but not extrapolation.]

This post summarizes the feedback received from the WordPress 6.7 retrospective. Thank you to those who contributed their feedback via the retrospective survey and comments on the post.  For ease of reading, feedback has been synthesized. Full feedback is available for review in the anonymized form responses and comments to the original post.

Please remember that the following feedback are suggestions to bear in mind for future releases rather than action items for implementation. 

What would you keep?

  • Aligning Dev Chats to the time where Tech Release leads could attend was useful and should be considered in the future.
  • Release process.

What would you add?

  • Future release leads should be announced earlier—prior to the end of the previous release.
  • More robust testing around new features in conjunction with plugins.

What would you change, reduce, or remove?

  • The squad was announced too late.
  • The climate of contributing.

How did the collaboration feel?

This section included ways for one to indicate how much they agreed or disagreed with a statement around collaboration.

Would you like to be part of future release squads?

What is your feedback on the current release squad size?

Takeaways and next steps

  • One lead felt they and their co-leads were not appropriately respected by a sponsored non-lead and indicated their intent to not volunteer for another lead role without assurances that lead roles are to be respect by non-leads.
  • Another contributor indicated a general sense that release testing throughout the cycle was less that usual.

Props to @desrosj and @jeffpaul for reviewing this post. 

#6-7, #retrospective

WordPress 6.7.2 RC2 is now available

WordPress 6.7.2 Release Candidate 2 (RC2) is available for testing! Some ways you can help test this minor release:

  • Use the WordPress Beta Tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
    • As this is a minor 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). release, select the Point Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ to test: wp core update https://wordpress.org/wordpress-6.7.2-RC2.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.7.2 RC2 is a release candidaterelease 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). for a maintenance release with a focus on bugs introduced in WordPress 6.7. In total, this RC features fixes for 35 bugs throughout Core and the Block Editor. This also includes one fix for Twenty Twenty-Five which means a new version of that default theme will be released. Please see the RC1 announcement for a list of fixes. New fixes in RC2 are:

  • #62907 – 6.7 broke accordion styles for themes/plugins using `do_accordion_sections()`
  • #62597 – WordPress 6.7 sizes=”auto” is messing featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. on chrome mobile.
  • fix ensure post meta panel stays visible in all rendering modes gutenberg#69083

What’s next?

Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 6.7 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The final release is expected on Tuesday, February 11th, 2025. This date is subject to change if any issues with RC2 are discovered. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #6-7-release-leads channel, and releases are always packaged and tested in #core.

A special thanks to everyone who reported issues, helped test, and helped create patches. The success of 6.7.2 depends on proper testing, so please lend a helping hand.

Thanks to @fabiankaegy and @desrosj for pre-publication review.

#6-7, #6-7-2, #6-7-x, #minor-releases, #releases

WordPress 6.7.2 RC1 is now available

WordPress 6.7.2 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release:

  • Use the WordPress Beta Tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
    • As this is a minor 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). release, select the Point Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ to test: wp core update https://wordpress.org/wordpress-6.7.2-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.7.2 RC1 is a maintenance release with a focus on bugs introduced in WordPress 6.7. In total, this RC features fixes for 32 bugs throughout Core and the Block Editor. This also includes one fix for Twenty Twenty-Five which means a new version of that default theme will be released.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets and PRs are included:

What’s next?

Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 6.7 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The final release is expected on Tuesday, February 11th, 2025. This date is subject to change if any issues with RC1 are discovered. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #6-7-release-leads channel, and releases are always packaged and tested in #core.

A special thanks to everyone who reported issues, helped test, and helped create patches. The success of 6.7.2 depends on proper testing, so please lend a helping hand.

Thanks to @audrasjb and @desrosj for pre-publication review.

#6-7, #6-7-2, #6-7-x, #minor-releases, #releases

WordPress 6.7.2 Release Planning

WordPress 6.7.2 is scheduled to be the next maintenance release for the 6.7 version. Its release will follow the following preliminary schedule:

  • February 4, 2025 – Release Candidaterelease 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). made available and announced here on the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. site.
  • February 11, 2025 – Final release made available.

Specific times will be decided in advance and adjustments to the schedule may be made. All adjustments will be noted in this post.

Minor or Maintenance releases of WordPress are intended as bugbug A 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.-fix releases. If you have a 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. that you think should be considered, please put it in the 6.7.2 milestone. If you have a GitHubGitHub 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/ issue, please add it to the 6.7.x Editor Tasks board. If you lack bug gardening capabilities and have a ticket or issue you wish to highlight for 6.7.2, please add a comment here.

Note: except in extreme situations, only bug fixes will be considered and generally only bugs that have been introduced during the 6.7 cycle.

Get involved with 6.7.2

Bug Scrubs will happen in the #core room during the following times:

Each of the open tickets is going to require development work along with testing and review. You can also run your own scrubs to help ensure that all of the correct tickets are fixed in this release. Additionally, while the intent is for no new translated strings in this release, some locales have strings in 6.7 in need of translation.

General coordination for the release will happen in the #6-7-release-leads channel and decisions around code for the release will be made in the #core room.

This 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. will be led by myself (@jorbin), building off work started by @cbravobernal and @desrosj.

Thank you to @desrosj, @jeffpaul, and @joemcgill for pre-publication review.

#6-7, #6-7-2, #6-7-x

WordPress 6.7 Performance Improvements

This post is the latest in a series of updates focused on the performance improvements of major releases (see 6.6, 6.5, 6.4, 6.3, and 6.2).

WordPress 6.7, “Rollins” is the last major version of WordPress released in 2024. This release delivers important performance updates, including faster pattern loading, optimized previews in the data views component, improved PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8+ support and removal of deprecated code, auto sizes for lazy-loaded images, and more efficient tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) processing in the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways..

Explore the WordPress 6.7 Field Guide. Learn about the changes in this release with detailed developer notes.

Further details on the methodology behind these measurements are provided later in this article, along with an explanation of possible regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. sources.

Key improvements

Media: Auto sizes for lazy loaded images

In #61847,  support was added for sizes=”auto” for lazy-loaded images. This feature, which was recently added to the HTML specification, allows the  browser to use the rendered layout width of the image when selecting a source from the srcset list, since lazy loaded images don’t load until after the layout is known. It maintains backward compatibility while boosting performance, particularly for responsive and dynamic layouts. Explore the details in the official dev note.

Media: Caching _wp_image_editor_choose results for improved performance

In #61532, WordPress now caches the results of _wp_image_editor_choose, storing the WP_Image_Editor implementation that supports queried options. This avoids redundant and costly compatibility checks, such as multiple calls to WP_Image_Editor_Imagick::supports_mime_type(), often triggered during tasks like setting up wp_plupload_default_settings(). The cache, stored for one day, speeds up editor loading times and introduces a new global caching group, image_editor, to manage future optimizations for image editor performance.

Media: Improve speed of AVIF image generation

In #61758, the change results in the AVIF encoder working faster by raising heic:speed to 7 from the default of 5. AVIF generation time is reduced by up to 20% with minimal impact on image size.

Editor: New blockBlock Block 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. type registration APIs to improve performance

In #62002, new block type registration APIs were introduced, offering a more efficient way to manage block metadata and improve performance across the board. These APIs allow developers to register blocks more flexibly, reducing server-side processing and enhancing editor load times. With these changes, WordPress lays the groundwork for faster, more scalable block-based experiences while maintaining backward compatibility. Explore the details in the official dev note.

Editor: Caching Global Styles for Blocks

In #59595, profiling WordPress 6.4 revealed that the WP_Theme_JSON::compute_style_properties method could account for 6-11% of server time during page generation. To address this, the editor now caches the generated CSSCSS Cascading Style Sheets. for block nodes derived from merged Theme JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. data. By saving the computed styles in a transient, WordPress avoids repeated and resource-intensive operations, significantly improving performance and reducing server load. This change is a key optimization for sites leveraging block themes and theme.json.

Themes: Improve performance of applying background image styles in theme.json.

In #61858, the cost of using WP_Theme_JSON::get_block_nodes() for this in its original shape was high enough to lead to a performance regression. Therefore this changeset introduces a new option on the method that allows to bypass all logic except for retrieving the node paths, which is much faster and everything that this functionality needs.

Miscellaneous Editor improvements:

In addition to the previously listed editor improvements, this release includes the following list of changes that improves the editor experience itself:

Additional performance focused changes

In total, there were 23 performance related improvements included in this release, split evenly between new enhancements (12) and bugbug A 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 (11).

Performance metrics

In our analysis, block themes (Twenty Twenty-Four was tested) experienced a modest regression in performance. The median Largest Contentful Pain (LCP) time increased by ~6ms or ~3.5% in tests, and the median Time To First Byte (TTFB) shows a 2ms (2%) regression.

Classic themes show a slight improvement (Twenty Twenty-One was tested). The median Largest Contentful Pain (LCP) and Time To First Byte (TTFB) time shows a slight 0.2ms or 0.2% improvement in tests.

How release performance is measured

The performance measurements used for the overview are based on benchmarks conducted using an automated workflow on GitHubGitHub 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/ action runners. Benchmarks were taken from the homepage of the Twenty Twenty-one, Twenty Twenty-three, and Twenty Twenty-four themes, comparing WordPress 6.7 with WordPress 6.6.2 (the latest version of WP 6.6 available when 6.7 was released).

Performance metrics were collected from 100 runs for both CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Web Vitals (CWV) and Server-Timing headers provided by the Performance Lab pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party using CLI scripts from the WPP Research repo.

Benchmark Data

Follow up from this release

WordPress 6.7 shows a regression in performance. While some overhead typically accompanies new features, these declines point to areas where the performance team continues to investigate where these regressions came from and how they can be addressed in the upcoming releases.

Each release, the Performance Team looks for opportunities to improve the performance of WordPress for the following releases, which includes identifying ways we can improve the tooling and processes we use to support the performance practice. For example, we’re collecting opportunities to improve our performance testing in this GitHub issue

Performance Lab – the plugin(s) we use to test out new performance features for core – continues to add new features such as Image Prioritizer , Embed Optimizer, Speculative Loading, Performant Translations, Modern Image Formats, Enhanced Responsive Images, and Web Worker Offloading.

You can also follow progress on other performance-related work being planned for the WordPress 6.8 release in Trac. A full list of the Performance Team’s priorities for the year is available on the 2024 Roadmap page. Additionally, the 2025 Roadmap will be published early in Q1 2025 in the team’s handbook. Come join us in making WordPress as performant as possible.

Props to @joemcgill, @flixos90, @westonruter, and @fabiankaegy for contributing to this post.

#6-7, #core, #core-performance, #performance

WordPress 6.7 Release Retrospective

Congratulations to all who helped make WordPress 6.7! Now that it has launched, you’re invited to reflect and share your thoughts on the release process and squad to learn, iterate, and improve for future releases. 

Whether you led, contributed, tested, followed along—whatever your role, even if you didn’t have one—you are welcome to participate in this retrospective. So please take a moment to complete the form or leave public feedback in the comments below.

Please note: the survey is not anonymous. That’s in case a relevant person wants to reach you for further clarification. But your email address will not be shared publicly, and nobody is going to use it for any other purpose.

The form and comments will be open until January 13, 2025. Shortly thereafter, you’ll see a follow-up post with collected, anonymized results.

Again, thank you for your contributions to 6.7 “Rollins,” and for taking the time to help make future releases even better!


Props to @priethor for the peer review

#6-7 #retrospective

#core, #release-process

WordPress 6.7.1 RC1 is now available

WordPress 6.7.1 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release:

  • Use the WordPress Beta Tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party
    • As this is a minor 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). release, select the Point Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunk.
  • Use WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ to test: wp core update https://wordpress.org/wordpress-6.7.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.7.1 RC1 is a fast-follow maintenance release with a strict focus on bugs introduced in WordPress 6.7. In total, this RC features fixes for 16 bugs throughout Core and the Block Editor.

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

  • Customize: Slight side-scroll in sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. (#62313)
  • Customize: CSSCSS Cascading Style Sheets. error in CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. (#62335)
  • Editor: “Most Used” CategoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. Tabs Not Synced with “All Categories” Tab in Classic Editor (#62440)
  • Editor: BlockBlock Block 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. Editor converting new PNG uploads to JPEG with mangled backgrounds (#62447)
  • Editor: Fix uncategorized pattern browsing when pattern has no categories (GB-66945)
  • Editor: Fix TypeError when duplicating uncategorized theme patterns (GB-66889)
  • Editor: Prevent HEIC and HEIF files from always being uploaded on Safari (GB-67139)
  • HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.: serialize should include doctype when present (#62396)
  • i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. is not applied in load_theme_textdomain() function (#62337)
  • Interactivity API: Missing state properties and negation operator behave differently client/server (#62374)
  • Interactivity API: Remove redundant server state from Interactivity Router (#62465)
  • Login and Registration: Custom login logo CSS targets changed (#62410)
  • Media: Image editing in GD runs image stream functions multiple times (#62331)
  • Media: Auto-resizes reducing image sizes (#62413)
  • Menus: Untranslatable texts in adminadmin (and super admin) nav-menu.js (#62402)
  • Options, MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. APIs: Warning in wp_salt() since 6.7 (#62424)

What’s next?

Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 6.7 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The final release is expected on Thursday, November 21st, 2024. This date is subject to change if any issues with RC1 are discovered. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #6-7-release-leads channel, and releases are always packaged and tested in #core.

A special thanks to everyone who reported issues, helped test, and helped create patches. The success of 6.7.1 depends on proper testing, so please lend a helping hand

Thanks to @davidbaumwald, @cbravobernal, @sabernhardt, and @sarthaknagoshe2002 for pre-publication review.

#6-7, #6-7-x, #minor-releases, #releases

WordPress 6.7.1 Release Schedule

Since WordPress 6.7 was released last week, contributors have kept a close eye on incoming reports to the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Support Forums, TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., and the 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/ repository on GitHubGitHub 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/. Though volume has not been meaningfully higher than normal after a 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., most reports are describing a small set of issues that should be addressed expeditiously.

Schedule

WordPress 6.7.1 will be targeted for release on Thursday, November 21, 2024 with a very specific focus of only fixing bugs there were introduced in the 6.7 release. The goal is to deliver a small handful of high-impact bugbug A 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 for added stability prior to the busy online commerce holiday week consisting of Black Friday, Cyber Monday, and Giving Tuesday.

The release will be lead by myself (@desrosj) and @cbravobernal. If you’re interested in volunteering, please comment below or drop a message in the #6-7-release-squad channel in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Date/TimeEvent
Tuesday, November 19, 2024Continued triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., testing, and committing/backporting fixes.
Wednesday, November 20, 2024 at 13:00PM UTCGutenberg package updates released/pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party update released (if necessary).
Wednesday, November 20, 2024 at 17:00PM UTCWordPress 6.7.1 RC1
Thursday, November 21, 2024 at 13:30PM UTCWordPress 6.7.1 General Release

Targeted Fixes

The following are the high priority items that cumulatively make a fast-follow release necessary:

  • sizes=auto causing images to show smaller than they should (#62413)
  • Translations not being applied properly (#62337)
  • Patterns without categories break the editor when browsing uncategorized patterns (GB-66944/GB-66888)
  • Zoom in doesn’t focus on the right area of the screen based on selected item (a few PRs issues for this)
  • Zoom out button goes missing when plugins register toolbar items (GB-66884)

The following are bugs that should be included if ready, but as understood now are not affecting as many people or are less problematic:

  • Using the Upload button in image-based blocks in Safari unexpectedly converts images to HEIC with a temporary file name (#62447)
  • CategoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. management in the Classic Editor is broken (#62440)
  • CSSCSS Cascading Style Sheets. targets changed on the login screen affecting custom logos (#62410)

Finally, the following are minor bug fixes introduced in 6.7 that should also be considered:

  • Horizontal scroll bar in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. (#62313)
  • Undefined key warning in wp_salt() (#62424)
  • Untranslatable strings in nav-menu.js (#62402)

There is currently only one ticketticket Created for both bug reports and feature development on the bug tracker. that does not represent a bug introduced during 6.7 being considered: #62331. This is a pretty significant performance problem for sites using GD for image editing that should be considered. It was only discovered 2 weeks ago, too late to be considered for 6.7.

A full list of tickets being considered for 6.7.x minor releases can be found on Trac and the WordPress 6.7.x project board on GitHub.

Props @joemcgill for review.

#6-7, #6-7-1, #6-7-x, #minor-releases

Summary, Dev Chat, November 13, 2024

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., facilitated by @joemcgill. 🔗 Agenda post.

Announcements

WordPress 6.7 “Rollins” was released on November 12, 2024. A big thank you to everyone who contributed to this release!

To quote the release post:

WordPress 6.7 reflects the tireless efforts and passion of more than 780 contributors in countries all over the world. This release also welcomed over 230 first-time contributors!

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.8

We are currently in the WordPress 6.8 release cycle.

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/ release: 19.7

The next Gutenberg release will be 19.7, scheduled for November 20.

Discussion

There were two main topics today:

  1. Immediate issues that need to be addressed following the release
  2. Confirming volunteers to coordinate upcoming maintenance releases following 6.7

There are currently no immediate issues requiring a quick 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., so the first minor will likely be released in around 30 days.

@azaozz mentioned #62401 as something that may need addressing soon, but it is from 6.6 rather than 6.7.

@oglekler also raised #62413 for potential inclusion in the next minor release.

We also discussed the need to start to identify volunteers who are willing to help with minor releases as they are ready. We already have a list of 21 issues (1 fixed) set to the 6.7.1 release milestone. @joemcgill suggested we do a call for volunteers if needed next week.

Props to @joemcgill for proofreading.

#6-7, #core, #dev-chat, #summary

Agenda, Dev Chat, Nov 13, 2024

Notice: This abbreviated Dev Chat agenda is will be entirely focused on coordinating follow-up from yesterday’s 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. of WordPress 6.7.

The next WordPress Developers Chat will take place on Thursday at 01:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

Additional items will be referred to in the various curated agenda sections below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda.

Announcements

WordPress 6.7 “Rollins” was released on November 12, 2024.

Discussions

The discussion section of the agenda is to provide a place to discuss important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team.

Topics for this week will include:

  1. Immediate issues that need to be addressed following the release
  2. Confirming volunteers to coordinate upcoming maintenance releases following 6.7

If you want to nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting for discussion or if you will be async.

#6-7, #agenda, #dev-chat