[wp-meta] [Making WordPress.org] #8009: Phased releases and roll-outs of plugins

[Making WordPress.org]

#8009: Phased releases and roll-outs of plugins
------------------------------+---------------------
 Reporter:  matt              |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |
------------------------------+---------------------

Comment (by dd32):

 Replying to [comment:38 svovaf]:
 > Replying to [comment:35 dd32]:
 > > @svovaf We're definitely interested! Are you able to share any initial
 gotcha's that surprised the team? Or surprised Freemius customers?
 >
 > Not exactly a "gotcha", but more of a realization: in the context of WP,
 when a staged rollout update is delivered to a given site, there's no
 guarantee it will be installed.

 100%, this is the biggest issue with this staged rollout proposal in my
 mind - There's no guarantee that any staged/phased rollouts will actually
 get installed, and then actually get used in any form by the site (ie.
 editor-related plugin, are they going to publish on that Tuesday, or do
 they only write & publish every Friday?)

 Ozz's approach above of basing the staged rollout upon the actual number
 of sites that install the update is IMHO reasonable because of this, but
 given that the site might "sit on" the update being delivered to them for
 up to 12 hours (or more) is what rules this approach out for me, as by the
 5k installed time 50k could be sitting on the update waiting to install it
 later.

 > prioritize delivery to sites with auto‑updates enabled.

 Unfortunately WordPress.org doesn't have this data-point, and even then,
 there's plugins/filters which can alter it (ie. install point releases,
 not major releases)

 This is one data-point which we can consider looking at ways to improve
 the data sent through to .org from core, whether the site has auto-updates
 enabled for a given plugin.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8009#comment:39>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org