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

WordPress 5.7.1 RC 1

WordPress 5.7.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!

Here are two ways to test WordPress 5.7.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 (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. nightlies option)
  • Download the release candidate here (zip)

What’s in this release candidate?

5.7.1 Release Candidate 1 features 23 bug fixes on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., as well as 8 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.

Fixed Core tickets from TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.:

  • #52787 – Empty array for non-single post metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. breaks post save through REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.
  • #52822 – PHPMailer change in WordPress 5.7 breaks working sites
  • #52670Adminadmin (and super admin) pointer arrow border color darker than pointer content
  • #52713 – Reverse logic in wp_robots function and 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.
  • #52743 – Hardcoded SVG image URLs on WP 5.7 About screen
  • #52750 – WP 5.7 colors inconsistent in get_option( 'admin_color' ) since color contrast changes
  • #52751UIUI User interface issue on Privacy Policy Guide page
  • #52756 – Duplicate video URLs on WP 5.7 About screen
  • #52758 – 5.7 About Page: Image comparison doesn’t work on first load on some browsers
  • #52760 – Color not accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) for AA
  • #52764 – Classic editor adding empty tags in some media embed situations
  • #52768 – WordPress post URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org oEmbed rendering blocked by iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. lazy-loading
  • #52783 – Health Check mis-reports httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. functionality in certain situations
  • #52789 – Gallery layout block adds all media items when changing an image
  • #52816 – Post 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. style Twenty Seventeen has a border
  • #52826 – New wp_getimagesize() causing unexpected failures
  • #52834 – Reset password screen: improve buttons layout for better i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.
  • #52891 – Privacy: print screen reader text message
  • #52894 – The wp_sanitize_script_attributes function added in version 5.7 does not escape attributes in some cases
  • #52932 – Rest Api enum validation does not work correctly WordPress 5.7
  • #52961 – Add ‘object-position’ as an allowed CSSCSS Cascading Style Sheets. attribute
  • #52981 – Twenty Twenty-One: Update IE specific editor stylesheet

Fixed 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/:

  • PR30218 – Core Data: Use getAuthors for showCombobox
  • PR30524 – Editor: Revert (#27717) save editors value on change
  • PR30122 – Gallery: Set addToGallery prop to false when images don’t have IDs
  • PR29809 – Revert: Show empty paragraphs on fronted
  • PR29860 – Try: Fix gallery item clicking
  • PR29920 – Fix sibling block inserter displaying at end of block list
  • PR30125 – Block Editor: Ensure that uncategorized block types are properly handled
  • PR30243 – Add object-position to allowed inline style attributes list

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.7 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

As per the proposed WordPress 5.7.1 schedule, the final release is expected on Wednesday April 14, 2021 around 23:00 UTC. Please note that this date/time can change depending on possible issues after RC1 is released.

The 5.7.1 release is being lead by @peterwilsoncc and @audrasjb.

#5-7, #5-7-1, #minor-releases, #releases

WordPress 5.7.1 maintenance release schedule

Since the release of WordPress 5.7 a small number of bugs have been identified will benefit from a maintenance release.

Now, it’s time to merge these changes into a new WordPress 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. and to address the other tickets that have appeared in the meantime.

The following release schedule is being proposed:

  • 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).: Wednesday 7 April, 2021 around 23:00 UTC
  • Final release: Wednesday 14 April, 2021 around 23:00 UTC

At the time of writing, 18 tickets have been identified for the 5.7.1 milestone and 48 tickets submitted since March 9 are awaiting review.

In line with the trial for consistent minor release leads for each major 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 release leaders for the 5.7.x releases will be:

  • Release leadRelease Lead The community member ultimately responsible for the Release.: @peterwilsoncc
  • Deputy Lead: @audrasjb

#5-7, #5-7-1

A Week in Core – March 15, 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 March 8 and March 15, 2021.

  • 12 commits
  • 17 contributors
  • 63 tickets created
  • 9 tickets reopened
  • 70 tickets closed

There has been a low activity this week, as WordPress 5.7 was released last week.

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.

Code changes

Administration

  • AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility): Use a darker color for post dates in the Activity and Quick Draft dashboard widgets – #52760

Bundled Themes

  • Twenty Seventeen: Remove extra space around post editor – #52816

