In reply to Ryan Hellyer.

Maybe track Plugin compatibility by major core version, rather than by minor version? That would make things quite a bit easier for Plugin developers to maintain.

The other thing is that such information needs to be de-coupled from the readme-parser jump to the latest Stable tag.

If, however, developers could simply update the compatibility tags in trunk, life would be much easier. Unfortunately, the parser looks for "stable tag", and if found, continues parsing not from trunk, but from the readme in the found stable tag. So, even if Plugin compatibility is updated in trunk, users won't see the change.

As it is currently, to update version compatibility, Plugin developers either have to modify an already-tagged version of the Plugin (non-optimal for proper version control; once it's tagged, it doesn't change), or release a point version just to update the compatibility information.

So, provide Plugin developers some way of providing Plugin meta data that is separate from the stable-tag readme file.