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
MediaPortal 1
MediaPortal 1 Talk
The hell of versions and SVN's
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="tourettes" data-source="post: 366721" data-attributes="member: 10858"><p>MediaPortal 1.0 was in feature freeze (bug fix mode) over a year and to get rid of the all bugs would have taken another one at least. This is something that was considered to take too long. Maybe 1.0 should have been released as 0.9 <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Current architecture makes the bug fixing really slow and hard, thats why the MediaPortal II is in progress. </p><p></p><p></p><p></p><p>Forced or not. Only way to stop them to be forced is to disable the SVN build completely, but this wont help the MP itself.</p><p></p><p></p><p></p><p>I hope you understand that we are talking on completely two different projects. One is big, has huge developer base (even companies are paying for developers to write the code on Firefox side). Other one (MediaPortal) has only handful of developers, but the code base is almost equal on the size.</p><p></p><p>Only way how those 1.0 patches would be possible would be that so group from the users are willing to do two things</p><p></p><p>1) Start another SVN trunk where some skilled developer(s) are back porting the 1.0.x fixes. This is not an easy task as you simply cannot pick the wanted changes from other trunk and merge those and cross your fingers and hope that it works.</p><p></p><p>2) Create QA team that are testing the 1.0 patched trunk and make sure that the back ported fixes work and don't cause any new issues. (all 3rd party plugins would need testing as well as its easy to break plugin compatibility with MP)</p><p></p><p>So, any volunteers? Team doesn't have any resource for such... Of cource there is still that possibility that the 1.0 patched would contain even more severe bugs than the original 1.0 (smaller tester base, inexperienced developers on MP source code...)</p></blockquote><p></p>
[QUOTE="tourettes, post: 366721, member: 10858"] MediaPortal 1.0 was in feature freeze (bug fix mode) over a year and to get rid of the all bugs would have taken another one at least. This is something that was considered to take too long. Maybe 1.0 should have been released as 0.9 :) Current architecture makes the bug fixing really slow and hard, thats why the MediaPortal II is in progress. Forced or not. Only way to stop them to be forced is to disable the SVN build completely, but this wont help the MP itself. I hope you understand that we are talking on completely two different projects. One is big, has huge developer base (even companies are paying for developers to write the code on Firefox side). Other one (MediaPortal) has only handful of developers, but the code base is almost equal on the size. Only way how those 1.0 patches would be possible would be that so group from the users are willing to do two things 1) Start another SVN trunk where some skilled developer(s) are back porting the 1.0.x fixes. This is not an easy task as you simply cannot pick the wanted changes from other trunk and merge those and cross your fingers and hope that it works. 2) Create QA team that are testing the 1.0 patched trunk and make sure that the back ported fixes work and don't cause any new issues. (all 3rd party plugins would need testing as well as its easy to break plugin compatibility with MP) So, any volunteers? Team doesn't have any resource for such... Of cource there is still that possibility that the 1.0 patched would contain even more severe bugs than the original 1.0 (smaller tester base, inexperienced developers on MP source code...) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
The hell of versions and SVN's
Contact us
RSS
Top
Bottom