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="karlake" data-source="post: 366290" data-attributes="member: 25314"><p>Hi all!</p><p></p><p>First! I Love MP and what you devs are doing with it! So the following is just a try to make the packageing better.</p><p>I've been naggin' about this before, but It's an iomportant issue.</p><p></p><p>The problem is how we release versions and SVN's.</p><p>When 1.0.0 was released there was a long list of known bugs that was panned for 1.0.1.</p><p>No problem with that but that and the fact that 1.0.0 gave us new ones, makes it impossible for an enduser</p><p>to be content with the official release and wait for the next one. You need the SVN's to get the bug fixes for </p><p>the critical issues. But then you also need to know that you are installing a "test-version" that gives you new development, with new bugs attached.</p><p>You end up in a rat race of SVN's and you never get an "end user" friendly version that can be considered as</p><p>a "function" under your tv.</p><p></p><p>After installing latest SVN, the skin stoped working and the live TV is dead. For an end user, this makes MP</p><p>unusable and we wan't endusers to use MP, don't we!?</p><p></p><p>OK! So how do we solve this to make MP more friendly?</p><p></p><p>I would like to see a separation between the versions.</p><p></p><p>-After the release of a version, this version will not be developed any longer, but still be maintained with bug-fix</p><p>SVN's until the next version is released and then it will die.</p><p></p><p>-A copy of version code is made under the name of eg (1.0.1-"next-alpha). This version will not be released to the </p><p>community until it comes to Beta or RC1 level. </p><p></p><p>This will give end user a, more and more, stable version.</p><p>It will give the skinners and plugin artists a chance to make their products nice and stable.</p><p>It will give the devs some peace to do some real development, without the pressure of always have to consider that the latest development will effect the enduser.</p><p></p><p>Reported bugs will have to be corrfected in two sources, but this dissadvantage is well invested extra work to </p><p>let mp be usable for sooo many more users</p><p></p><p><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" /></p></blockquote><p></p>
[QUOTE="karlake, post: 366290, member: 25314"] Hi all! First! I Love MP and what you devs are doing with it! So the following is just a try to make the packageing better. I've been naggin' about this before, but It's an iomportant issue. The problem is how we release versions and SVN's. When 1.0.0 was released there was a long list of known bugs that was panned for 1.0.1. No problem with that but that and the fact that 1.0.0 gave us new ones, makes it impossible for an enduser to be content with the official release and wait for the next one. You need the SVN's to get the bug fixes for the critical issues. But then you also need to know that you are installing a "test-version" that gives you new development, with new bugs attached. You end up in a rat race of SVN's and you never get an "end user" friendly version that can be considered as a "function" under your tv. After installing latest SVN, the skin stoped working and the live TV is dead. For an end user, this makes MP unusable and we wan't endusers to use MP, don't we!? OK! So how do we solve this to make MP more friendly? I would like to see a separation between the versions. -After the release of a version, this version will not be developed any longer, but still be maintained with bug-fix SVN's until the next version is released and then it will die. -A copy of version code is made under the name of eg (1.0.1-"next-alpha). This version will not be released to the community until it comes to Beta or RC1 level. This will give end user a, more and more, stable version. It will give the skinners and plugin artists a chance to make their products nice and stable. It will give the devs some peace to do some real development, without the pressure of always have to consider that the latest development will effect the enduser. Reported bugs will have to be corrfected in two sources, but this dissadvantage is well invested extra work to let mp be usable for sooo many more users :thx: [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
The hell of versions and SVN's
Contact us
RSS
Top
Bottom