Tag Archives: 6-5

Aaron Jorbin 6:27 pm on May 30, 2024
Tags: 6-5, , ,   

WordPress 6.5.4 RC1 is now available

WordPress 6.5.4 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.5.4-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.5.4 RC1 features 3 fixes in Core.

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:

Additionally, two build and test tool changes have been made to the 6.5 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". to ensure the continued ability to maintain this version of WordPress. These do not affect user code.

What’s next?

The dev-reviewed workflow (double committer sign-off) remains in effect when making changes to the 6.5 branch.

The final release is expected on Wednesday, June 5th, 2024. Please note that this date can change depending on possible issues after RC1 is released. 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-5-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

Thanks to @hellofromtonya for pre-publication review and @davidbaumwald for RC package assistance.

#6-5, #6-5-x, #minor-releases, #releases

Aaron Jorbin 3:53 pm on May 24, 2024
Tags: 6-5,   

WordPress 6.5.4: An upcoming maintenance release

A number of 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 authors have reported that the fix introduced as a part of #60992 has not sufficiently helped their users, therefore #61269 is being proposed as a short cycle fix. In order to get this fix released quickly, WordPress 6.5.4 is being planned with the following schedule.

  • 30 May 2024 – 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.
  • 5 June 2024 – 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 only 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.5.4 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.5.x Editor Tasks board. If you lack bug gardening capabilities and have a ticket or issue you wish to highlight for 6.5.4, 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.5 cycle.

Get involved with 6.5.4

Each of the open tickets in the milestone is going to require development work along with testing and review. Additionally, while the intent is for no new translated strings in this release, some locales have strings in 6.5 in need of translation.

General coordination for the release will happen in the #6-5-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 @hellofromtonya, @costdev, and myself (@jorbin). If there are editor related issues that need to be included, @grantmkin has agreed to lead those as well.

Thanks to @joemcgill, @costdev, @grantmkin, and @hellofromtonya for prepublication review.

#6-5, #6-5-x

Akshaya Rane 1:09 am on May 8, 2024
Tags: 6-5,   

Recap: WordPress 6.5 “Regina” Retrospective

This post summarizes the feedback received from the WordPress 6.5 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?

  • More than one Editor tech lead
  • 24-hour Comitter freeze before the release party
  • Run the release party by release coordinators

What would you add?

  • A lead dev, specifically identified for each feature project. More lead dev or coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. feedback for feature projects 
  • Transparency of “leadership” decisions.
  • Increase in our release cadence. Docs lead & design team collaboration increase for 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. & Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.. A field guide can be made simpler as 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/ releases updates posts. 
  • Form the upcoming release squad early. Provide heads-up to selected squad members before x.y Release squad post gets published. Also, Allow them to set the Roadmap.
  • Improve Gutenberg feature merges into Core. If a feature satisfies the MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia, include it; half-baked features should wait until they, too, work at the MVP level. 
  • Automate some parts of the Release process to avoid errors & reduce release party time.

What would you change, reduce, or remove?

  • Sync GB packages more often. Make Gutenberg follow the same rules as TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. for commit.  
  • Document Release LeadRelease Lead The community member ultimately responsible for the Release. role rights. The person should:
    • Give the squad a clear vision/structure. 
    • Be the final arbiter of what gets included or punted from a release.
    • In the absence of a release lead, clearly delegate that responsibility to other roles.
  • Include the Theme Wrangler role in the Squad if major changes will come to themes (and not otherwise).
  • Publish major feature architecture early, to accommodate changes easily. 
  • Improve the release-process documentation to include communication with other teams. For example:
    • Notify Theme Wrangler to work on changes that impact Default themes.
    • Collaborate with Themes and Plugins teams to keep extenders aware of breaking changes and other docs they need to prepare for the release. At the moment, this consists mostly of an email to 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 developers and, lately, one to theme authors, 
  • We need to be better at sticking to feature deadlines for releases. Update Project philosophies to include exception criteria for Release delay. 
  • The “Source of Truth” post that Anne publishes for each release is super helpful. If we can make it a process to publish this on make/core, it will save a lot of duplicated effort. It will also give the Marketing/Media Relations, Docs and Training better information and more time to get the wider ecosystem prepared for new features.

