In the past we have had issues with plugins being incompatible with newer versions of MediaPortal due to some breaking change in MediaPortal itself. While we always try to avoid doing changes that break existing plugins, sometimes we just have to do it in order to solve some issues properly. This has caused frustration for the users and a lot of wasted time for the team trying to process bug reports that were the result of those breaking changes.
Recently there was a breaking change that requires that all plugins be rebuilt against the new version of MediaPortal. We are now taking the opportunity to implement a version compatibility system that will ensure that in the future incompatible plugins will be automatically detected and disabled, providing a smoother upgrade experience and less wasted time for the Team.
The new version compatibility system has been already implemented for the most part, but it requires that we categorize MediaPortal functionality/APIs into subsystems. Since MP1 has no defined API and plugin developers pretty much use whatever they find suitable for the task, it is really hard for us to do the categorization in a meaningful way. This is why we are asking for the help of the community to make proposals and have an open discussion.
IMPORTANT: Before you post please read the description of how the new Version Compatibility system works in our wiki page: Version Compatibility - MediaPortal Wiki
I also would like to point out that each subsystem should correspond to extisting MP functionality and needs to be unambiguously defined. We are planning to start by defining the subsystems coarsely in the first version then later on we can refine the categorization by extending the subsystem hierarchy adding more levels.
Thanks,
Arion
Recently there was a breaking change that requires that all plugins be rebuilt against the new version of MediaPortal. We are now taking the opportunity to implement a version compatibility system that will ensure that in the future incompatible plugins will be automatically detected and disabled, providing a smoother upgrade experience and less wasted time for the Team.
The new version compatibility system has been already implemented for the most part, but it requires that we categorize MediaPortal functionality/APIs into subsystems. Since MP1 has no defined API and plugin developers pretty much use whatever they find suitable for the task, it is really hard for us to do the categorization in a meaningful way. This is why we are asking for the help of the community to make proposals and have an open discussion.
IMPORTANT: Before you post please read the description of how the new Version Compatibility system works in our wiki page: Version Compatibility - MediaPortal Wiki
I also would like to point out that each subsystem should correspond to extisting MP functionality and needs to be unambiguously defined. We are planning to start by defining the subsystems coarsely in the first version then later on we can refine the categorization by extending the subsystem hierarchy adding more levels.
Thanks,
Arion