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

[Making WordPress.org]

#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 dd32):

 Replying to [comment:19 Ipstenu]:
 > > 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

 What's your thoughts on comment:6 from me:
 > I'd almost prefer to remove the ability to release from /trunk/
 entirely, and instead, add a UI button for "Release version x.y" that
 Checked the trunk files versions were correct, tagged it for them, and
 then updated the trunk Stable Tag readme field for them.
 > (That's complicated for other reasons, but I would totally support it
 and probably use it myself)

 That could be done through this email validation too - The approve-release
 option could trigger the make-a-tag action for trunk users and they'd
 realistically see no change in workflow, commit to trunk, get email,
 approve, tag happens. Remove their need to deal with `svn cp trunk
 tags/1.2` (since most do it badly anyway)

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