[wp-meta] [Making WordPress.org] #7641: Allow specifying `Tested up to` without changing the plugin

[Making WordPress.org]

#7641: Allow specifying `Tested up to` without changing the plugin
------------------------------+-------------------------
 Reporter:  dd32              |      Owner:  (none)
     Type:  feature request   |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:  2nd-opinion
------------------------------+-------------------------
 Many plugins get stuck in an endless loop of making a new release every
 WordPress release to mark their plugins as `Compatible with WordPress
 x.y`, this is also required to avoid the `This plugin hasn't been updated
 in more than 3 releases` banner.

 I'd like to propose that we allow plugin authors to set the `Tested Up To`
 value without making a new plugin release. This would be done through a
 plugin banner `"Have you tested your plugin with WordPress x.y? Mark it as
 Tested"` when the value is outdated. It could also offer something like
 `"No? You can close your plugin if it's no longer supported."` if it's
 more than 3 releases out of date perhaps.

 This would allow:
  - More plugin authors to mark their plugin as compatible, even if it
 didn't require any code changes
  - Less plugin releases which are simply due to requiring changing 1-3
 characters in their readme
  - A higher likelihood that a plugin author will close their plugin, if
 it's no longer compatible, and they have no intention to update it ever.

 WordPress Core doesn't currently do anything 'special' with the value
 within readme.txt or the plugin header, although 3rd party tools may. The
 only time the field is used is during plugin updates.

 I would still expect a plugin author to bump the version in their plugin
 if they make a release.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7641>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org