Site Health: Use a singular string in dashboard 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. if there is only one critical issue or recommendation – #52521
Docs: Correct unregister_block_style param for $block_name#52795

Coding Standards

  • Consistently format opendir() calls in get_plugins()#44250

Docs

Editor

  • Make blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. type aware of variations – #52688
  • Classic Editor: Make sure word count is hidden if JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. is disabled – #52662

Help/About

  • Run image comparison script after all assets have loaded – #52758
  • Use absolute URLs for inline images on About pages – #52743
  • Correct the WebM video URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org on About page – #52756

Props

Thanks to the 17 people who contributed to WordPress Core on Trac last week:

@audrasjb (4), @sabernhardt (3), @vladytimy (1), @jeremyfelt (1), @mihdan (1), @subrataemfluence (1), @TobiasBg (1), @Otshelnik-Fm (1), @gwwar (1), @timothyblynjacobs (1), @joyously (1), @kraftner (1), @hareesh-pillai (1), @Presskopp (1), @joseeyoast (1), @sergeybiryukov (1), and @mukesh27 (1).

Please join me to say welcome to our 2 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@Otshelnik-Fm and @joseeyoast

Core committers: @sergeybiryukov (6), @ryelle (2), @peterwilsoncc (2), @davidbaumwald (1), and @gziolo (1).
Shout out to @davidbaumwald for his first commit 🌟

Please note: it only includes commits with proper props attribution.

#5-7, #week-in-core

Dev Chat Agenda for March 10, 2021

Here is the agenda for this week’s meetings to occur at the following times: March 10, 2021 at 5:00 UTC and March 10, 2021 at 20:00 UTC.

Announcements

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.

In case you missed it, through the Field Guide for a full breakdown of everything you need to know about WordPress 5.7.

Blogblog (versus network, site) Post Highlights

Blog posts that need feedback

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 our standard list 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-7, #agenda, #dev-chat

A Week in Core – March 8, 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 March 1st and March 8, 2021.

  • 20 commits
  • 42 contributors
  • 64 tickets created
  • 9 tickets reopened
  • 81 tickets closed

You might have noticed that the activity on Core is still pretty high this week, as we are very close to release WordPress 5.7.

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.

Code changes

Build/Test Tools

  • Ensure the test_php_and_js_shortcode_attribute_regexes_match() test can run when testing using either the src or build directory – #51734
  • Pin SHA versions to the remaining 3rd party actions – #52625
  • Generalize the NPM test workflow – #52658
  • Add path detection when running 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/ Actions on pull_request#52667
  • Change the cancel-workflow-action version to a SHA value – #52625
  • Pin the welcome-action to a specific commit SHA – #52625

Bundled Themes

  • Twenty Twenty-One: Make text readable when dark background is selected for the Media & Text 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.#52702
  • Twenty Twenty-One: Correct inner container background color for Cover Blocks – #52676
  • Twenty Fifteen & Twenty Sixteen: Remove extra space around post editor – #52646

Docs

  • Add a @since note to wp_admin_bar_edit_menu() about the “View Post” link on Comments screen for a single post – #42366

Editor

  • Classic Editor: Make sure word count is hidden if JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. is disabled – #52662
  • Block Editor: Fix color support for dynamic blocks – #52709

Help/About

  • Clarify two strings – #52347
  • Clarify a string about lazy-loading iframes – #52347
  • Iterate on the 5.7 About Page – #52693

Roles/Caps

  • Return same result from current_user_can and user_can()#52076

Site Health

  • Do not store HTTPSHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. request error messages in an option – #52484

Upgrade/Install

  • Display version number on the “Update now” button on WordPress Updates screen – #52513
  • Upgrade/Install: Invalidate OPcache for version.php during update – #36455

XML-RPC

  • Pass an empty array to the xmlrpc_call action in methods that have no arguments – #52524

Props

Thanks to the 42 people who contributed to WordPress Core on Trac last week:

