WordPress 5.8.2 RC 1

WordPress 5.8.2 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). 1 (RC1) is available for testing!

Some ways you can help testing WordPress 5.8.2 RC1:

  • 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 RC release, select the 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. channel and the Nightlies stream. This will be 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-5.8.2-RC1.zip
  • Directly download the 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./RC version (https://wordpress.org/wordpress-5.8.2-RC1.zip)

What’s in this release candidate?

5.8.2 Release Candidate 1 features 3 bug fixes on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

The following core tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

  • #54207 – ca-bundle.crt contains expired certificate DST Root CA X3
  • #54129 – Undefined index posts_per_page in ajax-actions.php
  • #54323 – Too few arguments for function (closure)

What’s next?

The dev-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) is now in effect when making any changes to the 5.8 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 per the proposed WordPress 5.8.2 schedule, the final release is expected on Wednesday, November 10, 2021. 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/. #5-8-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!

The 5.8.2 release is being led by @desrosj and @circlecube.

Props @circlecube and @audrasjb for peer review.

#5-8, #5-8-2, #minor-releases, #releases

WordPress 5.8.2 Deferred

The WordPress 5.8.x release schedule calls for 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). this week and a 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. next week. However, the scheduling for these 5.8.x releases will be changed.

The 5.8.2 release dates as previously planned will be skipped and rescheduled to the “if necessary” 5.8.3 schedule as follows:

5.8.2 (updated)

  • RC: Tuesday November 2, 2021
  • Final release: Wednesday, November 10, 2021

This deferral was determined because currently there are no commit candidates. Plus, many commits still need a lot of work to merge, or are potentially too impactful and therefore belong in 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. instead.

Release Coordination

Because the 5.8.x releases are part of 5.8 by extension, all coordination and conversation related to the 5.8.x releases are held in the #5-8-release-leads 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.

Do you want to see some tickets included in the next release? Check the 5.8.2 milestone: provide feedback on tickets, test existing fixes, or even submit a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to help move things along!

Props @desrosj & @tobifjellner for peer review.

#5-8, #5-8-2, #5-8-3, #5-8-x

WordPress 5.8.2+ Release Schedule

Thanks to everyone that helped release 5.8.1 on September 9th! It’s time to look ahead to 5.8.2, and other 5.8.x releases (if necessary).

Like the 5.8.1 release, these releases are following the strategy of having a consistent minor release squad for all 5.8.x releases.

5.8.2

The following schedule is proposed for a 5.8.2 release:

  • RC: Tuesday, October 5, 2021
  • Final release: Tuesday, October 12, 2021

As of the publish date of this post, 19 open tickets are currently in the 5.8.2 milestone for consideration. Please head over and check out that list to help contribute to the release.

5.8.3 (if necessary)

For the 5.8.x release cycle, a 5.8.3 release will be pursued only if necessary. Below is the proposed schedule for 5.8.3:

  • RC: Tuesday November 2, 2021
  • Final release: Wednesday, November 10, 2021

These dates also take into account the 5.9 release cycle, which will be approaching the first 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. release at this time.

Release coordination

Because the 5.8.x releases are part of 5.8 by extension, all coordination and conversation related to the 5.8.x releases are held in the #5-8-release-leads 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. This channel will be archived when WordPress 5.9 is released.

Props @desrosj & @audrasjb for peer review.

#5-8, #5-8-1, #5-8-2, #5-8-3, #5-8-x

Dev Chat Agenda for Sept 15, 2021

Here is the agenda for this week’s developer meeting to occur at September 15, 2021, at 20:00 UTC.

Blogblog (versus network, site) Post Highlights and announcements

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-8, #5-9, #agenda, #core, #dev-chat

WordPress 5.8.1 RC 1

WordPress 5.8.1 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). 1 (RC1) is available for testing!

