Upgrade/Install component meeting agenda for November 9, 2021

The next meeting is scheduled on Tuesday, November 9, 2021, at 17:00 UTC and will take place on the #core-auto-updates 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.

The aim of the meeting is to discuss the rollback for failed 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/theme updates 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. #51857

@peterwilsoncc reported some failures on his tests, so the commit might need to be reverted. Let’s discuss it together.

Got something to propose for the agenda? Please leave a comment below.

See you there!

#core-auto-updates, #updater, #upgrade-install

Upgrade/Install component meeting agenda for September 21, 2021

The next meeting is scheduled on Tuesday, September 21, 2021, at 17:00 UTC and will take place on the #core-auto-updates 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.

The aim of the meeting is to discuss the four years old ticketticket Created for both bug reports and feature development on the bug tracker. #22316 and two PRs that have been proposed to solve it.

Let’s try something different! A Zoom call 🙂 I will drop the link to it in the Slack channel at the start of the meeting.

Got something to propose for the agenda? Please leave a comment below.

See you there!

#core-auto-updates, #updater, #upgrade-install

Upgrade/Install component meeting agenda for September 14, 2021

The next meeting is scheduled on Tuesday, September 14, 2021, at 17:00 UTC and will take place on the #core-auto-updates 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.

The aim of the chat is to check the status of the [Feature project] Updates on updating the updaters and scrub tickets for inclusion in WordPress 5.9

Got something to propose for the agenda? Please leave a comment below.

See you there!

#core-auto-updates, #updater, #upgrade-install

Upgrade/Install Meeting Notes, September 7

Quiet but productive chat, only two attendees, @afragen and @francina, but here is a quick recap 🙂 Slack logs.

#51857

@afragen stress tested it but didn’t find any concerning blockers. I asked @sergeybiryukov about commit: he is going to do another round of code review tomorrow, September 8, and if everything looks good, it will be committed. The solution addresses Outcome 1 and 2 of the initial feature proposal.

Outcome 3 – Have managed updates (database migrations)

This is going into the icebox momentarily. It needs a new 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. to work. If anyone is interested in picking it up, join our meetings on Tuesdays, at 17:00 UTC.

Outcome 4 – Create a unified JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. convention for requirements and dependencies.

This nine-year-old issue was revived. Worth reading through it all.

Here is @afragen TL;DR

  1. Any 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 that requires a dependency should degrade gracefully if that dependency is not present.
  2. Dependencies should have notices to install and later activate the dependency.
  3. Some notification of which plugin is a dependency of what other plugin.

There is also the potential for abuse, with plugins reporting dependencies that aren’t really dependencies.

Andy also suggested making a proof of concept plugin, instead of creating a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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..

What say you?

Do you want to add to the conversation? Please comment on the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. (beware, comments in GH will be shown in Trac, but not the other way around, so please use Trac, thank you 🙏). We are in the “feedback, validate, outreach, test, inform, reply to questions” 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. stage. Join us!

See you next week 👋

#core-auto-updates, #updater, #upgrade-install

Upgrade/Install component meeting agenda for September 07, 2021

The next meeting is scheduled on Tuesday, September 7, 2021, at 17:00 UTC and will take place on #core-auto-updates 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.

The aim of the chat is to check the status of the [Feature project] Updates on updating the updaters.

Got something to propose for the agenda? Please leave a comment below.

See you later!

#core-auto-updates, #updater, #upgrade-install

Upgrade/Install component meeting agenda for August 24, 2021

The next meeting is scheduled on Tuesday, August 24, 2021, at 17:00 UTC and will take place on #core-auto-updates 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.

The aim of the chat is to check the status of the rollback for failed plugin/theme updates after last Friday’s testing session and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors./scrub tickets in the component.

Got something to propose for the agenda? Please leave a comment below.

See you later!

#core-auto-updates, #updater, #upgrade-install

Upgrade/Install Meeting Notes, August 17