How did the collaboration feel?

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

Forms response chart. Question title: How did collaborating on this project feel?. Number of responses: .

Would you like to be part of future release squads?

  • 11.1%: I haven’t been part of the squad but I would like to try in the future.
  • 66.7%: I have been part of a release squad and I will gladly repeat.
  • 0%: I have been part of the release squad but will not repeat in the near future
  • 0%: I haven’t been part of the squad but I would like to try in the future
  • 11.1%: Day job doesn’t allow for the consistent time.
  • 11.1%: I have been part of a release squad and I will repeat, However perhaps in some time. 

What is your feedback on the current release squad size?

Forms response chart. Question title: What is your feedback on the current release squad size?. Number of responses: .

Takeaways and next steps

  • Several very long-term contributors mentioned that the current process for adding new editor features diverges significantly from traditional processes, and they found it hard to influence direction before those features incurred predictable consequences.
  • The fixes they propose echo those of other respondents:
    • More frequent syncing of the editor package to the wordpress-dev repo
    • More posts on Make that highlight important discussions on the Gutenberg repo
  • Contributors across the board would like to see more communication with extenders about new features and breaking changes.
  • Contributors value the Source of Truth documentation that comes from Anne McCarthy and have come to rely on it.
  • That said, they would like information about new features even more often, earlier, and in more media.
  • Contributors would also like more information on the roles of release leads (not just coordinators) and what decisions the lead makes versus what decisions are the purview of the tech leads.
  • Finally, respondents would like to see updates in the Handbook that specify what issues can legitimately delay a release and that a squad will follow the principle that deadlines are not arbitrary the rest of the time.

Props to @priethor,@marybaum and @akshayar for compiling retrospective responses & reviewing this post. 

#6-5, #retrospective

Aaron Jorbin 8:54 pm on May 2, 2024
Tags: 6-5, , ,   

WordPress 6.5.3 RC1 is now available

WordPress 6.5.3 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.5.3-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

6.5.3 RC1 features 11 fixes in Core as well as 8 fixes for the 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.

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:

The following block editor issues from 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/ are fixed:

  • #60489 – Layout: Skip outputting base layout rules that reference content or wide sizes if no layout sizes exist
  • #60620 – Fix inserter pattern pagination focus loss
  • #60608 – Fix static posts page setting resolved template
  • #60641 – Font Library: Fix modal scrollbar
  • #60661 – Interactivity 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.: Allow multiple event handlers for the same type with data-wp-on.
  • #60668 – Layout: Always add semantic classes
  • #60845 – List View: Fix stuck dragging mode in UIUI User interface in Firefox when dealing with deeply nested lists
  • #60764 – Don’t output base flow and constrained layout rules on themes without 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.

What’s next?

The dev-reviewed workflow (double committer sign-off) is now in effect when making changes to the 6.5 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, May 7th, 2024. Please note that this date can change depending on possible issues after RC1 is released. 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-5-release-leads channel.

A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!

Thanks to @grantmkin, @hellofromtonya for pre-publication review and @davidbaumwald @desrosj for RC package assistance.

#6-5, #6-5-x, #minor-releases, #releases

Joe McGill 9:52 pm on April 23, 2024
Tags: 6-5, , ,   

WordPress 6.5 performance improvements

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

WordPress 6.5, “Regina” is the first major version of WordPress released in 2024. This release includes several important performance enhancements impacting the user experience for site visitors, along with remarkable improvements to editor performance. Importantly, WordPress 6.5 delivers site performance that is similar, if not superior to previous versions, despite the addition of many significant new features.

In our analysis of the Twenty Twenty-four theme, we observed modest changes in website front-end performance. The median LCP time shows a slight 0.81% decline in non-translated tests, with a 0.95% improvement in translated tests. Similarly, the Twenty Twenty-one theme exhibits a 1.13% drop in median LCP times in non-translated tests, yet showcases a notable 4.50% improvement in translated tests. Further details on the methodology behind these measurements are provided later in this article.

Key improvements

Improved performance for translated sites

