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

 Moving forward, my initial MVP launch plan for next week:
  - Requires Release Confirmation
   - The UI will be presented as part of the RC confirmation, it's chosen
 at that time.[[BR]]
     The intention here is that it's an intentional choice by the plugin
 author for the plugin release.[[BR]]
     This is opt-in.
  - Two rollout options:
   0. (default) Full rollout: no staged/phased rollout.
   1. Delayed auto-updates: Update is released to all users, but auto-
 updates are delayed for 24hrs (timing TBC)
   2. Linear rollout: Release to ~2% of sites every hours (ie. by 48hrs
 it's at 100% - TBC Alternatively, 1% every hour for ~4days)
  - No feedback mechanisms, no stats, beyond what is already available to
 authors (Manually Monitoring Support Forums)
  - "Abort release" - Prior to the rollout above being finalised, a
 previously confirmed release can be reverted to as stable.

 Second iteration:
  - Experimentation on Feedback mechanisms, including any data w.org can
 already collect and #8032
    - This might include additional review statistics or support forum
 stats.
  - Some additional tooling for Plugin Admins / Plugin Reviewers to change
 anything about a plugins release strategy. Depending on feedback from
 those who use iteration 1.
  - Improvements in WordPress Core to enhance feedback and/or
 implementation.

 Third iteration:
 ''This is assuming that plugins have been making use of the feature, and
 it is providing value to plugin authors, and documentation is clear for
 all authors''
  - Enable a per-plugin selection UI for enabling this for all plugins,
 regardless of whether Release confirmation is enabled.
  - If Release Confirmation is NOT used, there is no abort release process.
 The abort release process is either a) Release a new version, b) Change
 the `Stable Tag:`. This is a limitation of using `readme.txt` data.

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