[wp-trac] [WordPress Trac] #22704: Automatic Core Updates

[WordPress Trac]

#22704: Automatic Core Updates
-----------------------------+------------------------------
 Reporter:  pento            |       Owner:  pento
     Type:  feature request  |      Status:  assigned
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  dev-feedback     |
-----------------------------+------------------------------

Comment (by DH-Shredder):

 Definitely in agreement that it seems appropriate to start from the minor
 and security upgrades for a first pass.

 From what I've seen, we have generally very low volumes of support (to
 none) when we run minor upgrades.  I'm sure that if these became automated
 in core, everyone committing would be even more careful about what goes in
 them.

 The biggest security concerns come from plugins, so it'd be good to have a
 solution that keeps them in mind for the future (perhaps a tag to let
 plugin authors specify an upgrade as a security update, which was talked
 about at the summit).

 As far as major release auto-upgrades go, I'm a fan of moving forward on
 them, but with this as a second or third step (likely at least two major
 releases forward from now).
 Plugins and themes need to be, at the very least, taken into account if we
 want to do them properly. As it's been talked about above, it'll be
 important to avoid auto-upgrades if it's going to cause a fatal error.
 This situation is the one we see most often when we auto-upgrade users,
 and generally speaking it's a problem because the users haven't kept their
 plugins up to date before the core auto-upgrade takes effect.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/22704#comment:15>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software