[wp-meta] [Making WordPress.org] #5652: Plugin Readme Header Spec Update

[Making WordPress.org]

#5652: Plugin Readme Header Spec Update
--------------------------------------+---------------------
 Reporter:  pewgeuges                 |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  Plugin Directory          |  Resolution:
 Keywords:  has-patch needs-approval  |
--------------------------------------+---------------------

Comment (by pewgeuges):

 @dd32,

 The relevant part of your reply is about #5484, but the click-and-release
 button automation still relies on parsing the Stable Tag.

 To dismantle the danger originating from the Stable Tag, you just need to
 make it more intuitive by adding a field for the package version in case
 it differs, and a warning to raise awareness that the unconcerned readme
 is actually a configuration file, to the attention of developers joining
 in from other backgrounds. WordPress relies on volunteers, so please make
 it a bit less unwieldy and more intuitive for newcomers hurrying to help
 out while engaged elsewhere.

 What is the cost for you and the PRT/PD when updating the WordPress Plugin
 Readme Standard?

 Replying to [comment:11 dd32]:
 > I still disagree with the intention of this ticket though.

 Would you please elaborate upon your disagreement, please?

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