[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:  (none)
     Type:  enhancement       |      Status:  reopened
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-----------------------

Comment (by dd32):

 Replying to [comment:4 jsmoriss]:
 > Plugin authors received an email a while ago about updating their
 "Tested Up To" for 5.0. Should we not be using 5.0, even if the plugin is
 tested with the latest RC?

 You should be doing exactly that, as you've tested with 5.0.

 ----

 As stated by @Otto42, Having a `6.0 tested up to` ranks you much worse in
 search, it's effectively like saying "I'm tested with 4.0" when the
 current is 5.0. Heavy penalty in search results, possibly worse than not
 including a version.

 That all being said, changing how we import the number seems like a good
 idea to me.
 If it's higher than whatever trunk currently is, it can be safely
 discarded.
 While we're at it, we can also discard anything like `PHP 5.2.x, WordPress
 4.9, BuddyPress 1.5` too (That's a real example).

 Looking at the raw data for published plugins, it'd only affect ~50
 plugins who have future tested-up-to versions:
 {{{
 tested count
 9.9             20
 5.1             19
 6.0             5
 9.1             3
 5.5             3
 5.6             3
 }}}

 Those marked `5.5/5.6` I'm going to guess are actually PHP versions and
 the `9.9` is obviously a "I don't want to update this".

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