[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:21 Ipstenu]:
 > My biggest concern there would be miles of re-education.

 Is there really any there though? If it's a plugin using `trunk` that were
 opt'd in to using release confirmation (either now, or forced in future)
 they'd see no major change other than SVN commits that they didn't make
 after confirming a release - and that act of having to confirm the release
 IS the re-education step.

 > Second biggest is ... how does that take into account readme only
 updates for WP compat?

 Let's stop that behaviour then, make people actually bump their `tested up
 to` value by making it easier for them to do - anecdotally a lot of
 plugins don't bump them because it's not worth making a commit for it.

 All the other readme updates though.. FAQ, Screenshots, typos.. those kind
 of things make me think that the readme is really an `asset` or should use
 the `trunk` file and not the latest stable.. but then you have things like
 Changelogs in trunk which shouldn't be displayed until released, etc..

 My point is that it's a messy experience currently because of the old
 choices made, and we should consider whether we ''really'' need to have
 ongoing support for it.

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