Some ways you can help testing WordPress 5.8.1 RC1:

  • 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 RC release, select the 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. channel and the Nightlies stream. This will be 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-5.8.1-RC1.zip
  • Directly download the 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./RC version (https://wordpress.org/wordpress-5.8.1-RC1.zip)

What’s in this release candidate?

5.8.1 Release Candidate 1 features 41 bug fixes on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., as well as 20 bug 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 core tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:

  • #52818 – Ordering metaboxes broken in WP 5.7
  • #53556 – Add a new template-editing 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.) to the Theme 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.
  • #53562 – Widgets Editor 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. doesn’t load with E2E tests + 0ms Animations
  • #53609 – Responsive widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. block embeds not showing in the customizer
  • #53616 – Registered block styles should only be rendered when the block exists on a page
  • #53641 – Can not configure image widget (and others) in widget accessability mode
  • #53654 – Menus: Hide bulk-select options when no menus exist
  • #53667 – Support wp_editor_set_quality for both loaded and saved mime_types
  • #53668 – Generated images for one file can be overwritten by another with the same name when mapping mime types for generated images
  • #53679 – The media library looks broken on mobile
  • #53680 – Correct inline documentation about IMAGETYPE_WEBP and IMG_WEBP
  • #53696 – wp_add_iframed_editor_assets_html() not checking for block editor
  • #53697 – 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. – Border settings not displaying for Button Block
  • #53702 – Four css files removed between 5.7.x and 5.8 were not included in $_old_files
  • #53713 – Bounce underscore.js version in script-loader
  • #53714 – Bounce jquery.form.js version in script-loader
  • #53715 – Bounce hoverIntent.js version in script-loader
  • #53716 – The “/” missing at the end of image tag
  • #53719grunt clean:css does not clean the css/dist folder
  • #53738 – Broken loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. in WP_Theme_JSON_Resolver
  • #53752 – Twenty Ten: Block patterns file causes error in child themes
  • #53757 – Widget editor calls get_block_categories() with incorrect arg type
  • #53762 – Replace the remaining references to wp.editor with wp.oldEditor
  • #53769 – Bundled themes: block-patterns.php file should use get_template_directory_uri instead of get_stylesheet_directory_uri
  • #53773 – /wp-adminadmin (and super admin)/includes/ajax-actions.php file line 3006 is creating divide by zero error
  • #53777 – Bump bundled theme versions for
  • #53799 – Remove version-controlled files check from Test Old Branches workflow
  • #53803 – Customizer: Radio button on background image position selector visible on focus
  • #53820 – Build doesn’t support Docker Compose V2
  • #53827 – Increase number of media items displayed when clicking button to “Load More”
  • #53830 – Default filters try to create nonce during installation before options table exists
  • #53833 – ‘Replace image’ Media Modal is missing select fields under filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. media due to css issues
  • #53877 – Menus: Selected display locations for new menus aren’t saved
  • #53898 – Duplicated 404 templates in the TemplatePanel
  • #53922Docblockdocblock (phpdoc, xref, inline docs) in get_block_editor_settings function
  • #53932 – Media grid view doesn’t show all media elements
  • #53936 – Output of serialize_block_attributes does not match equivalent 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/ function
  • #53955 – Fix and improve the docs for the image_editor_output_format filter
  • #54030 – Pressing esc in Widgets Editor closes panel in customizer
  • #54036 – PclZip throwing errors on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8 – previously merged patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. is incomplete
  • #54052 – Block editor package updates for 5.8.1

The following block editor issues from GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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:

  • PR33384 – Fix API docs for data reference guides
  • PR33381 – Docs: use markdown headings instead of links for API declarations
  • PR33498 – Docs: Run Prettier after updating API in documentation
  • PR33549 – Use tabs instead of spaces in block transform doc example
  • PR30617 – Fix metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. reordering
  • PR32083 – Block editor: move layout styles to document head (instead of rendering inline)
  • PR33814 – Widgets: Allow HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. tags in description
  • PR33457 – Editor: Set ‘hide_empty’ for the most used terms query
  • PR33482 – Update widget editor help links to point to the new support article
  • PR33621 – Fixed that the block is selected instead of the title when using the select all shortcut.
  • PR33699 – Writing flow: select all: remove early return for post title
  • PR33618 – Call onChangeSectionExpanded conditionally
  • PR33679 – FontSizePicker: Use number values when the initial value is a number
  • PR33739 – Fix justification for button block when selected
  • PR33771 – Add error boundaries to widget screens
  • PR33802 – Fix insertion point in Widgets editors
  • PR34280 – Default batch processor: Respect the batch endpoint’s maxItems
  • PR34314 – Fix button block focus trap after a URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org has been added
  • PR34076 – Text for dropdown fields within legacy widgets in the Customizer is off centered
  • PR32935 – Add a SearchControl component and reuse accross the UIUI User interface(class change in tests)

What’s next?

The dev-reviewed workflow (double committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. sign-off) is now in effect when making any changes to the 5.8 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 per the proposed WordPress 5.8.1 schedule, the final release is expected on Wednesday, September 8, 2021. 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/. #5-8-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!

The 5.8.1 release is being led by @desrosj and @circlecube.

Props @webcommsat and @desrosj for peer review.

#5-8, #5-8-1, #minor-releases, #releases

A Week in Core – August 2, 2021

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between July 26 and August 26, 2021.

  • 24 commits
  • 24 contributors
  • 85 tickets created
  • 7 tickets reopened
  • 58 tickets closed

Pending the appointment of the WordPress 5.9 team, a number of tickets have been fixed, waiting for the next 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.(s). No release date is yet available for 5.8.1, but it should arrive in a couple of weeks.

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Build/Test Tools

  • Post a message to #core 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/. when a workflow fails – #52644
  • Remove the check for changes to version-controlled files in the Test Old 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". workflow – #53799
  • Revert the test and coding standards changes in [51511]#52644
  • Split packages and blocks to their webpack configs – #53690

Bundled Themes

  • Remove extra trailing spaces from translatable strings in 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. patterns – #53774

Coding Standards

  • Apply some alignment fixes from composer format#53729
  • Coding Standards: Fix typo in the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. function name for handling the password reset button – #53359
  • Code Modernization: Silence the deprecation warning for missing return type in JsonSerializable_Object#53635
  • Add missing documentation for the minute parameter of WP_Query#53399

Documentation

  • Clarify the @return value for WP_Filesystem_Base::getnumchmodfromh()#53399
  • Correct @return type for WP_Filesystem_Base::getnumchmodfromh()#53793
  • Correct the documented allowed range for the minute and second parameters of WP_Query#53399
  • Document the $wpdb global in WP_Debug_Data::get_mysql_var()#53845
  • Fix typo in the WP_Upgrader::install_package() description – #53399
  • Replace $this in hook param docs with more appropriate names – #53457

Networks and Sites

  • Replace two remaining occurrences of “blogblog (versus network, site)” with “site” in user-facing strings – #53775

Site Health

  • Add some more MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. information to the Site Health Info screen – #53845

Site Health

  • Standardise site health check status message punctuation – #53594

TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.

  • Pass correct default value for $post_id to wp_terms_checklist() in the posts list table – #43639

Themes

  • Add “Template Editing” to the list of WordPress theme features – #53556, #meta5802
  • Make sure get_theme_mods() always returns an array – #51423

Upgrade/Install

  • Add files for 5.8 to the $_old_files list that were missed – #53702
  • Avoid creating nonce during installation – #53830
  • Skip any node_modules directories when removing Genericons example.html files on update – #52765
  • Store correct result when bulk updating plugins or themes – #53002

Props

Thanks to the 24 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (3), @desrosj (3), @audrasjb (3), @jrf (2), @johnbillion (2), @donmhico (2), @mukesh27 (2), @afragen (2), @pbiron (1), @ocean90 (1), @WFMattR (1), @aristath (1), @youknowriad (1), @poena (1), @pwtyler (1), @tareiking (1), @bobbingwide (1), @zodiac1978 (1), @xknown (1), @hellofromTonya (1), @sanketchodavadiya (1), @swissspidy (1), @schlessera (1), and @ankitmaru (1).

Congrats and welcome to our 2 new contributors of the week! @pwtyler and @tareiking ♥️

Core committers: @sergeybiryukov (15), @desrosj (5) and @johnbillion (4).

#5-8, #meta5802, #week-in-core

Devchat summary, July 28, 2021

A week after the release of WordPress 5.8, @desrosj led a well attended but quick chat on this agenda.

Highlighted blogblog (versus network, site) posts

Jonathan drew the group’s attention to these posts:

He also added a late post of his own:

If you’d like to help with 5.8.xx minor releases, leave a comment on that post.

To-do items on 5.8

Moving on, @desrosj opened one last review of the 5.8 release and asked the group for retrospective comments and other feedback.

In reply, @chanthaboune said she’d likely have her retrospective up later in the day. And she said @matveb will shortly have some thoughts about features to target for 5.9.

Remember, also, that trunk is open now, so if you’re a 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., keep committing whatever you feel is ready! (Ed. note: Plus, we’re also in alpha for 5.9, so whether you’re a committer or not, if you’re passionate about bringing a new feature into CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., now is the time to do what it takes to land it.)

Component maintainers

@sergeybiryukov checked in with news on Build/Test, where ticketticket Created for both bug reports and feature development on the bug tracker. #53363 has details on some 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 and updated naming to follow established conventions.

On U[grade/Install, Sergey added a second plug for his feedback request on the updater proof of concept highlighted above.

Open Floor

Above, in highlighted posts, you probably noticed that @desrosj asked for comments on his minor-releases post if you want to help with the 5.8.x minors. He actually added that suggestion in Open Floor.

#5-8, #core, #dev-chat, #summary

WordPress 5.8 ‘Tatum’ Retrospective

A lot of things changed with the way that the WordPress 5.8 release was managed. A retrospective is always a good idea after a project, but in this case I wanted to be sure I cataloged the big changes for anyone who felt that it was different, but couldn’t quite put words to it. I originally shared this with the release team in Slack.

  • The teamwork had a different feeling. Instead of having buddies or cohorts of learning contributors (roughly one-to-one), we put the squad in a public channel to coordinate the work (one-to-many).
  • The release process had a different feeling. We made feature freeze independent of any other type of milestone and also are trying to be more focused about what work is done in each phase.
  • The included features had a different feeling. Instead of flipping the switch on a massive change for everyone, full site editing is being being shipped in smaller, more manageable chunks so it’s easier to catch up and we can iterate as we go.
  • The environment is different. We’ve all been struggling through this pandemic and being isolated from those we care for. Whether we recognize it or not, that has a profound impact on what we choose to do with our spare time, how we are able to meet others where they are, and whether we “grow through” or “bounce back” from hurdles that stand in our way.

Anyone is welcome to participate in this retro, so please take a few moments to fill in the form or leave public feedback in the comments below. It is not anonymous in case I need some clarification, but your email address will not be kept. The form will be open until August 15, 2021.

Thank you everyone for your contribution to this release, and thanks in advance for taking the time to help make future releases even better!

#5-8, #retrospective

Consistent minor release squad leaders for each major branch: Trial run retrospective and 5.8.x releases

During the 5.8 release cycle, a Release LeadRelease Lead The community member ultimately responsible for the Release. and Release Deputy was named for all 5.7.x releases in a trial run. The experiment was an attempt to address several pain points that made executing minor releases needlessly difficult. Each of the pain points of the minor release cycle were expanded in detail in the original post.

For the 5.7.x releases, @peterwilsoncc and @audrasjb were named as Release Lead and Release Deputy respectively. In the months between the 5.7 and 5.8 releases, they successfully planned and released 2 minor 5.7.x versions with an average of 4.5 weeks between each. The gap between the final 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. (5.7.2) and 5.8 was 9.7 weeks.

Feedback

In an effort to evaluate how this process went, they were asked for some answers to a handful of questions. Here is some collected feedback from @peterwilsoncc on how the process went.

What went well?

Generally I thought the experiment was successful and it was good to be able to concentrate (and only be expected to concentrate) on the minor releases rather than try to track both major and minor. More specifically:

  • Getting a few more people in the AEST timezone involved than usual helped with coordination.
  • Starting early my time for releases was good for the .1 version as it went longer than expected.
  • Probably should have asked for author rather than contributor permission on w.org/news so I could actually publish the posts I prepared.
  • Having scripts prepped a day in advance was great at reducing stress and allowed for dry-runs (excluding commit).

What went poorly?

  • Night owls or not, I don’t think it was great having me in APAC and @audrasjb in EU working as team leads, everything that was good about release times for me was exactly the reverse for @audrasjb (and @desrosj but to a lesser extent).
  • Better prep on the .1 release could have shortened the time for committing and moving on to the release party.
  • Needed to pull in a couple of people on the release day for the .1 release.
  • Finding someone with mission control access is not easy (especially in timezone). The list of those with permissions is really out of date, and some probably don’t need release permission any more.
  • I didn’t delegate some of the adminadmin (and super admin) stuff well and ended up doing a fair bit at the last minute as a result (on me for not asking).

What did you learn?

  • How to release 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/ packages, although doing so on my first production commits to the repository was a little brave.
  • Depending on the number of security backports, and how far back they need to go, release day for a minor can be busier than a major.
  • Process page in the handbook is quite out of date: updated a few steps after each of the two releases.

What support did you receive?

A lot.

  • @gziolo and @isabel_brison helped a great deal with getting the Gutenberg release process down, especially @gziolo by updating the undocumented steps as I asked questions.
  • @audrasjb, @desrosj and @whyisjake with release processes, both in advance and on the day.
  • Code review of shell scripts to attempt to speed up the process.
  • @dd32 with release day stuff, including catching quite a few things I was unaware of on the day.


What support could you have used?

Needed a lot more support from editor team with some planning tasks. The team was consumed with 5.8 and Full Site Editing, so they did not have much time to spare.

What were some responsibilities or tasks you had to take care of that you did not anticipate?

  • Expected I’d need to prep some release day scripts, but didn’t realize how many until I started doing them. Again, probably would have been helped by better delegation
  • Didn’t realize I’d need to do NPM releases at the start but figured it out well before the actual release

Anything else you feel is worth sharing?

Generally I think it went well and was successful.

Continuing the trial in 5.8.x releases

Because the experiment was generally successful, it will be repeated in 5.8.x releases. To reiterate the ideal criteria that was listed in the original proposal, the two contributors serving as release lead and release deputy will be responsible for:

  • Publishing timelines and plans for each minor release.
  • Executing these plans through release day.
  • Coordinating with the Security Team lead to improve the flow of fixes from the team to users.
  • Assembling and requesting help from other volunteers for each release as deemed necessary (docs, test, specific focus areas, etc.).

Ideally, one of these two contributors has a technical background (with the abilities to identify, confirm, test, and approve 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 and changes), and the other has a project manager or coordinator background (with the abilities to create release timelines, coordinate contributors, and help unblock efforts).

One additional (potentially optional) criteria would be that either the lead or deputy be a part of the previous 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.’s squad, or be very familiar with the changes that were introduced in that major release. This would further increase the speed at which the minor releases are able to fix related bugs, as they are already “up to speed” on the changes.

In recent years, the gap between major releases has been, on average, 3 to 5 months. If necessary, contributors can 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.) in and out of the role should circumstances change and it becomes necessary.

If you’re interested in volunteering as a Release Lead or Release Deputy for the 5.8.x releases, please comment below!

Props @peterwilsoncc and @audrasjb for their great work during the 5.7.1 and 5.7.2 releases, and @chanthaboune for pre-publish review.

#5-7, #5-8

Dev Chat Agenda for July 28, 2021

Here is the agenda for this week’s developer meeting to occur at July 28, 2021 at 20:00 UTC.

Blogblog (versus network, site) Post Highlights

5.8 Review

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#5-8, #agenda, #core, #dev-chat