Dev Chat Agenda for May 6, 2020

Here is the agenda for the weekly meeting happening later today: Wednesday, May 6, 2020, at 20:00 UTC.

Announcements

WordPress 5.4.1 has been released!

Highlighted/Need Feedback Blogblog (versus network, site) Posts

Components Check-in

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration

Open Floor

Got 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-4-1, #agenda, #devchat

Dev Chat Summary: 29th April, 2020

@francina facilitated the latest weekly Dev Chat on this agenda; here’s the Slack transcript.

Announcements

@whyisjake announced the official release of WordPress 5.4.1.

The group took a moment to cheer this second releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. accomplished during the pandemic. To quote @whyisjake

“Thank you all for helping get out this release. It’s an amazing example of the collaboration, dedication, and spirit of open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL.. Releases like this really makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the web a better place.”

@whyisjake

Upcoming Releases

Work is underway for WordPress 5.5 – and has been, since the 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". at 5.4 RC2. This is prime time for you to actively develop, test, give feedback and more. @davidbaumwald has scheduled the first bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub for Tuesday, May 5, 2020, at 18:00 UTC and has already published it on the meetings page

Highlighted/Blogblog (versus network, site) Posts

These posts need your feedback, as soon as you can get your thoughts together:

5.4 Retrospective – Call for feedback – Deadline April 30

Please focus your feedback on processes only. Next week @francina will collect it all and publish a recap much as she did for 5.3.

So far, chat participants noted there hasn’t been a whole lot of feedback from 5.4 – why not? Speculation included:

  • the release went particularly smoothly, 
  • privacy concerns,
  • the state of the world,
  • some combination of the above! 

WordPress 5.5: Call for Tickets – Deadline April 30

Please add the tickets you most want to see land in 5.5 to the comments of this post.

Of course, please remember that there are no magic bullets – nobody can guarantee your ticketticket Created for both bug reports and feature development on the bug tracker.’s inclusion in the next release. With that said, the team (which does include you!) can only fix what we know is wrong. So please bravely share!

Proposal: Core Team Rep Elections 

@francina and several others admitted they were confused about whether this post is for adding nominations or getting feedback on the idea of a nomination process ahead of a second post to come, to add nominations. After some discussion,  the group decided to ask @jeffpaul for a separate nomination post. He agreed, and it’s up!

WCEU Online 2020 Contributor Day

Thanks to the confusion around Team Reps, since that’s who works with the Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. squads of every WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more., the group tabled the discussion of WordCamp Europe Contributor Day until next week.

REST API: Decision on Introducing a dashboard namespace 

In the words of the post, “the 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/. team has decided on giving major features their own namespace. For example, wp-sitesite (versus network, blog)-health and wp-customize.” This should help all sorts of people find these features and hook into them a lot more easily.

Components Check-in

@garrett-eclipse announced that Privacy + Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site will share a focus in 5.5 to bring the relevant tools to multisite. Teamwork makes the dream work!💥

@azaozz has been investigating the best way to update jQuery: https://core.trac.wordpress.org/ticket/37110#comment:105. The work will take three WordPress releases and can start in 5.5. Please review his plan! 

@desrosj is planning to update the SimplePie library and, possibly, PHPMailer in 5.5. He welcomes your reviews and thoughts on both.

@audrasjb updated the group on Plugins & Themes Auto-updates. This week the merge proposal goes live on Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. — and patches on the tickets, too.

Discussions

How long do we let a merge proposal percolate?

@whyisjake asked: in light of the auto-updates work, how much time do we normally let a merge proposal percolate before moving forward? A lively discussion followed, with resident historians @azaozz and @jorbin chiming in and concurring: it obviously depends on the proposal, but generally speaking, 1-2 weeks and a blog post is reasonable.

What are the plans for 5.4.2?

@asif2bd asked when 5.4.2 might be released. The answer: only if necessary.

If nothing major comes up in the next couple of weeks post 5.4.1, we’ll move onto 5.5. Now, @desrosj did create a 5.4.2 milestone when it became clear 5.4.1 wouldn’t include a bundled-theme update, in case we need it for backporting later. For now, there are no compelling reasons to do another minor — but stay tuned! Things can always change. 

Friendly Reminder

Finally, @francina reminded the group that you don’t have to wait for devchat to raise issues for discussion. In fact, you should really start the conversation ahead of time.

