home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
General Forums
News and Announcements
MediaPortal 1 Development - get involved!
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="messo001" data-source="post: 821704" data-attributes="member: 96320"><p>I am sorry, but this sounds like a terrible idea:</p><p></p><p>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.</p><p></p><p>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.</p><p></p><p>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.</p></blockquote><p></p>
[QUOTE="messo001, post: 821704, member: 96320"] 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. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
General Forums
News and Announcements
MediaPortal 1 Development - get involved!
Contact us
RSS
Top
Bottom
