This has become a bit of a concern for me with the upcoming beta for v2.0 of the API. The problem is simple: if someone wants to know what version of the API a library is compatible with (or at least makes use of), they need to either visit the library's page or look a the source code (since not every library advertises the version it uses).
A similar problem (listing libraries by language) was tackled by creating this post. I'm not sure how to approach this problem, but I've come up with some suggestions:
- Use tags. This option seems to be the best, since it makes searching for libraries that match a given version simple. In fact, one could even search for those libraries by version using the API itself. The downside of this is that comparitive searching is difficult. If you want to find all libraries that uses v1.1 or newer, then you must use all of the tags for newer versions ([v1.1] and [v2.0]). Beta releases of the API make this even harder.
- Create another question. We could create a 'list of libraries by API version' post that lists each API version followed by the libraries that make use of it. The problem with this approach is constantly updating a certain question and the risk that it might omit some library or be out of date. It would also require that each new user listing a library be informed about the post.
- Create a "special meta-attribute". Similar to how the thumbnails and version are stored in the question, we could perhaps add a meta-attribute to the libraries that indicate the version of the API that the library was developed against. This would require the team to add support for the attribute and perhaps create a page or something that allows us to browse the data.
So what does the community think? Which of these approaches is best? Which one would make it the easiest to search for libraries?