This version of WordPress includes a new localization system that loads translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. files more quickly, and introduces support for providing translation files as native PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher files. As the merge announcement summarizes, these enhancements are expected to bring a 23.5% improvement in loading time and 41.4% reduction in memory consumption for translations.

A significantly faster editing experience

A major focus of this release was improving performance while editing your site. WordPress 6.5 delivers 5x faster typing processing, 2x faster editor loading, and a 60% reduction in pattern loading, based on measurements collected as part of the overall effort documented in this GitHub issue.

Improvements for registering 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. variations

The WordPress block editing system allows blocks to be registered with a set of block variations, which makes it easy to define different versions of a block without needing to duplicate the whole block. This version of WordPress adds support for registering block variations only when used, avoiding costly processing when this data is unnecessary, which makes server rendering 5% faster.

Support for AVIF image format

WordPress 6.5 supports AVIF, a modern image format that offers significant improvements in image quality and compression over previous formats like JPEG, PNG, and even WebP.  AVIF images can be up to 50% smaller than JPEGs while maintaining the same image quality.

Additional performance focused changes

In total, there were 20 performance related improvements included in this release, split evenly between new enhancements (10) 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 (10).

How release performance is measured

The performance measurements used for the overview are based on benchmarks1 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 of the homepage of the Twenty Twenty-one, Twenty Twenty-three, and Twenty Twenty-four themes with and without translations installed, comparing WordPress 6.5 with WordPress 6.4.3 (the latest version of WP 6.4 available when 6.5 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

No translation (en_EN):

Translation (it_IT):

Follow up from this release

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. 

You can also follow progress on other performance-related work being planned for the WordPress 6.6 release in Trac and in the Gutenberg repository. A full list of the Performance Team’s priorities for the year is available on the 2024 Roadmap page in the team’s handbook. Come join us in making WordPress as performant as possible.

Props to @flixos90, @peterwilson, @adamsilverstein, @annezazu, and @jorbin for contributing to this post.

  1.  Benchmark measurements use lab data to gather performance metrics under controlled conditions and may not reflect the way the software performs in the field. For more on the differences between Lab and Field data, see this article. ↩︎

#6-5, #core, #core-performance, #performance

Aaron Jorbin 5:28 pm on April 15, 2024
Tags: 6-5, 6-5-release-leads, ,   

WordPress 6.5.3: An upcoming maintenance release

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

  • 2 May 2024 – 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.
  • 7 May 2024 – 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.5.3 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.5.x Editor Tasks board. If you lack bug gardening capabilities and have a ticket or issue you wish to highlight for 6.5.3, 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.5 cycle.

Get involved with 6.5.3

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.5 in need of translation.

General coordination for the release will happen in the #6-5-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 @grantmkin and myself (@jorbin).

Thank you to @grantmkin for pre-publication review.

#6-5, #6-5-x

Héctor Prieto 6:07 pm on April 12, 2024
Tags: 6-5, , ,   

WordPress 6.5 Release Retrospective

Congratulations to all who helped make WordPress 6.5! Now that it has launched, I invite you 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 April 26th, 2024. Shortly thereafter, you’ll see a follow-up post with collected, anonymized results.

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

Props to @akshayar and @marybaum for the peer review

#6-5 #retrospective

#core, #release-process

Aaron Jorbin 10:01 pm on April 9, 2024
Tags: 6-5,   

What Happened to WordPress 6.5.1?

Observant folks will notice that the first 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. for WordPress 6.5 is 6.5.2 instead of 6.5.1. This is due to an error with the initial package. When the 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.) for 6.5.1 was created on the WordPress build server, it was created from a previous revision of the 6.5 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".. As tags are treated as immutable, this meant that WordPress 6.5.1 could not be released.

As a follow-up, the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team will work with 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/ Systems team and update respective documentation as needed to ensure that everything is done to prevent similar situations.

Thanks to @audrasjb, @davidbaumwald, and @jeffpaul for pre-publication review.

#6-5, #6-5-x

Sarah Norris 10:44 pm on April 3, 2024
Tags: 6-5, , 6-6-release-squad, ,   

Summary, Dev Chat, April 3, 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.

Announcements

