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

 Replying to [comment:50 beccawitz]:
 > From the perspective of a large-scale plugin like Elementor, we wanted
 to share a couple of thoughts. In the current design, only plugin
 committers/admins can manage these phased releases. For security reasons,
 we keep that group very small, which means every release would need to be
 funneled through just a couple of people. That creates a bottleneck that
 makes it difficult for us to realistically use this otherwise great
 feature.

 I think this bottleneck is intentional and required.

 Only committers can commit a release, and only committers should approve a
 release, as such, only committers should be able to set the phased release
 settings. Those settings can't be changed once a release is confirmed.

 This isn't separate to "creating a release of the plugin".

 > One idea that could help would be to introduce a dedicated role, such as
 “Release Manager,” who would have the specific ability to create and
 manage phased rollouts, without having the broader and higher-risk
 permissions that committers have (like deleting plugins).

 This IS something that we could look into however, although, it'd likely
 be more open than you're suggesting.
 Specifically, adding `Plugin Maintainers` or something similar that has
 full access to manage the plugin, but doesn't have SVN commit access. This
 would be useful for cases where authors have a CI/CD process which is the
 only user that needs SVN access.

 It's worth noting that destructive actions like plugin closure are limited
 to plugins with less than 10k active installs.


 > Additionally, it could be very valuable if release managers had the
 ability to stop or freeze a rollout during the 24-hour timer window.

 This is a planned feature, just wasn't implemented in the initial release.

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