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

 > I'm still fairly concerned that we don't have any reasonable ways for
 authors to really know that there's a problem. I'd like to hear more from
 Plugin Authors on how we can address that, or if it's really something
 we're not going to be able to begin to solve until after this feature has
 been used for a while.

 @dd32 Brief idea. I wonder if we could add some additional functionality
 to the WP Fatal Error Handler:

 - If stack trace on error can reliably match the fatal error path to an
 installed plugin path...
 - Match to a wp.org listing...
 - Send a package to a new endpoint with the error details, masking any
 sensitive details, and/or send email to plugin author.
 - Potentially make basic stats available to the plugin author on the count
 of fatal errors reported in the rollout with aggregate list of errors?

 This might require opt-in for sites. Also, this won't capture all the
 relevant errors and would also have to account for potential false signals
 - for example, another plugin with a compatibility issue actually is what
 shows up in the stack trace.

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