WordPress 6.5 “Regina” was released yesterday! Thank you to everyone who worked on, tested, and supported this release 🎉

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

We are officially in the WordPress 6.6 release cycle. @priethor published this WordPress 6.6 Planning Proposal & Call for Volunteers post last week. Please take note of the following callouts on that post:

  • Please leave your feedback about the schedule and release squad size in the comments by April 7th.
  • If you are interested in participating in WordPress 6.6’s release squad as a lead or as a cohort, please show interest in the comments, specifying the role and the type of involvement (lead/cohort).

@colorful-tones and @fabiankaegy will be covering and merging TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress./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/ Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. for 6.6, and if anyone has any recommendations to streamline things for overall Triage to make lives easier, then please reach out to them.

For 6.6, we discussed considering not having a sticky post for the 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. scrub schedule and instead ensuring the schedule is linked at the top of the main release page.

We also discussed 6.5.1, and noted that @jorbin published a post: Initial Bug Scrub for 6.5.1 for tomorrow. @fabiankaegy mentioned that the editor team have created this new board in GitHub to track any editor-related issues that may be candidates for a point 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.. Currently, there are 5 tickets with the backport to wp minor release label.

We also already have quite a few tickets targeted for the 6.5.1 milestone, so any eyes before the initial bug scrub will likely help that be more efficient.

Next Gutenberg release: 18.1

The next Gutenberg release will be 18.1, scheduled for release on April 10, and will include these issues.

Discussion

We began by discussing any potential follow-up actions and reflections following the recent 6.5 release. @fabiankaegy asked about starting a conversation about possibly evolving how we approach the field guideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. and dev notesdev 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. in future releases.

@jorbin has previously opened a related proposal to updating the field guide. We discussed where the most appropriate place was to start a conversation like this, and whether it sits more with CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., Docs, or Project. As it touches on many different areas and how we do things within software release cycles, then it seems to fit more into the Core team’s scope.

@audrasjb suggested this may be good to discuss in the future #6-6-release-squad Slack channel so maybe the squad could discuss it in the open with the future Docs Leads and come up with a formal proposal for 6.6 on Make/Core.

@joemcgill also proposed arranging another release retrospective post to collect feedback about the release while it’s still fresh in people’s minds. @chanthaboune mentioned being able to do this in any way that works for folks. For 6.4, we collected the data in an anonymized format and then that data was shared on make/core, and we discussed potentially following a similar approach for 6.5.

Highlighted posts

The full list of posts from the last week in Core can be read on the agenda at this link.

Open floor

We started by highlighting this PR for the WP Importer in support of the Font Library from @mmaattiiaass.

@kkmuffme mentioned that they’re looking for reviews on several PRs, listed in this message and this message.

Two additional issues that were raised in the agenda comments were:

  • https://github.com/WordPress/gutenberg/issues/15117 – “the excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. 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., that impacts all plugins incl. WooCommerce”
  • https://core.trac.wordpress.org/ticket/59270 – “adding border setting to columns”

This issue was highlighted: Responsive previewing and device-specific editing. Nolan asked what the best way was to make a decision on the issue, as this has been open for 4 years. @annezazu replied with:

I understand that’s an important issue — it has been for a long time! I know some designers have recently chimed in there and there’s some momentum gathering. The best thing to do at this point is to be specific and keep sharing what would be helpful. Beyond that, the main blockerblocker A bug which is so severe that it blocks a release. is finding solid design solutions and finding specific/targeted ways to implement as anything that is implemented has to be maintained.

Also, @webcommsat highlighted a forthcoming contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. which is looking for core input and people to join. More info on here on Slack.

Props to @joemcgill for reviewing.

#6-5, #6-6, #dev-chat, #summary

Aaron Jorbin 7:06 pm on April 2, 2024
Tags: 6-5, ,   

Initial Bug Scrub for 6.5.1

There is no specific target date for WordPress 6.5.1 yet. However, we can start ensuring that all the correct bugs are targeted for it and that work progresses towards fixing them.

To assist with preparation for 6.5.1, an initial scrub will be held at Thursday, April 4, 2024 at 18:00 UTC in the #core 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/. channel.

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

#6-5, #6-5-x, #bug-scrub