[wp-meta] [Making WordPress.org] #5352: Plugin Security - Add email confirmation prior to releases being processed

Making WordPress.org noreply at wordpress.org
Wed Aug 12 17:55:00 UTC 2020


#5352: Plugin Security - Add email confirmation prior to releases being processed
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |
------------------------------+---------------------

Comment (by Ipstenu):

 So basically half of ALL plugins use trunk. Ew.

 > When I say it makes it a lot simpler, I really mean it's a lot simpler
 (to the point, that I actually consider it a requirement), the edge cases
 that need to be handled are significantly decreased and errors on
 WordPress.org would be significantly reduced.

 Okay. Then we need to figure out how to get the half of plugins to do it
 :D

 >> We can also say "disable auto updates for plugins using trunk as
 stable" though I don't know if the API (as is) is robust enough to handle
 that. It's something we should consider.

 > The API is, but it won't be a good user-experience as core
 implementation isn't robust enough for it.

 Maybe we tackle that first. "Plugins that use trunk are not eligible for
 auto-update because we can't be sure you're getting the right version."
 It's not a GREAT user experience, but it's actually considering their
 needs first, which is we don't want to break sites.

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


More information about the wp-meta mailing list