Author Archives: Aaron Jorbin

Aaron Jorbin 5:28 pm on April 15, 2024
Tags: , 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

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

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

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

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

Aaron Jorbin 8:26 pm on January 25, 2024
Tags: , , ,   

WordPress 6.4.3 RC1 is now available

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

What’s in this release candidate?

6.4.3 RC1 features 5 fixes in Core as well as 16 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:

What’s next?

The dev-reviewed workflow (double committer sign-off) is now in effect when making changes to the 6.4 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, Janury 30th, 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-4-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 @joemcgill for pre-publication review

#6-4, #6-4-x, #minor-releases, #releases

Aaron Jorbin 7:31 pm on January 16, 2024
Tags: , , ,   

6.4.3: An upcoming maintenance release

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

  • 25 January 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.
  • 30 January 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. Currently, four bug fixes have been merged into the 6.4 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". with seven additional tickets intended for this release. If you have a ticketticket Created for both bug reports and feature development on the bug tracker. that you think should be considered, please put it in the milestone or if you lack bug gardening capabilities, 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.4 cycle.

Final note: Some default themes are also receiving updates, but these will be happening separately even though the tickets are in the 6.4.3 milestone. See #60267 for more information. Update: The theme updates have been released

Get involved with 6.4.3

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

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

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

Thank you to @fabiankaegy, @annezazu, @hellofromtonya for pre-publication review.

#6-4, #maintenance

Aaron Jorbin 7:01 pm on December 13, 2023
Tags: ,   

6.4.3 Maintenance Release Bug Scrub

There is no specific target date for WordPress 6.4.3 yet, but that doesn’t mean work can’t be done to ensure that all the correct bugs are targeted for it and that work progresses towards fixing them. To assist with this, some initial scrubs will be held at the following times:

All Scrubs will take place in the #core room in Slack. The first scrub will be going through tickets in awaiting review that may belong in the 6.4.3 milestone with the goal of triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and the second scrub will focus on tickets in the 6.4.3 milestone.

Anyone else that wishes to host a scrub for 6.4.3 is welcome. Please comment here with the time you would like to hold one and I will edit the post to include it. As the documentation on leading bug scrubs states:

Leading a Bug Scrub is something any interested community member can do.

Thanks to @joemcgill for prepublication review

#6-4, #bug-scrub

Aaron Jorbin 8:37 pm on November 10, 2023
Tags:   

An update to the core commit message format

WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. uses a standard commit message format to make it easier for people and machines to read and understand the changes that happen. The documentation on commit messages notes that:

We write commit messages for multiple audiences: contemporaries (fellow core developers, 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, anybody following along with core development), future contributors, and computers. Good commit messages serve each of these audiences well. They describe the what and the why of the changeset; the how is described by the diff itself.

To assist in this endeavor, the format for commit messages has been updated to take into account 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. and follow up commits. The documentation around commit messages has been updated to now include specific sections for follow up, merges, and reviewed by.

A few additional updates have been made to the commit message documentation:

  1. It is now strongly discouraged to use the word props outside of the line where contributors to a commit are recognized as it can lead to false positives in the tools that collect props. When referencing properties, please avoid the short form props in favor of the full word.
  2. The props line should only include the word props, 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/ usernames and punctuation for the same reason as above. Avoid free-form props. When those are used, please mention them in the message such as “Special thanks to the jQuery team for assisting.”
  3. The words backport and backports must not be used in commit messages. Backporting is the task of moving a commit from trunk to a specific numbered 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". and the format described above is to be used then. This is to avoid confusion when reading commit messages.

Note: This update is strictly for commits to WordPress Core SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase., however others are welcome to use this standard.

Thanks to @desrosj for pre-publication review.

#commit

Aaron Jorbin 8:31 pm on October 30, 2023  

Call for 6.4.x Release Managers

WordPress 6.4.0 remains on schedule to be released 7 November 2023. Afterward, work will need to be done to release one or more maintenance or minor releases. While the work of 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. team includes people filling approximately 16 different positions, maintenance release teams generally are considerably smaller. 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. managers are responsible for:

  • Triaging bugs in coordination with committers and component maintainers.
  • Drafting announcements for the release.
  • Preparing for and running release day activities.
  • Updating the documentation on minor releases so that it gets better each time.

Members of the 6.4 release cohort are encouraged to stay on as release managers for maintenance releases, but it is not required to have been on a major release squad in order to be on a minor release team.

If you are interested in volunteering to be a release manager for the 6.4 maintenance releases, please comment here.

Thanks to @jeffpaul, @joemcgill, and @hellofromtonya for reviewing this post before publication.

Aaron Jorbin 4:56 pm on August 31, 2023  

Proposal: An update to the Field Guide

This proposal comes out of an ad-hoc session at the WordPress Community Summit. This session grew out of discussions during the session on backward compatibility in 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/ where it was noticed that some WordPress changes are easily missed by the extendors of WordPress and WordPress site builders.

Background

The Field Guides in WordPress started in 3.4 and have been consistently published since WordPress 4.1. In this time, they have grown in length due to an increase in both the number of 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. and the number of changes in each version.

Longer posts can be more difficult to read to completion and this can cause important information to be missed. Additionally, as much of the information is linked to rather than included in the post it takes effort to truly understand the breadth of changes in a WordPress release. All of the information that is published is valuable to the WordPress community, so discouraging the publishing of content would be antithetical to the goal of informing and helping the WordPress community and is not something that is desired.

Proposal

The first part of this proposal is to continue publishing the existing 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. on this site (make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.) but adjust the target for publishing it to the final scheduled betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.. Currently, the target is to publish the Field Guide at the same time as RC1. This doesn’t change the amount of work for the release team, but it does move the target up by approximately one week. Publishing this earlier will give some additional time to update documentation, encourage testing from the community, and also allow for time to prepare for part two of this proposal.

The second part is to start publishing a simplified Field Guide to the WordPress Developer Blog. The audience for this guide is primarily two groups: Extenders of WordPress such as 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 and theme authors and Developers building custom sites. This simplified guide will focus on the following things:

  • Large features that developers would want to tie into
  • Changes with a high potential of causing breakage
  • Features the core team wants developers to start using right away as the use of them will benefit WordPress end users.

As an example, a hyper-focused Field Guide for WordPress 6.3 could have highlighted the new command palate (a large feature that developers would want to tie into), Async/Defer in the script loader (a new feature that when developers start using, WordPress end users will benefit), and the post editor being iframed (a change with a higher potential of causing breakage).

The target length of this Field Guide should be 800-1000 words and it should link to but not embed any other documentation such as dev notes. The target will be to publish this post within one week of RC1. The same process for all content published on the developer blogblog (versus network, site) will be followed and the release documentation lead(s) or their designee will be expected to work with the WordPress Developer Blog team in the #core-dev-blog channel and the developer blog content GitHub repository to coordinate the content and publish date.

Provide feedback by 15 September 2023

This proposal is one step, but not necessarily the only step, at improving communication around WordPress releases and making it easier for WordPress updates to instill confidence. Feedback will be accepted until 15 September 2023

Thanks to @annezazu, @webcommsat, @ndiego, and @jeffpaul for feedback on this proposal prior to publication.

Aaron Jorbin 2:51 pm on August 30, 2023
Tags: ,   

X-post: Community Summit Discussion Notes: PHP version support

X-comment from +make.wordpress.org/summit: Comment on Community Summit Discussion Notes: PHP version support