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: 367965" data-attributes="member: 25314"><p><strong>Compromize</strong></p><p></p><p>OK! It's maybe to much to ask of a small team, to maintain two sets of code.</p><p></p><p>We know that every new release, of any software, gives new bugs. First fixes for my ubuntu 8.10 came 1 or 2 days after the release. And they are a BIG team. So it's likely that 1.0.1 will give us new bugs to. That is life! So I still </p><p>feel that we need to do something for our endusers.</p><p>Is it possible to do it like this?</p><p></p><p>After a new release, the team concentrates on bugfixes only and release SVN's every week under the name of </p><p>eg. 1.0.1 SP1, SP2, SP3 and so on, until we have a solid platform. Then it changes name to 1.0.2.alpha with normal svn and the new development starts.</p><p></p><p>This is exactly the same amount of work for the team, only we state that official versions and SP's are for endusers and the versions to release skins/plugin to.</p><p></p><p>the newer versions with it's SVN's are for expert and people who like to be on bleading edge.</p><p></p><p>With this method, we will satisfy everybody's needs with exactly the same amount of work. Only differece is in the way we do it and that there are two different sets of download official, with SP and Alpha,Beta,RC with svn's</p><p></p><p>This will also focus the skin/plugin to be developed in the same way. They can stay in the official version for a long time and when RC1 of next version comes out, it's time to move on.</p><p></p><p>For the installer-idea to work in reality, it's important that all the plugin/skins in the bundle is made for the same version. Today some plugins/skins are made for official, some demand SVN X. Some other SVN Y. This new method could be a good way of making MP/skin/plugin to follow the same tempo.</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: 367965, member: 25314"] [b]Compromize[/b] OK! It's maybe to much to ask of a small team, to maintain two sets of code. We know that every new release, of any software, gives new bugs. First fixes for my ubuntu 8.10 came 1 or 2 days after the release. And they are a BIG team. So it's likely that 1.0.1 will give us new bugs to. That is life! So I still feel that we need to do something for our endusers. Is it possible to do it like this? After a new release, the team concentrates on bugfixes only and release SVN's every week under the name of eg. 1.0.1 SP1, SP2, SP3 and so on, until we have a solid platform. Then it changes name to 1.0.2.alpha with normal svn and the new development starts. This is exactly the same amount of work for the team, only we state that official versions and SP's are for endusers and the versions to release skins/plugin to. the newer versions with it's SVN's are for expert and people who like to be on bleading edge. With this method, we will satisfy everybody's needs with exactly the same amount of work. Only differece is in the way we do it and that there are two different sets of download official, with SP and Alpha,Beta,RC with svn's This will also focus the skin/plugin to be developed in the same way. They can stay in the official version for a long time and when RC1 of next version comes out, it's time to move on. For the installer-idea to work in reality, it's important that all the plugin/skins in the bundle is made for the same version. Today some plugins/skins are made for official, some demand SVN X. Some other SVN Y. This new method could be a good way of making MP/skin/plugin to follow the same tempo. :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