Here’s how: 

  • Post something on the blog – async conversations starts
  • Schedule an extra meeting here or in the relevant channel and advertise it far and wide so people can attend
  • Post a recap in the blog
  • Rinse and repeat as necessary.  

Take care!

#5-4-1, #5-5, #meeting-notes, #devchat

Dev Chat Agenda for April 29, 2020

Here is the agenda for the weekly meeting happening later today: Wednesday, April 29, 2020, at 20:00 UTC.

Announcements

If anyone has any announcement to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)., now is the time!

Upcoming Releases

  • Work continues on WordPress 5.4.1 lead by @whyisjake. WordPress 5.4.1 RC1 is out.
  • All the maintainers have been pinged about 5.5. The information has been collected and expect a further pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” for a status update so the schedule for 5.5 can be finalised.

Highlighted/Need Feedback Blogblog (versus network, site) Posts

Components Check-in

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration

Open Floor

Got 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-4-1, #5-5, #agenda, #devchat

WordPress 5.4.1 RC1

WordPress 5.4.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 now available for testing!

There are two ways to test the WordPress 5.4.1 release candidate: 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 (you’ll want to 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), or you can download the release candidate here (zip).

What’s in this release candidate?

5.4.1 Release Candidate 1 features 11 bug and regression fixes, as well as 6 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. Here’s a detailed list:

  • #49838AccessibilityAccessibility 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): Fix the headings hierarchy on the Freedoms page
  • #49798 – Customize: Give the WordPress logo a white background for dark mode browsers
  • #49853 – Mail: Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). the check for empty post title in wp-mail.php more resilient
  • #49753 – Media: Remove display: none; from the (visually hidden) <input type="file"> button used in Plupload to select files for uploading. Fixes selecting files in Edge <= 44 and iOSiOS The operating system used on iPhones and iPads. Safari
  • #49772 – Privacy: Support additional elements (table, ol, ul) in privacy policy guide new styling
  • #49802 – Privacy: Make the deprecated wp_get_user_request_data() function available on front end
  • #49645REST 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/.: Fix revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. controller get_item permission check
  • #49648 – REST API: Fix _fields filtering of registered rest fields
  • #49824Sitesite (versus network, blog) Health: Instantiation prevents use of some hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. by plugins
  • #49759TaxonomyTaxonomy 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.: Un-deprecate category_link and tag_link filters
  • #49974 – Block Editor updates

What’s next?

Committers: 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) still applies when making any changes to the 5.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 official 5.4.1 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. is still scheduled for Wednesday, April 29, 2020. Happy Testing!

#5-4-1, #minor-releases

Devchat meeting summary – April 22, 2020

The chat was led by @davidbaumwald based on this agenda.

The full meeting transcript is available on Slack.

Highlighted blogblog (versus network, site) posts

@davidbaumwald shared some posts from the Makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog.

5.4 Retrospective – Call for feedback: the deadline is April 30 and everyone is welcome to leave a feedback.

Proposal: Core Team Rep Elections: the deadline for nominations and self-nominations is May 4.

We’re applying to Season of Docs: a new working group that needs help!

WordPress 5.5: Call for Tickets: the deadline is April 30.

Upcoming Releases

WordPress 5.4.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 was supposed to be released yesterday Wednesday, but there were some miscommunication between Core team and 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/ team. The RC has then been pushed back to this Friday. The Gutenberg changes that are going to be included in the releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. are listed in this pull request. The milestone for this point release is also cleared.

@davidbaumwald reminded that for 5.5, all the maintainers have been pinged about potential features and focuses.  If you’re a component maintainer and haven’t replied yet, please do, so scope and schedule can be proposed.

He also said that work for 5.6 release, aka all-women release, continues. All the women that expressed interest have been contacted. @chanthaboune, @angelasjin, @cbringmann and @francina will work on phase 2: identifying missing roles and cohorts to organize the team that will ride along with 5.5.

Components Check-in

@francina has pinged #meta team about having a weekly scheduled post to check Components status; @dd32 expressed some concerns about the noise that it will create. @davidbaumwald suggested to move on with this for a three-month test.

@audrasjb gave an update about plugins and themes auto-update feature. The team released version 0.6.0 of the Feature Plugin yesterday Wednesday.

The Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. contains all the identified must-have features and the UIUI User interface was reviewed by several teams. The team is now about to write the Core merge proposal post on Make/Core. More infos here.

Open Floor

