[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:25 azaozz]:
 > Right, has to be fixed in core. The API should be able to set whether to
 do an auto-update. Thinking this would be a fairly simple enhancement.

 Oh, Turns out this is already a feature of the API, via #core50824 - I had
 completely forgotten this existed and it's not documented in the API
 code..
 Unfortunately the flag is completely broken between WP 5.5-6.5 (despite
 being realised shortly after addition), and so it can only be used in
 WordPress 6.6+ #core52796

 So yes, we can totally disable auto-updates for the first 24hrs of a
 plugin release for a significant portion of sites without any core changes
 and minimal WordPress.org changes.

 > I kind of imagine something like this: on clicking "Report a (plugin)
 problem" a modal opens with the site health info pre-filled. The user will
 be able to add few words to describe it. Submitting it would go through
 their WP install (TBD, but seems preferable not to be directly to wp.org;
 privacy, etc. and there can be filters for plugins to access it) and WP
 will send it through the API.
 >
 > Then these semi-automated reports can be visible only by the plugin
 authors, not public so they are unattractive for spammers. Or perhaps we
 can try to aggregate some of the data and post to the plugin's support
 forum so other users are aware (if they ever look there..).

 I think this is a reasonable approach, and mostly what I was thinking.
 This could also be combined with the before-mentioned Fatal errors
 collection.
 This is probably best as a separate Meta ticket though (@azaozz Would you
 like to write one up?), maybe prior to being a core ticket, as the
 majority of the work concerns WordPress.org.
 I do have a [https://github.com/wordpress/wporg-experiments-plugin wporg-
 experiments-plugin] that was intended as a testing ground for this kind of
 `WordPress <=> WordPress.org` interoperability things.

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