gPodder Bug Tracker – Bug 1273
Extend current API Versioning Scheme with minor Version Numbers
Last modified: 2011-02-08 08:51:40 CST
As discussed on the Mailinglist: https://lists.berlios.de/pipermail/gpodder-devel/2011-January/002683.html
-) Increment Minor Version for every API Change ( and document for every API Endpoint when it was introduced or last time changed
-) Document Changes in the API in a "Version History" on the Wiki Page of the API Specification
-) Wishlist: Create a new API Endpoint which returns the current API Version
I have added version numbers to all API Endpoints. Additionally a changelog is provided at
If you notice any missing entries or inconsitencies, please reopen or file a new bug.
I did not provide an API endpoint that returns the current version as this should be transparent to a client. It should never have to check for a version is it should have been written against one API version and newer versions will preserve backward compatibility anyway.
If you have a specific use case for such an endpoint, please file a new bug for it.