Upgrade/Install Component meeting summary – November 10, 2020

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 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-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 meeting was focused on the component’s major project for 5.6: an UIUI User 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 ticketticket Created 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 BetaBeta A 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 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., 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.
    • @helen and @karmatosed to iterate on the design/copy.

@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.

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

Upgrade/Install Component meeting summary – October 13, 2020

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 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-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 meeting was focused on the component’s major project for 5.6: an UIUI User interface for opting in to core auto-updates: #50907.

@audrasjb sent a first 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. 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 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 or by using the existing hooksHooks 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. or PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 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 accessibilityAccessibility 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) would need to be tested and reviewed. It doesn’t look realistic for WP 5.6 BetaBeta A 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:

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

Upgrade/Install component bug scrub for WordPress 5.6

As part of the 5.6 release, we’ll be hosting a Upgrade/Install focused bugbug A 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. scrub this Thursday, September 17, 2020, 18:00 UTC in the #core-auto-updates channel on 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/..

They are many tickets for this component that will need feedback and help to move forward, as part of WordPress 5.6 release cycle.

During the scrub, we’ll go through this TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. report:

https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&type=defect+(bug)&component=Upgrade%2FInstall&group=priority&col=id&col=summary&col=type&col=status&col=owner&col=priority&col=milestone&order=id

That report contains all tickets for this component of type defect (bug). We’ll be starting with the oldest tickets first, with the goal of seeing if we get any of these old tickets to land in 5.6.

#5-6, #bug-scrub, #upgrade-install

This is a summary of the shiny updates…

This is a summary of the shiny updates chat from May 31. (Slack log)

Attendees: @ocean90, @swissspidy, @mapk, @afragen, @screamingdev, @ipstenu, @obenland

Topics:

  • Merge plan
    @swissspidy will have a merge proposal ready for review and publish on 6/2. Friday, 6/3, was set as the deadline for code changes so that there will be enough time to prepare 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. prior to next weeks Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. meeting.
  • Overall status
    We discussed various options around how to display a notice on update-core.php when there are no updates pending. The issue of dismissible updates was brought up, and whether that could be deprecated. That should be brought before a bigger audience at the next dev chat. Allowing 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 installations from import.php came up as well; we need to find a solution there and make the experience better. We ended with discussing implementation details of various open tickets, that don’t have an effect on the bigger picture

Next meeting is on Tuesday June 7, 20:00 UTC.

#4-6, #shiny-updates, #upgrade-install

This is a summary of the shiny updates…

This is a summary of the shiny updates chat from May 24. (Slack log)

Attendees: @ocean90, @swissspidy, @mapk, @ryelle, @melchoyce, @adamsilverstein, @obenland

Topics:

  • Open Pull Requests
    • @swissspidy was waiting for feedback and a merge on PR120, which happened right after conclusion of the meeting.
    • @ryelle was waiting for clearance to re-globalize pagenow in order to make more parts of shiny updates testable.
  • Overall status
    We should be at a point where we can write the merge proposal and a 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. in the coming week. We have one more week to fix more bugs and get some more user eyes on update-coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and themes. @ocean90 mentioned two core tickets that should be fixed before merge, #13071 and #36914 and asked for review and testing there.

Next meeting is therefore on Tuesday May 31, 20:00 UTC.

#4-6, #meeting, #shiny-updates, #upgrade-install

Shiny Updates Chat Summary 5/17/16

This is a summary of the shiny updates chat from May 17. (Slack log)

Attendees: @ocean90, @swissspidy, @j-falk, @mapk, @ethitter, @obenland

Topics:

  • Accomplished work since last week
    • Review requests were posted to the AccessibilityAccessibility 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), Flow, Polyglots, and Design teams.
    • The feature project landing page was written and published.
    • @swissspidy merged update-core.php into master.
    • Lots of bugbug A 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. fixes and smaller enhancements went in.
  • Activate after install
    We discussed what the best way would be to provide users with the ability to activate a 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 after it was installed. @swissspidy offered to work on a way that would switch the install button to an activation link after the install queue emptied, so it can be user tested for a more informed decision.
  • Update coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
    @swissspidy‘s update-core work was merged into master, where it will remain to receive a broader test coverage than it would in a branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. All updates (except for ‘update all’ button) work via ajax.
  • Open floor
    We decided on a new meeting time, 20:00 UTC, that is one hour later than before.

