#5805 closed enhancement (maybelater)
Need to introduce Staged Rollouts for the Plugin and Theme Repository
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Component: | Plugin Directory | Keywords: | 2nd-opinion |
| Cc: |
Description
Staged Rollouts allow you to specify the number (or percentage) of websites that you want to roll out a new version to, it is nothing but limited exposure of the new update.
Benefits of Staged Rollouts?
Instead of risking the entire install base with the release of potential bugs, conflicts with 3rd party plugins/themes, or even UI/UX issues, we can release versions progressively, minimizing the number of people and websites that will get exposed to unexpected problems.
Read more information here.
https://freemius.com/blog/staged-rollouts-wordpress-plugins-themes/#wordpress_org_here_s_how_you_can_introduce_staged_rollouts_for_the_plugin_and_theme_repository
Note: See
TracTickets for help on using
tickets.
We already have staged rollouts when we need them, and we have had them ever since WordPress 3.7.
We don't need to implement these in the way that is described in that article, and we have no plans to provide tools like these to plugin or theme authors.
More to the point, unless auto-update is enabled, staged rollouts are essentially meaningless. Thus, we currently only use them for WordPress core security updates when necessary. If and when we move towards plugin and theme auto-updating, then these issues will make sense to discuss, but at present, they do not.