These are the weekly notes for the WP Auto-updates team meeting that happened on Tuesday June 16, 2020. You can read the full transcript on the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-auto-updates Slack 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.
Reminder: WP Auto-updates Feature has been merged into WordPress Core so bugs reports and enhancements requests should now happen on Core Trac.
Update on Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
#50215 – Help Tabs implementation.
This ticket Created for both bug reports and feature development on the bug tracker. was discussed by the team and the patch 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. was merged by @whyisjake during the meeting.
#50268 – Auto-update email notifications.
@desrosj is working on a new patch.
#50350 – Provide plugin 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 theme versions informations in auto-updates email notifications.
This ticket still needs a patch. @audrasjb is working on it.
#49771 – Double “Updated!” text blocks when updating theme.
This one still needs a patch.
#50280 – Enable auto-updates shows for plugins with no support.
This ticket is now very close to be ready for commit. @azaozz and @pbiron are on it.
#41910 – Scheduled maintenance message.
This ticket was raised by @paaljoachim. As it is outside the auto-updates feature scope, the best way to move forward on this proposal is to point it out in core devchat.
@audrasjb touched bases with the Docs team last meeting on Monday. @milana_cap is available to review it.
It should be done ahead of the release date so localized versions of HepHub have time to translate it before WordPress 5.5 release. @audrasjb is going to open a Meta 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. Trac ticket to follow this task.
Dev 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, and 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. for WordPress 5.5
@audrasjb proposed the following structure for the dev note:
- How to hook into the general auto-updates interface
- Disable the whole auto-updates UI User interface
- Plugins screen (single and multisites)
- Themes screen (multisites)
- Themes screen (single sites)
- Update screen
- How to hook into auto-updates email notifications
- Success notifications
- Failure notifications
- Mixed notifications
- WP-Cron & plugins/themes auto-updates
- Auto-updates Help Tabs
Feel free to comment below or to get in touch in core-auto-updates Slack Channel if you have any suggestion for this dev note.