On August 17, the Upgrade/Install component met to discuss the proof of concept that builds on the rollback update failure 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 prepare it to merge in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Slack logs.

In the post and during the meetings a number of concerns and potential improvements were mentioned, so here are the next steps:

  1. @aristath will write steps for manual testing, in time for the next Test scrub (Friday, August 20) ✅ Instructions in the Pull Request
  2. @francina will liaise with the Test Team and Hosting Team (aka cross post 😇) so the PR can be tested ✅
  3. @sergeybiryukov will do the code review once there is a good amount* of testing.

The conversation led to other two topics

  1. Unit tests for the updater classes. They don’t exist. Should they exist? Yes. But it’s a big task and it needs a dedicated initiative. Let’s take one step at a time.
  2. #51928 is independent from the auto-updates/failures/rollback items, but closely related. As @pbironmentioned, failure data can give information about areas in the updater that could use more error checking/recovery logic, etc. The results are anonymous and seen only by the .org system folks.

If you have input on any of the above, please leave a comment – here or on the relevant PR/Tickets.

Thanks!

#core-auto-updates, #updater, #upgrade-install

Upgrade/Install component meeting agenda for August 17, 2021

The next meeting is scheduled on Tuesday, August 17, 2021, at 17:00 UTC and will take place on #core-auto-updates 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.

The aim of the chat is to check the status of the rollback for failed plugin/theme updates and decide if it is ready for a merge proposal.

Got something to propose for the agenda? Please leave a comment below.

#core-auto-updates, #updater, #upgrade-install

Upgrade/Install component meeting agenda for August 3, 2021

The next meeting is scheduled on Tuesday, August 3rd, 2021, at 17:00 UTC and will take place on #core-auto-updates 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 with the following agenda:

  • Status update on the rollback for failed plugin/theme updates
  • Open floor, tickets awaiting review, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. – depending on who shows up 🙂

Got something to propose for the agenda? Please leave a comment below.

#core-auto-updates, #updater, #upgrade-install

[Request for feedback] Updater Proof of Concept

Over the past month, @aristath and @sergeybiryukov have been working on a proof of concept to solve the two first outcomes highlighted in the Updater Initiative scope post.

They drew inspiration from the https://wordpress.org/plugins/rollback-update-failure/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and tried to address a few tickets.

They created a proof of concept that can be found in a draft PR on https://github.com/WordPress/wordpress-develop/pull/1492/files and does the following:

  • Add new arguments to hook_extra passed by plugin and theme updates to ensure we can rollback to the correct version.
  • After a plugin/theme is successfully downloaded and extracted, the old plugin/theme folder is moved to wp-content/upgrade/rollback/plugins/PLUGIN or wp-content/upgrade/themes/THEME wp-content/upgrade/rollback/themes/THEME (thanks Paul Bigai for catching that)
  • If the plugin/theme was successfully installed, the backup of the previous version we kept in wp-content/upgrade/rollback/ is deleted.
  • If the plugin/theme was not successfully installed, then we cleanup any remnants of files in wp-content/plugins/PLUGIN (or the corresponding folder for themes), and then we move the backup we kept in the rollbacks folder back to its original location.
  • Adds info in the site-health screen, to make sure the rollback folder is writable (or can be created if it doesn’t exist)

That is the basic concept. The team ran some tests, helped by @peona as well and it seems to be working.

The main difference with the rollback-update-failure plugin is that this solution moves the plugin/theme folders instead of zipping/unzipping them. This change should help to make the implementation a bit lighter/safer on shared hosts with limited resources.

Before moving forward, I would like to ask the Upgrade/Install Maintainers to have a look at this and discuss together, in the comments of this post, if you agree with this change, if it works, etc…

I am not setting a deadline for the comments, but ideally, I would like to be able to write a merge proposal for 5.9 so I will review the post in mid-JulyAugust (thanks @meher for pointing out that we are at the end of July already 😂) and nudge a bit more 😉

Thank you all for your help and feedback!

Thanks @ipstenu for the peer review

#updater