[wp-meta] [Making WordPress.org] #3936: limit "Tested up to" plugin header to current stable release

Making WordPress.org noreply at wordpress.org
Wed Nov 21 00:07:02 UTC 2018


#3936: limit "Tested up to" plugin header to current stable release
------------------------------+-----------------------
 Reporter:  littlebizzy       |       Owner:  dd32
     Type:  enhancement       |      Status:  reopened
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by littlebizzy):

 Having no tested up to is a penalty, a fairly large one. Not only does it
 mean that they'll get ranked down in the search results (IIRC, far more
 than just having it set to 10 versions away from current) but they'll also
 get "Unknown Compatibility" warnings inside WordPress on the install
 screens and update screens - where as previously they got a great big "All
 good! Compatible!", that'll also cause more support requests asking if
 it's compatible (Yes, that does happen).

  The sanitisations done can be removed if wanted, but they add so little
 overhead and protect developers who thought they were doing it right, but
 weren't - as we never enforced any form of sanity in the fields.

 This all sounds as perfect as can be.

 Dishonest, lazy, or irresponsible plugin authors get penalized in search
 results, while end users are protected from confusion and misinformation.
 Organization and clarity is also improved... and `Unknown Compatibility`
 errors will encourage end users to ask plugin authors for answers, so the
 whole thing self-regulates.

 Overall it should create more "honest" competition in the directory.

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


More information about the wp-meta mailing list