Implementing a plugin updater + dependency management + semantic versioning
#2
I still don't think it's the server's job to update plugins. What could make sense though is implementing it in a different plugin or in Core.

Though I don't really know what you want to do with that plugins.txt file. What would it be used for?

Also, I could understand people wanting to use "beta" or "alpha" in their plugin version. Are we going to rob developers from being able to do that?

Another thing we might want to consider is that some developers might want to use a fast lane or slow lane like with the Windows preview builds. The fast lane gets new features rather quickly, but it's possible that there are still bugs in there while the slow lane gets less features but is more stable.
Reply
Thanks given by:


Messages In This Thread
RE: Implementing a plugin updater + dependency management + semantic versioning - by NiLSPACE - 01-28-2016, 11:43 PM



Users browsing this thread: 1 Guest(s)