[wp-trac] [WordPress Trac] #50907: Add a method to opt-in to core auto-updates.

[WordPress Trac]

#50907: Add a method to opt-in to core auto-updates.
-------------------------------------------------+-------------------------
 Reporter:  whyisjake                            |       Owner:  (none)
     Type:  enhancement                          |      Status:  new
 Priority:  normal                               |   Milestone:  5.6
Component:  Upgrade/Install                      |     Version:  5.5
 Severity:  normal                               |  Resolution:
 Keywords:  early needs-patch needs-docs needs-  |     Focuses:
  unit-tests needs-design                        |
-------------------------------------------------+-------------------------

Comment (by johnbillion):

 Brain dump of the points about the actual update process that I raised
 during [https://wordpress.slack.com/archives/CULBN711P/p1600794037001500
 the meeting on Tuesday]:

 * What happens when a user or admin logs in for the first time after a
 major version auto update? Normally an admin would be redirected to the
 About page after clicking the big blue button. They could be in the middle
 of doing something in the admin area, or see the admin area change before
 they see the email notification.
 * Look at the possibility of a pre-release notification (email or admin
 area message) saying "WordPress will update to 5.7 in 7 days time". Would
 need something in the w.org API.
 * A minor update rarely has changes that are visible to users but a major
 could potentially mean a change in UI from one page load to the next.
 * Jonathan raised that "Most major updates have database upgrades to
 perform (though not all)".
 * If a Multisite installation opts in to automatic major updates, the db
 upgrade process still needs to be run on all sites on the network.
 * Hosts such as SiteGround auto update major releases on their managed WP
 hosting plans. It might be worth chatting further with the hosting
 community team to see if they have feedback from users around when major
 updates happen or find out what hosts do for major version updates.
 * Maybe also the Gutenberg team. If we think of the block editor as a
 long-running SPA it could need some work around delivering over the air
 client code updates in the same way that PWAs do, or forcing a reload of
 the page at the point where a major update happens.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50907#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform