My stance is I would rather not have the beta version support an alpha version of Kodi at all. I don't mind supporting the repo if someone is willing to tell me how to. Will sort itself out in time when Jarvis hits RC I guess. Interesting idea, unfortunately I don't think anyone on the team wants to have to manage yet another repo, are you volunteering to build, release and support an Alpha repo? That might be doable if you want to take that on. Just adding support for the DB file version is not the same thign as testing all regressions and supporting all features. Yes the addon is being updated but it is not being fully tested, that is why it is not supported. People can use whatever version they want, but they will get mixed results with Kodi 16. Nope, its not supported until it hits RC and then only in our Beta version of the addon. So the situation for quite a few of us is we have to run on Jarvis if we want the latest and greatest from the most popular skin.
KODI 15.2 ISENGARD BUILDS APK ENGLISH SKIN
One of the reasons so many emby users are using Jarvis is because the Arctic Zephyr skin is only being updated for Jarvis. Right now your beta users for Isengard are getting plugin updates they are applying where the only change to the plugin is for Jarvis users. I get that it is an alpha product, so let's have an aloha repo. It would be much simpler if it said "Sorry, this plugin is not compatible with jarvis" and force the Jarvis to use an Alpha repo. Especially when the plugin itself works with Jarvis and is being updated to work with Jarvis. Just because we are saying its not supported doesn't mean people are not using it, and it means we have to continue to help people that have issues with it. But again, it is not suggested to use Jarvis because things will break, since they modify their database schema often until RC release. If you are using Jarvis, only im85288 is updating it for the nightly build, for himself. No where does it mention that we officially support Jarvis. It's mentioned here in this forum(pinned threads) and in our wiki. We only support Helix and Isengard for both stable and beta version of our add-on. So basically, don't use Jarvis until we officially announce that we support it, you will never have a problem. But again, it is not suggested to use Jarvis because things will break, since Kodi modify their database schema often until RC release. We only support Helix and Isengard for both stable and beta version of Emby for Kodi add-on (Emby sync server plugin has nothing to do with this). Right now I don't believe we have that unless people read through the main thread. It would be easier for me to say ok you are on version 1.44, that requires Alpha 4 or newer. Since the release notes never specifically state which Kodi Version it works with you end up sometimes having to apply multiple dailies until you figure out which kne it works.įrom a daily support standpoint we get questions daily on specific versions and what works with what.
I think somewhere we should plainly document that Isengard is supported with the Stable EmbySync release, and that the beta EmbySync only works with Kodi 16 Alpha 4. There is nowhere that it is clearly layed out on what version supports what. The problem is the same one I have mentioned since day one when we started testing this.
0 kommentar(er)