Next meeting is therefore on Tuesday May 24, 20:00 UTC.

#4-6, #shiny-updates, #upgrade-install

Shiny Updates Chat Summary 5/10/16

This is a summary of the shiny updates chat from May 10. (Slack log)

Attendees: @ocean90, @swissspidy, @paaljoachim, @j-falk, @mapk, @obenland

Topics:

  • Accomplished work since last week
  • Remaining work
    The landing page for feature projects still needs to be written, as well as contributor groups asked to review Shiny Updates. @ocean90 opened a few issues that need addressing as well. These things should all be done by the time of the next meeting though.
  • Activate after install
    Shiny Updates introduced a disconnect between installing a 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 then activating it. @mapk offered to solicit more UXUX User experience feedback to address what happens when there are plugin install request in the queue while the user wants to activate a plugin, and how WP signals a successful installation while changing the button action to Activate.
  • Open floor
    …was mostly spent on discussing approaches to update-core.php and inconsistencies between the theme and plugin install UIUI User interface.

Next meeting is on Tuesday May 17, 19:00 UTC.

#4-6, #shiny-updates, #upgrade-install

Shiny Updates Chat Summary 5/3/16

This is a summary of the shiny updates chat from May 3. (Slack log)

Attendees: @ocean90, @swissspidy, @ethitter, @adamsilverstein, @mapk, @obenland

Topics:

  • Accomplished work since last week
  • Remaining work
    @obenland will work on the Shiny Updates landing page for feature projects and fix a bugbug A 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. that were discovered during the most recent user test. @mapk offered to conduct another user test focused on the new interactions with some learnings from the previous one. Goal is to identify any hiccups or behaviors that are unexpected to users. @swissspidy wants to continue working on update-core.php and see if we can get it into shape for 4.6.
  • Most recent user tests
    We briefly talked about the most recent user test (linked above). It showed a variety of bugs that @obenland initially assumed were based on being in subviews of the 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 list. After the meeting it turned out that the test site ran an outdated version of WordPress that didn’t include some of the date that Shiny Update needs to work. It was a good demonstration of progressive enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. here though, as all actions still worked, they just weren’t shiny. More user tests to come, to make sure that users agree with the new interactions.
  • Schedule for 4.6 inclusion
    Next up is writing the merge proposal that was requested to be published around 6/1, definitely before 6/8.

Next meeting is on Tuesday May 10, 19:00 UTC.

#4-6, #shiny-updates, #upgrade-install

Shiny Updates Visual Records

https://make.wordpress.org/flow/2016/05/02/shiny-update-visual-records/

#4-6, #shiny-updates, #upgrade-install

Shiny Updates Kickoff for 4.6 Chat Summary

This is a summary of the shiny updates chat from April 26. (Slack log)

Attendees: @ocean90, @swissspidy, @ethitter, @adamsilverstein, @karmatosed, @obenland

Topics:

  • Remaining work
    On the updates-core.php side there is quite a bit of work remaining. On the 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 management part outside of that, there is actually fairly little work remaining.
    Since the two parts vary in their readiness so much, it was proposed to go ahead with the theme/plugin management part and propose that for 4.6, while leaving the rest to be continued to be iterated on.
  • More user tests
    @obenland will reach out to @mapk and @karmatosed to get a final round of user tests in, to make sure the new workflows are up to par.
  • update-core.php changes
    Autoupdate settings will be pulled as they are not ready to be worked on yet. @swissspidy volunteered to work on #5, mainly merging the three tables and adding JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. handlers for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and language updates.
  • Schedule for 4.6 inclusion
    Core 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. should be ready by June 1 for merge on June 8. The remaining time is for creating visual records, user tests, and a merge proposal.

Next meeting is on Tuesday May 3, 19:00 UTC.

#4-6, #shiny-updates, #upgrade-install