Implementing a plugin updater + dependency management + semantic versioning
#9
I think the plugin updater should be implemented in a separate plugin, and it should be tied to the plugin repository. The plugin repository should really keep track of the versions and whether they are "beta" or "release" grade; the updater will have a per-plugin setting which grade to use.
As for version numbers, I still think a single number is the best solution, like in Android; the plugin repository would have the database of which version numbers are considered "release grade". It makes comparisons simple, no library is needed. It could even be made so that the actual plugin has no knowledge of the version number, only the updater and the repository keep track of those.
Reply
Thanks given by:


Messages In This Thread
RE: Implementing a plugin updater + dependency management + semantic versioning - by xoft - 01-29-2016, 08:51 PM



Users browsing this thread: 2 Guest(s)