[wp-meta] [Making WordPress.org] #8009: Phased releases and roll-outs of plugins
Making WordPress.org
noreply at wordpress.org
Wed Sep 3 12:38:27 UTC 2025
#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 beccawitz):
This is a really exciting development! Thank you to everyone who has been
working on it. Gradual rollouts will be a huge step forward for plugin
stability and user trust, and we’re very appreciative of the effort that’s
gone into making this possible.
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.
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).
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
would give teams a chance to pause a release mid-rollout if issues
surface, before it reaches all users.
We’re really grateful for the work being done here, and we hope this
perspective from the large-plugin side is helpful as the feature evolves.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/8009#comment:50>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list