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

[Making WordPress.org]

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

 Replying to [comment:8 Otto42]:
 > Mmmm.. not really a big fan of this approach. I would rather there be
 consequences of using invalid data. By ignoring it or overly sanitizing
 incorrect data, then this eliminates that penalty in the search rankings
 we talked about above.

 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.

 I'll pull a list of affected plugins today, along with some information
 about each and you can decide for yourself if it's really a problem.

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