Reply to thread

Message: <blockquote data-quote="joboehl" data-source="post: 124060" data-attributes="member: 23490">hot_dog_friend. I think most people do get it. The dilema is: People don't whant to use the stable version (0.2.0.4) because it pales in comparison to what newer (unstable) versions do. So people want the feature being added, but expect the same level of stability of the stable release. That's actually a problem of the open source project. If this was a closed project, everybody would be using the stable 0.2.0.4 and not complaining about stabilty. After a year a new (stable) release would be released and people would love the new version with all the functions. There will be stable releases of MP with all the features you see on the SVN. But there is a cycle and process needed to get there. 0.2.0 passed trough 4 release candidates in order to get in shape to be called a stable release. I think that the TVServer will go trough a process like that once it has all it's planned features in place and with basic functionality working. The same with an eventual 0.3 release of MP itself. But until then:- 0.2.0.4 it's the stable release (no new music engine, old tv engine, no DVB-S2, and etc)- 0.2.2.0 it's the latest release to be used to preview functions to come in a new version. - SVNs are development snapshots. It might work one day and break the other. So if you want stability, go to 0.2.0.4. If you find a bug, report it (or fix it if you can and post as a patch). I know it's hard after knowing what cool things are in 0.2.2 and SVNs. But that's the price we pay for stability. Every software is unstable when features are being added. I do think a list of features (like the one in the tvengine v3) could be done and people know what they could expect on a newer release. It would even help the developers to decide their priorities and know when to stop adding stuff. At the same time, they would have to say no to many " it would be nice if MP could do this" messages in the forums. As for the tvengine (the one being discussed in this thread) the feature list exists and it is not ready today, so devs need to keep going implementing stuff before they can start polishing and call it stable. As a side note: I used other HTPC solutions before coming to MP. I just finished migrating from Windows MCE to MP. My opinion is that HTPCs in general are naturally  unstable, independent of what front end you have. I can't use MP completely in it's current form, but I'am betting it will shape up a pretty stable product by 0.3 or whatever number the next stable release will come.</blockquote>

Verification