[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 svovaf):

 Replying to [comment:35 dd32]:
 > Replying to [comment:31 svovaf]:
 > > We've implemented [https://freemius.com/blog/staged-rollouts-
 wordpress-plugins-themes/ staged rollouts for plugins at Freemius] about 5
 years ago and learned a ton from the process. It's an exciting capability
 with huge potential for the .org and greater WP ecosystem — happy to share
 our experience and help make this a reality!
 >
 > @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. If you don't count those into the rollout,
 then you can't guarantee the rollout's exposure. If you do count those,
 developers need to understand that it doesn't mean that now X% of sites
 are actually running the staged version—it just means they got the
 notification and can update. That nuance is important.

 Perhaps one way to optimize this, which just came to mind, is to
 prioritize delivery to sites with auto‑updates enabled. The downside of
 this approach is that the distribution of the rollouts wouldn't be random,
 and those sites would always be more favorable.

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