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

 Replying to [comment:27 dd32]:
 > In this case, nothing would need to be opt-in as the plugin releases are
 not intended on being "experimental" or unstable. It's the same stable
 release that the site owner would have to opt to installing. We're not
 suggesting forced beta updates for a segment of sites, or anything of the
 sort.

 I would just caution against assuming that every user of this feature will
 use it exactly as intended. The goal may not be to force beta updates on a
 segment of sites, and I'm sure the vast majority of plugin developers will
 not use it that way, but I would be surprised if ''no'' plugin developers
 ever use this feature as a replacement for a beta test or QA.

 > If an agency doesn't perform plugin updates (Either manually, or
 automatically) this won't affect them, as they won't update in the first
 place.

 Updating infrequently is not the same as never updating, given the number
 of sites served by .org and the number of plugins in the repository, it
 can be assumed that some small fraction of infrequently updated sites will
 end up being selected randomly if any significant number of plugin authors
 use this feature.

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