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