@johnbillion (6), @audrasjb (3), @SergeyBiryukov (3), @paaljoachim (3), @hellofromTonya (3), @desrosj (3), @sabernhardt (2), @peterwilsoncc (2), @davidbaumwald (2), @marybaum (2), @pbiron (2), @flixos90 (1), @tmatsuur (1), @tikifez (1), @lukecarbis (1), @dianeco (1), @mikeschroder (1), @kjellr (1), @sergeybiryukov (1), @cenay (1), @antonlukin (1), @krstarica (1), @stodorovic (1), @francina (1), @clorith (1), @TimothyBlynJacobs (1), @melchoyce (1), @sarahricker (1), @youknowriad (1), @rafhun (1), @nosolosw (1), @mukesh27 (1), @johnjamesjacoby (1), @ryelle (1), @poena (1), @jdy68 (1), @dd32 (1), @alexstine (1), @munyagu (1), @janak007 (1), @afragen (1), and @felipeelia (1).

Please join me to say welcome to our 3 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@tikifez, @cenay, and @rafhun.

Core committers: @sergeybiryukov (6), @desrosj (6), @ryelle (4), @johnbillion (1), @peterwilsoncc (1), @noisysocks (1), and @mikeschroder (1).

Please note: it only includes commits with proper props attribution.

#5-7, #week-in-core

WordPress 5.7 Release Candidate 3

In preparation for the final release of WordPress 5.7 on March 9th 2021, 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). 3 has been packaged and released 🎉