@apedog asked a question about routing in WordPress Core. He stated that the WP class having $_SERVER hard-coded into it. And this would require re-writing the methods inside WP class, but without changing its functionality.

@clorith said that he’s generally against the bot idea for a general channel with lots of chatter, and the loss of potential input to backscroll. If it’s going to happen, it should be on Make/* somewhere for consistency and visibility.

@audrasjb pointed out to #16557, a long standing ticketticket Created for both bug reports and feature development on the bug tracker. raised by some people in the French WordPress community. It appears it would be a great SEO enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. to provide proper filters on redirect_guess_404_permalink() function.

He milestoned the ticket to 5.5.0 and refreshed the existing 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. against trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. after testing it. This still needs some unit tests, but before writing them, it would be nice to get a quick review on the current proposal.

@netpassprodsr called for review on #49832.

#5-4-1, #5-5, #5-6, #summary

Dev Chat Agenda for April 22, 2020

Here is the agenda for the weekly meeting happening later today: Wednesday, April 22, 2020, at 20:00 UTC.

Announcements

If anyone has any announcement to makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility)., now is the time!

Upcoming Releases

  • Work has started on WordPress 5.4.1 lead by @whyisjake
  • All the maintainers have been pinged about 5.5. Some replied, some didn’t – please do, so scope and schedule can be proposed.
  • Work for 5.6, aka all-women release, continues. All the women that expressed interest have been contacted. @chanthaboune, @angelasjin, @cbringmann and I will work on phase 2: identifying missing roles and cohorts to organise the team that will ride along with 5.5

Highlighted blogblog (versus network, site) posts

Components Check-in

I have pinged 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. about having a weekly scheduled post to check Components status – @dd32 expressed some concerns about the noise that it will create. I would still suggest to move on with this for a three-month test.

But in the meantime… the usual:

  • News from components
  • Components that need help/Orphaned components
  • Cross-component collaboration

Open Floor

Got 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-4-1, #5-5, #5-6, #agenda, #devchat

Devchat meeting summary – April 15, 2020

@davidbaumwald facilitated the chat on this agenda.

Full meeting transcript on Slack

Highlighted blogblog (versus network, site) posts

Upcoming Releases

WordPress 5.5 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.

WordPress 5.5 Call for Tickets is still open for feedback.

@sageshilling shared that the Editor team is working on a Gallery block update for WP 5.5.

WordPress 5.4.1 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.

@audrasjb shared that on the 13 tickets in the milestone, 12 are already committed and one ticketticket Created for both bug reports and feature development on the bug tracker. still needs some work.

@whyisjake self nominated to lead WordPress 5.4.1. @davidbaumwald added that if anyone is interested in helping with 5.4.1, they can get in touch with @whyisjake. @audrasjb expressed his interest.

The idea is to ship 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). next week and a final releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. in two weeks.

Components Check-in

@imath shared an update on Comments component:

  • He is working on a 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 to progress about #35214
  • It would be nice to get some feedback on #49236, since it would be nice to have 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. committed early
  • Feedback is also needed on #49179

@clorith pointed out that it would be nice to move forward on Dashboard Namespace introduction in REST API. Volunteers are welcome to contribute to the associated tickets.

@audrasjb shared the 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) team main focuses for WP 5.5:

@audrasjb also shared an update about WP Auto-updates feature plugin: version 0.5 was released just before the devchat. It addresses all the feedback received from the Design and Accessibility teams.

Open floor

@audrasjb raised a question concerning WP Auto-updates feature: should it provide a way to rollback to the previous version of an auto-updated plugin? This feature was proposed in a GitHub issue.

@imath believes WordPress could makemake A collection of P2 blogs at make.wordpress.org, which are the home to a number of contributor groups, including core development (make/core, formerly "wpdevel"), the UI working group (make/ui), translators (make/polyglots), the theme reviewers (make/themes), resources for plugin authors (make/plugins), and the accessibility working group (make/accessibility). it easier to come back to a previous version of a plugin.

@timothyblynjacobs pointed out that one of the big issues with rolling back, is that if a plugin does any kind of DB change, it can’t necessarily rollback without data loss or other breakage.

@clorith added that it might “double” the time needed per update in doing so, maybe even triple if it needs to revert as well, the increase in memory consumption, and processing time adds a new layer of potential failures as well.

@afragen raised this could be detected by the new WSOD so at least it wouldn’t white screen a sitesite (versus network, blog). @timothyblynjacobs answered WSOD protection would notice the error, but wouldn’t automatically deactivate the plugin.

@timothyblynjacobs thinks it would also be worth clarifying whether this would be limited to the updater automatically rolling back, or it being available for the user to take action.

For @sageshilling, ideally, the update if automated, would check for known problems and either notify site owner if detected during import.  If possible, stop import, roll back and allow the site owner to address it.

@clorith thinks the correct approach is yes, keep a backup until the update is completed so it can be reverted, and introduce an actual feature for plugins/themes to run upgrade tasks after the fact, that way the site can be confirmed still functional without triggering any DB upgrades for example.

@timothyblynjacobs thinks there would be value to plugins being able to rollback the same way coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. does if the actual upgrade process fails. But he think having a WP-Rollback [note: it’s a plugin available on the repository] type solution in core should be a separate project.

As WP Auto-updates co-lead, @pbiron added an other question to the discussion: if one want to rollback, is that something that should be in the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. or can that be worked on after the feature plugin is merged into core? He think the WP_Automatic_Updater class has enough hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. that we could work on it in the feature plugin, but it might be difficult.

@desrosj point out that the way core handles rollbacks currently is a rollback URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is provided in the 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. response, and it gets retrieved if a severe failure occurs. There is no equivalent link returned in the API response for plugin updates.

@imath believes it’s better to have a way to manually upgrade/downgrade a plugin in WordPress before merging the feature into Core.

@desrosj thinks that for the first iteration, the WSOD may be enough for a non-technical to recover from an issue. Enabling auto-updates for plugins and themes will be opt-in, so maybe there just needs to be appropriate messaging when the site owner enables an auto-update for the first time.

@clorith agreed, when/if the feature is enabled by default, it needs rollback, but for a first iteration with manual enablling, let’s roll with what a manual way of reverting, sounds reasonable.

@audrasjb pointed out that managing updates rollback is a project in itself as it is something that should be currently available for manual updates.

@afragen asked: aren’t core rollbacks only for critical errors? Any plugin downloads and updates correctly but results in a fatal because of a coding issue sets a higher bar than we have for core.

@pbiron added that the current scope of the feature plugin has been providing a UIUI User interface for enabling/disabling auto-updates, and rollback seems to be another feature plugin itself. Also, there is a notification email that gets sent with updates successes and failures. Also @timothyblynjacobs added that WSOD would send a recovery mode email if a site has fatal error on protected endpoints. @desrosj added that in the current process to manually upgrade a plugin in the dashboard today, there is no protection for a fatal error or coding error in the plugin.

@audrasjb raised that a rollback feature would be a nice improvement to WordPress Core, but it’s useful for both manual and auto updates.

#5-4-1, #5-5, #feature-autoupdates

Devchat meeting summary – April 8, 2020

@audrasjb facilitated the chat on this agenda.

Full meeting transcript on Slack

Announcements

Upcoming Releases

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.: WP 5.4.1

While there is no releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. planning for the moment, there is already 12 tickets in the milestone.

2 tickets are labelled with major severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs.. It will probably lead to a point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. in few weeks.

@whyisjake will run a first bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub for WP 5.4.1 on Thursday April 9, 2020 at 20:00 UTC.

@marybaum volunteered to run another bug scrub on Friday.

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: WP 5.5

There is currently 27 tickets with early keyword in the milestone. Those tickets need to be merged as soon as possible.

@davidbaumwald will run a first bug scrub for WP 5.5 on Tuesday April 14, 2020 at 19:00 UTC.

Component maintainers updates

@afragen shared a number of tickets for theme compatibility that still need eyes and are marked early. All have working patches and need further testing.

@audrasjb pointed out that the Auto-updates team needs a cross-team discussion about wording and specifically concerning the action links text labels. Design and 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) teams could help, and of course everyone interested. Design & Wording validation is the main goal for the next version of the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins..

@garrett-eclipse shared that the Privacy team has a multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site focus in 5.5 so any people from Networknetwork (versus site, blog)/multisite component is welcome to assist.

Daylight saving time: devchat meeting time change

As Daylight saving time already started for every countries/locales on our planet 🌏 the devchat meeting time will be adjusted from 21:00 UTC to 20:00 UTC.

The next meeting will be held on Wednesday April 15, 2020 at 20:00 UTC.

@marybaum is going to publish a specific announcement about this adjustment.

#5-4-1, #5-4, #5-5, #dev-chat, #devchat