Plugin Versioning numbers
With the recent community involvement in releasing plugin versions to work around calibre changes in cases where the plugin maintainer is either absent from the forum, or the plugin has been abandoned, I've observed some version number conflicts.
Either an invalid version number (ie 1.2.3.4) as opposed to the calibre three part number (1.2.3), a reuse of the officially released plugins version number, or the use of a version number that the developer had intended for their next build but never publically announced on MobileRead.
Any thoughts on standards / techniques that could be implemented to handle these issues?
|