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

[Making WordPress.org]

#5652: Plugin Readme Header Spec Upgrade
------------------------------+---------------------
 Reporter:  pewgeuges         |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by pewgeuges):

 @Otto42

 The Plugin Review Team starting seeing the 3 added lines in submitted
 plugins’ readme headers is the expected outcome.

 Your convoluted and sibylline response resulted IMO from a lack of
 precision in the ticket description as I posted it.

 If the permission to add custom fields in the plugin readme header can be
 inferred from https://developer.wordpress.org/plugins/wordpress-org/how-
 your-readme-txt-works/#custom-sections without overstretching the
 allowance for custom sections in the readme body, then why not add these
 to the spec since the Package Version and Tagged Version are useful
 information. This information needs to be provided in a place that users
 can be expected to look up, and that can be accessed remotely. If hiding
 this information is intended, that should be stated in the spec.

 As of the comment line, it has become indispensable in Footnotes’ readme
 header after v2.5.10, and it needs to be in all caps there, while other
 projects may use lowercase; they may drop it only if they can guarantee
 being maintained by professionals long-term.

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