I've built a local copy just now of 3.1 and by chance I'd tried to install the demo addins and noticed they didn't work due to a version mismatch (3.1 > 3) - while I don't think the user version string should be tied to API most people don't see, it looks like that's implicitly kind of the case at the moment and there probably is some need to disconnect the Addin API version from the user version so that simple bug fixes to the UI don't instantly invalidate an entire ecosystem and put people in a position they can't upgrade (especially when a lot of package managers are keen to).
Right now it's probably not that important since there's effectively none, but going forward if Addins were expected to thrive, they'd need some guarantees and the initial release of 3.0 being the first release in years to have them seems like an ideal point to make an "Addon API 1.0" officially.
Originally posted by @JGCarroll in #693 (reply in thread)
I've built a local copy just now of 3.1 and by chance I'd tried to install the demo addins and noticed they didn't work due to a version mismatch (3.1 > 3) - while I don't think the user version string should be tied to API most people don't see, it looks like that's implicitly kind of the case at the moment and there probably is some need to disconnect the Addin API version from the user version so that simple bug fixes to the UI don't instantly invalidate an entire ecosystem and put people in a position they can't upgrade (especially when a lot of package managers are keen to).
Right now it's probably not that important since there's effectively none, but going forward if Addins were expected to thrive, they'd need some guarantees and the initial release of 3.0 being the first release in years to have them seems like an ideal point to make an "Addon API 1.0" officially.
Originally posted by @JGCarroll in #693 (reply in thread)