Please use this thread if you have questions regarding the MediaPortal 1 Development - get involved! news.
I highly recommend that everybody gets involved in getting us a https://forum.team-mediaportal.com/general-development-no-feature-request-here-48/native-blu-ray-support-102375/#post808004. That would be a cool feature to have!
I am sorry, but this sounds like a terrible idea:
1) It is highly likely that a new feature/bug submission will interfere with contributions by other developers. So testing an installer for changes from just a single developer does not seems like a good idea.
2) If people have the time to test every single installer a developer publishes (and I presume there would be lots of those floating around once this comes out), then they are most likely developers themselves. Hence, this makes this whole thing kinda redundant.
I think you guys should implement a system that is known to work. Have a look at any random open source project that is highly successful, e.g. Firefox. There are a handful of branches that testers can play with and provide direct feedback. This makes development much more manageable and feedback more meaningful.
I am sorry, but this sounds like a terrible idea:
1) It is highly likely that a new feature/bug submission will interfere with contributions by other developers. So testing an installer for changes from just a single developer does not seems like a good idea.
2) If people have the time to test every single installer a developer publishes (and I presume there would be lots of those floating around once this comes out), then they are most likely developers themselves. Hence, this makes this whole thing kinda redundant.
I think you guys should implement a system that is known to work. Have a look at any random open source project that is highly successful, e.g. Firefox. There are a handful of branches that testers can play with and provide direct feedback. This makes development much more manageable and feedback more meaningful.
...Remember this is for people who want to help, and have means to setup and test outside of a production machine, no one wants to screw up a working MP install that a user relies on.
More people testing something, the higher likely hood of coming across a scenario where a fault shows up.
This is voluntary, not compulsory