The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of the tickets in the spreadsheet (they all refer to Outcome 1 of the Updater initiative)
On Tuesday June 1, I did a scrub in the #core-auto-updatesSlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel about tickets related to Outcome 1 of the Updaters initiative, “Make sure the zips upload and unpacking are safe”. You can read the monologue on Slack 🙂
#33571 – Asked for more information to confirm that the issue persists
#34676 – I will test it and if it needs a refresh I will leave a comment on it
#38084 – Pinged @desrosj for review since there is a patchpatchA 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. uploaded
#44118 – Patch has been refreshed by @pbiron recently, added needs-testing keyword
TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of the tickets in the spreadsheet (they all refer to Outcome 1 of the Updater initiative)
Open floor/tickets awaiting review
Got something to propose for the agenda? Please leave a comment below.
#14781 – The ticketticketCreated for both bug reports and feature development on the bug tracker. was discussed also during the previous chat. It was decided to close it and follow the best practices laid out in the plugin handbook.
#20944 – The ticket was closed. The maintainers don’t see an elegant way to automate this action at this time. The solution is to re-activate the pluginPluginA 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 from the CLICLICommand Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. or via FTPFTPFTP is an acronym for File Transfer Protocol which is a way of moving computer files from one computer to another via the Internet. You can use software, known as a FTP client, to upload files to a server for a WordPress website. https://codex.wordpress.org/FTP_Clients..
#17301 – A method or instructions on how to test would be good. Added a note asking for testing info in the ticket.
#51823 and #51857 – The issue in the first ticket can not be reproduced or addressed without more details. @francina will investigate with @sergeybiryukov since the ticket mentions the Yoast plugin. As for the second ticket, @afragen pointed out that there were issues in the copying of the downloaded plugin or the plugin was incompletely downloaded and it’s hard to determine. The feature pluginFeature PluginA plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins.Rollback Update Failure is an attempt to restore the previous existing plugin in the event of a failure. He created a Gist to force a failure to see how the feature plugin works. https://gist.github.com/afragen/80b68a6c8826ab37025b05d4519bb4bf – If you try it, please add your comments in the tickets.
#15134, #29408, and #36710 are all related to symlinks. @pbiron will evaluate those and see if he can close a couple of them in favor of keeping of single ticket open.
TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of the tickets in the spreadsheet (they all refer to Outcome 1 of the Updater initiative)
Open floor/tickets awaiting review
Got something to propose for the agenda? Please leave a comment below.
TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. of the tickets in the spreadsheet (they all refer to Outcome 1 of the Updater initiative)
Open floor/tickets awaiting review
Got something to propose for the agenda? Please leave a comment below.
The group will tackle the outcomes in order, to complete one sub-project before moving to another.
The weekly upgrade/install component meeting is back and the updater project will be part of them. Tuesdays at 5 pm UTC is confirmed.
@francina will post the agenda and host the meeting. If she isn’t available @audrasjb will step in.
@pbiron is going to go through the tickets in the “Outcome 1” list to prioritize them before the next meeting.
@audrasjb will refresh his patches as part of the “Outcome 1” drive.
The attendees agree that @schlessera‘s proposal to make everything as compatible as possible with WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/ should be part of the scope.
No additional tools will be used to keep track of the project at this time since it’s a small group of people working on it. If there will be more contributors (🤞), the decision will be revisited.
The attendees also checked an open ticketticketCreated for both bug reports and feature development on the bug tracker. on TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. (#53049) and agreed that it’s a good idea to include a changelog in the autoupdate emails that users that have opted-in to this service receive.
Outcome 1 – Make sure the zip uploads and unpacking are safe
Outcome 2 – Create a mechanism to upgrade and rollback
Outcome 3 – Have managed updates (database migrations)
Outcome 4 – Create a unified JSONJSONJSON, 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
Open floor / tickets awaiting review
Got something to propose for the agenda? Please leave a comment below.
These are the weekly notes for the Updates/Install component meeting that happened on Tuesday November 10, 2020. You can read the full transcript on the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.-auto-updatesSlackSlackSlack 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 meeting was focused on the component’s major project for 5.6: an UIUIUser interface for opting in to core auto-updates. The feature was merged into core at the end of the alpha cycle of WordPress 5.6, when ticketticketCreated for both bug reports and feature development on the bug tracker.#50907 was committed.
As per the post previously published by @chanthaboune on Make/Core, there will be some changes in core auto-updates scope for WordPress 5.6.
Here is our goals for WP 5.6:
Provide some updates to the design of the UI.
For existing installations, the behavior will remain the same as it is today: opted-in to minor updates by default, but a user must opt-in to major updates (constants and filters that are already in use by hosts or agencies will still take precedence).
For new installations, default behavior will change: opted-in to minor updates by default and opted-in to major updates by default.
On Monday 9, @audrasjb opened two tickets/patchs to handle those changes:
#51742: Make sure constants and filters are disabling the major auto-updates option
#51743: Auto-updates for major version is set by default to true for fresh installations
Both tickets can be merged independently. For the moment, ticket #51742 doesn’t address any UI change.
During the last devchat, @helen shared some concerns about the UI overload caused by the changes introduced in #50907. @karmatosed worked on some mockups to simplify the current interface. The intention is to get rid of the auto-updates section and to replace it with an action link when auto-updates are already activated:
After discussing those changes, the team agreed to consider using action links for both enable and disable actions, for better consistency. Indeed, it wouldn’t be great to have a full auto-updates section with a checkbox for enabling the feature, and a simple action link moved to the top of the screen to disable it. Replacing the section with a simple action link could also eases the burden caused by the multiple buttons on this screen.
Next steps until WP 5.6 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 4 scheduled on Thursday:
Enabling auto-updates by default for fresh installs is a small patchpatchA 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., and it’s ready to be committed in ticket #51743
Taking into account constants/filters was already done in ticket #51743, but not committed yet.
[TODO] UI changes:
@audrasjb to update the patch in ticket #51743 to transform the form/checkbox interface to action links located in the main section on the top of the update-core screen.
@pbiron also raised ticket #50870 and @hellofromtonya provided some feedback after the office hour to help this ticket to move forward. The ticket is now marked as ready for commit.
These are the weekly notes for the Updates/Install component meeting that happened on Tuesday October 13, 2020. You can read the full transcript on the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.-auto-updatesSlackSlackSlack 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 meeting was focused on the component’s major project for 5.6: an UIUIUser interface for opting in to core auto-updates: #50907.
@audrasjb sent a first patchpatchA 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 feature and shared a screenshot of the first workaround:
This approach adds two checkboxes, to provide the ability to enable/disable auto-updates for both minor and major auto-updates.
@pbiron pointed out that disabling auto-updates for minor releases was already discussed during previous meetings, and the decision is that it is not an option the Core team wants to provide to end-users. It needs to be disabled by a pluginPluginA 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 or by using the existing hooksHooksIn 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. or PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher constants. @audrasjb will update his patch accordingly, so there will be only one available option: opt-in for major releases auto-update.
@estelaris added that there is already 4 buttons on this screen. It would be nice to avoid adding a new one. She added that we should use a toggle button instead of a checkbox + a submit button. @audrasjb answered that there is no existing toggle component in WordPress Core for now. This eventual new component also would need to be designed, developed, and its accessibilityAccessibilityAccessibility (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) would need to be tested and reviewed. It doesn’t look realistic for WP 5.6 BetaBetaA pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1.
@paaljoachim proposed to move the auto-updates opt-in to General Settings. @pbiron and @audrasjb are not enthusiastic about this proposal as for now, the Updates screen seems to be the more natural place to find Core auto-updates settings.
@karmatosed pointed out that this screen is already a very dense interface. She will share some alternative designs this week on this Figma file, to help design decisions. @audrasjb will work on the patch implementation at the end of the week.
For beta 1, the team agreed that a robust technical implementation is needed, so we have a UI basis for this new feature. Then, the team will focus on phrasing and on polishing the interface elements.
@estelaris asked for documentation about plugins and themes auto-updates. The team shared all the existing documentation:
Technical documentation (WordPress 5.5 dev notesdev noteEach 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.):
You must be logged in to post a comment.