[wp-trac] [WordPress Trac] #12317: Plugin Compatibility Missing for 2.9, 2.9.1, etc.

[WordPress Trac]

#12317: Plugin Compatibility Missing for 2.9, 2.9.1, etc.
---------------------------+------------------------------------------------
 Reporter:  miqrogroove    |       Owner:  mdawaffe          
     Type:  defect (bug)   |      Status:  assigned          
 Priority:  high           |   Milestone:  WordPress.org site
Component:  WordPress.org  |     Version:  2.9.2             
 Severity:  normal         |    Keywords:                    
---------------------------+------------------------------------------------

Comment(by mdawaffe):

 We now filter plugin author supplied data (in the form of the "tested up
 to" datum in the plugin header) through the equivalence class information.

 So if a plugin author has "Tested Up To: 2.9.1" in the plugin header,
 api.wordpress.org and the plugins directory should say the plugin is
 "Tested Up To: 2.9.2"  (... which is obviously a lie).  This equivalence
 is meant to reduce author burden; authors don't have to edit their readme
 every time a minor release comes out.

 The user submitted compatibility data (collected on the plugins directory
 site) is not aggregated by equivalence class: 2.9, 2.9.1, 2.9.2 are
 separate again.


 Replying to [comment:3 miqrogroove]:
 > This is not a good strategy for Plugin Compatibility.  There are plugins
 that are version locked and will not activate if the version number
 changes for any reason.

 Can you give some in-the-wild examples?

 If this auto-equivalence-mapping is problematic, we could make it opt out:
 "Tested Up To: 2.9!" or something.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12317#comment:4>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software