These are the weekly notes for the WP Auto-updates team meeting that happened on Tuesday July 14, 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.
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 drafted a dev note focused on hooking the plugins and themes auto-updates UI User interface controls. @pbiron, @desrosj and @azaozz started to review this proposal.
It was previously decided to split the auto-updates dev note into several Posts. @audrasjb also drafted a dev note for email notifications. @pbiron pointed out that a dev note will be necessary for Site health screen hooks 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. and functions. It will probably be added to the second dev note about email notifications. The first dev note will be published on Wednesday or Thursday.
Update on Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
- #50350: A couple weeks ago, the team agreed to add the version updated
TO to the emails for 5.5 and possibly add the version updated
FROM in 5.6. @audrasjb is working on a 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. for this.
- #50437 still needs a patch.
- Concerning #50512, items 1, 2 and 4 of the ticket Created for both bug reports and feature development on the bug tracker. are already fixed. Item 3 will be discussed on Friday by the accessibility 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.
- @desrosj is working on #50662.
- @pbiron is working on #50663.
- @johnbillion pointed out that #50437 needs some more discussion. This ticket will probably be moved to milestone 5.6.
- Concerning #50623, It’s probably too late to address this ticket before 5.5 is released, but @audrasjb proposed to comment with few links to previous decisions (especially design decisions, as the design team already reviewed the interface) made by the team.
- @apedog asked for review on ticket #32101, but given it’s not directly related to plugins and themes auto-updates, it’s probably better to raise this ticket during core team dev chat meeting.
#5-5, #auto-update, #core-auto-updates, #feature-plugins, #feature-projects, #feature-autoupdates