The following were late-discovered blocking issues:

  • Twenty Fifteen & Twenty Sixteen: Remove extra space around post editor ([5046852646)
  • Twenty Twenty-One: Correct inner container background color for Cover Blocks ([5046952676)
  • Twenty Twenty-One: Make text readable when dark background is selected for the Media & Text 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. ([5049452702)
  • XML-RPC: Pass an empty array to the xmlrpc_call action in methods that have no arguments ([5050052524)
  • Block Editor: Fix color support for dynamic blocks ([5048952709)
  • Block Editor: Drop zone: fix media lib duplicate issue ([5049752718)
  • Block Editor: Fix cover block content position not migrating correctly from deprecated version ([5049752718)
  • Block Editor: Fix solid-color only cover has small gray border in the editor only ([5049752718)
  • Block Editor: Add z-index to gallery fig caption to make sure it is still selectable over absolute positioned border ([5049752718)
  • Block Editor: Cover: Add missing align attr to deprecation ([5049752718)

A special thanks to the reporters of these issues for bringing them to light.

You can test the WordPress 5.7 release candidate in two ways:

  • Try 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 (choose the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and 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./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). Only” stream options)
  • Or download the release candidate here (zip).

If you think you’ve found a 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., you can post to the Alpha/Beta area in the support forums. We’d love to hear from you! If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

Props to @hellofromtonya for compiling all of the issues and to @audrasjb and @davidbaumwald for their peer revision.

___________________________

RC here, RC there…
RCs are everywhere
Because we must prepare!

#5-7

Dev Chat Agenda for March 3rd 2021

Here is the agenda for this week’s meetings to occur at the following times: March 3rd, 2021 at 5:00 UTC and March 3rd, 2021 at 20:00 UTC.

Announcements

  • WordPress 5.7 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). 2 is released 🎉

Blogblog (versus network, site) Post Highlights

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.

In case you missed it, the WordPress 5.7 Field Guide is out! Read through it for a full breakdown of everything you need to know about WordPress 5.7.

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 our standard list 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-7, #agenda, #dev-chat

A Week in Core – March 1st, 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 February 22 and March 1st, 2021.

  • 27 commits
  • 44 contributors
  • 92 tickets created
  • 7 tickets reopened
  • 85 tickets closed

You might have noticed that the activity on Core is still pretty high this week, as we entered the WordPress 5.7 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). cycle.

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.

Code changes

Administration

  • Revert the change to click event handler for fly-out submenus – #52638

Bootstrap/Load

  • Check if the error_reporting() function exists in wp-load.php#52226

Build/Tests Tools

  • Add missing `@covers` tags for files in phpunit/tests/load/#39265
  • Add missing `@covers` tags for files in phpunit/tests/link/#39265
  • Split the PHPUnit tests for PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher versions below 7.0 in half, allowing them to run in parallel and reduce the overall test run duration
  • Avoid attempting to redeclare the origin remote prior to sending the test results to the test reporting 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.#51734
  • Switch back to running the PHPUnit test suite against the src directory instead of build#51734
  • Prevent the NPM/Composer caches in 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/ Actions from snowballing – #52660
  • Disable fail-fast for PHPUnit testing – #52612
  • Reset current screen after setting it to dashboard in add_submenu_page() tests – #52607
  • Introduce a CONTRIBUTING.md file – #33043
  • Stop running the restapi-jsclient tests separately – #52608
  • Add a missing word to the CONTRIBUTING.md file – #33043
  • GitHub Actions – #52645

Bundled Themes

  • Twenty Twenty-One: Improve transparent PNG logo visible on focus – #52257

Docs

  • Use correct variable in the style_loader_tag 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. DocBlockdocblock (phpdoc, xref, inline docs)#52673
  • Improve documentation for WP_Block_Type properties – #48640

External Libraries

  • Install jQuery via NPM – #52647
  • Further fix jQuery deprecations in WordPress core – #51812
  • Correct click event handling in the Thickbox library – #52618

Help/About

  • Remove extra space in the 5.7 About page copy – #52632
  • WordPress 5.7 About Page – #52347

Security

  • move Content-Security-Policy script loaders – #39941

Script Loader

  • Prevent wp_localize_script() warnings – #52534

Users

  • Use localized site title for password reset emails – #52605
  • Only include the IP address in password reset email if the user is not logged in – #34281
  • Ensure reset password emails are in the receiving user’s localeLocale A locale is a combination of language and regional dialect. Usually locales correspond to countries, as is the case with Portuguese (Portugal) and Portuguese (Brazil). Other examples of locales include Canadian English and U.S. English.#52605
  • Relocate the Password Reset feature to the Account Management section – #52597

Props

Thanks to the 44 people who contributed to WordPress Core on Trac last week:

@peterwilsoncc (9), @audrasjb (6), @johnbillion (5), @SergeyBiryukov (4), @desrosj (3), @hellofromTonya (3), @jrf (3), @sephsekla (2), @chouby (2), @kraftbj (2), @johbillion (2), @adamsilverstein (2), @hedgefield (1), @davidbaumwald (1), @metalandcoffee (1), @noisysocks (1), @netweb (1), @melchoyce (1), @ad7six (1), @francina (1), @marybaum (1), @lukecarbis (1), @boonebgorges (1), @meher (1), @sarahricker (1), @ediamin (1), @webcommsat (1), @Ipstenu (1), @aristath (1), @Clorith (1), @gmariani405 (1), @carike (1), @ryelle (1), @sabernhardt (1), @poena (1), @tobifjellner (1), @jorbin (1), @gziolo (1), @iandunn (1), @ayeshrajans (1), @fijisunshine (1), @rima1889 (1), and @mukesh27 (1).

Please join me to say welcome to our 2 new Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. of the week ♥️
@fijisunshine and @rima1889.

Core committers: @sergeybiryukov (12), @desrosj (7), @johnbillion (3), @peterwilsoncc (3), and @ryelle (1).

Please note: it only includes commits with proper props attribution.

#5-7, #week-in-core

Dev Chat Summary: February 24, 2021

This post summarizes the weekly dev chat meeting from February 24, 2021 (Slack Archive). There was no APAC timed dev chat this week.

Announcements

WordPress 5.6.2 was released on Monday, February 22, 2021.

WordPress 5.7 RC1 is also available for testing!

5.7 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. & developer notes

The WordPress 5.7 Field Guide has been published! All developer notes for the 5.7 release are included. Head on over and dive in!

All 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 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. related to the 5.7 release can also be found by browsing the 5.7 and dev notes tags. Props to @audrasjb for making sure every ticketticket Created for both bug reports and feature development on the bug tracker. needing a dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change 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. had a guardian.

Blogblog (versus network, site) post highlights

Component maintainer updates

  • Build/Test Tools: @sergeybiryukov shared #33043, #52643.
  • Upgrade/Install: @audrasjb reiterated the call for feedback on the Rollback Plugin Update Feature Plugin post.
  • Date/Time: No major news to share this week.
  • General: No major news to share this week.
  • I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: No major news to share this week.
  • Permalinks: No major news to share this week.
  • Menu/Widgets: No major news to share this week.

Open floor

  • @davidbaumwald proposed adding an officially recognized needs-testing-info keyword to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. that can be used to request better documented steps for testing a proposed 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.. The Meta-#5634 ticket has been opened to field feedback.

Next week

The next dev chat meetings will take place on Wednesday, March 3rd, 2021 at 5:00 UTC and Wednesday, March 3rd, 2021 at 20: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.

Props @hellofromtonya, @cbringmann, and @audrasjb for proof reading.

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