[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 ariel.k):

 Thanks @matt for starting this proposal.

 As a plugin developer with millions of active installs, we’re really
 excited about this idea and would love to be involved. Right now the
 plugin repo has ~70 plugins with 1M+ active installations, and we think
 that with their wide reach they also could benefit greatly from a more
 controlled rollout configuration.

 I don’t know exactly how things work behind the scenes on wp.org, so I
 can’t weigh in on the technical side. But we agree with @dd32 that
 starting with auto-update users sounds like the right move, and we can
 then see how that goes.

 About the percentage-based rollout that @Otto42 mentioned, I think it’s
 also a good starting point. I’d suggest adding a few more options,
 inspired by the Apple and Android rollout processes.

 For example:
 1. **Immediate rollout** - This would be the default. Best for patches,
 security fixes, or anything small and urgent.

 2. **Balanced rollout** - For regular major or minor versions that are
 well tested but still might have some regressions: Day 1: 25% > Day 2: 50%
 > Day 3: 100%

 3. **Phased rollout** - For high-impact changes, major refactoring, new
 APIs, or UI overhauls: Day 1: 10% > Day 2: 25 > Day 3: 50% > Day 4: 100%

 The idea is to finish the rollout within one work week. So if a release
 starts on Monday, it should reach everyone by Friday. That way, problems
 don’t spill into the weekend.

 I’m really excited about how this approach can help improve stability and
 reliability, especially for end-users.

 Thanks

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