[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:                    |
------------------------------+---------------------

Comment (by dd32):

 > allows developers to roll out a release to a random subset first

 I can see a major confusion point for end-users here, when they see a
 plugin update on Site1, and not on Site2. Especially a problem when it's
 resolving a bug they're experiencing on both sites.

 I would suggest that staged rollout should be specifically only for auto-
 updates, which while I don't have the data to backup my opinion, I believe
 accounts for the majority of plugin updates today.

 Combining that with improved messaging in the core UI of when a site
 should update to the plugin (ie. the API says `"Update to v2.0 either by
 user clicking Update, OR automatically in +29hrs"`) I believe that concern
 would be adequately resolved.

 > gather feedback

 I feel that we're ''currently'' not in an ideal position to fulfil that
 need. Support forums are the obvious place for feedback, but I don't feel
 that most end-users '''(and authors)''' make the best use of it.
 Ensuring that we have a good feedback loop for both end-users and plugin
 authors would be needed to make the most of this.

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