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="gxtracker" data-source="post: 366404" data-attributes="member: 14004"><p>Hi karlake,</p><p></p><p>What critical bugs were introducted into 1.0 that weren't present in the release candidates? </p><p></p><p>I think the current SVN system that is in place is just fine: you have a base version used for regular end users (1.0) and the SVN's are your bleeding edge updates that will most likely break some functionality - use at your own risk type update.</p><p></p><p>I've noticed some minor issues such as <a href="http://mantis.team-mediaportal.com/view.php?id=1871" target="_blank">0001871: Black screen after stopping video_ts playback - MediaPortal Bugtracker</a> on my installation of MP 1.0, and I could upgrade to the latest SVN since it will be implemented in 1.0.1, but then I run the risk of breaking something else.</p><p></p><p>End users should not be installing SVN's.</p><p></p><p></p><p></p><p>Since MP 1.0 is under a feature freeze, we already have this in essence. All new bugs that are being worked on for 1.0.1 are just bug fixes and no new development.</p><p></p><p>In general software development, Beta's and RC's should never be released to the end user. MP development is slightly different because community development can take so long, and most users of the product are highly experienced, they can release Beta's and RC's and still have them run stable. They do this to get more releases out to the user in a shorter time frame.</p><p></p><p></p><p></p><p>Teeing off development like this and maintaining two source trees is a major development no-no. It's not just a matter of applying a bugfix to two different version - bug fixes can sometimes break other functional features. this means additional testing, QA, resources, etc...</p><p></p><p>I think ultimately, the answer to the problem is this (and this is my own opinion <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" />): If you're using a version that breaks some functionality you require, then as an end user you have two options - revert to a previous version where this worked, or wait until a new version comes out that fixes it.</p><p></p><p>You can report the bug, and install the SVN, but then IMO you are not an end user anymore - you are helping with development. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="gxtracker, post: 366404, member: 14004"] Hi karlake, What critical bugs were introducted into 1.0 that weren't present in the release candidates? I think the current SVN system that is in place is just fine: you have a base version used for regular end users (1.0) and the SVN's are your bleeding edge updates that will most likely break some functionality - use at your own risk type update. I've noticed some minor issues such as [url=http://mantis.team-mediaportal.com/view.php?id=1871]0001871: Black screen after stopping video_ts playback - MediaPortal Bugtracker[/url] on my installation of MP 1.0, and I could upgrade to the latest SVN since it will be implemented in 1.0.1, but then I run the risk of breaking something else. End users should not be installing SVN's. Since MP 1.0 is under a feature freeze, we already have this in essence. All new bugs that are being worked on for 1.0.1 are just bug fixes and no new development. In general software development, Beta's and RC's should never be released to the end user. MP development is slightly different because community development can take so long, and most users of the product are highly experienced, they can release Beta's and RC's and still have them run stable. They do this to get more releases out to the user in a shorter time frame. Teeing off development like this and maintaining two source trees is a major development no-no. It's not just a matter of applying a bugfix to two different version - bug fixes can sometimes break other functional features. this means additional testing, QA, resources, etc... I think ultimately, the answer to the problem is this (and this is my own opinion :D): If you're using a version that breaks some functionality you require, then as an end user you have two options - revert to a previous version where this worked, or wait until a new version comes out that fixes it. You can report the bug, and install the SVN, but then IMO you are not an end user anymore - you are helping with development. :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
The hell of versions and SVN's
Contact us
RSS
Top
Bottom