Reply to thread

Message

Chemelli:

I am well aware of that, but it is very useful to have different versions for several reasons:
- I am mainly doing it for quality assurance, i.e. verifying where problems are residing. I had a lot of problems with RTSP when switching channels earlier and I have a test-unit (one laptop with Vista on it) where I reinstall frequently to test SVNs and try to pinpoint the problems (hard to do in the "production environment" at home where the entire family is using MP).
- when having multiple clients in the network (I have four clients), it is very useful to have the possibility to upgrade them one at the time. I can accept that this fails once in a while, but as long as the protocol between the units have not changed it should be possible. Therefor the version check should be on the communication protocol version, not on the SW-version....
- I have once been in the situation where I can not get a fully working system without mixing versions between client and server. There are too many parameters that are not under the control of the developers that may mess things up (e.g. graphic driver versions in cooporation with specific graphic adapters). If I would have requirements on putting the server too sleep (like dino2008 requires) this then requires 1.0 release on the server. However I have had big problems with channel switching in the client of 1.0, which requires me to run 1.0.1 there. If it works it should be OK to match and mix like that to get a working system, if it is not working - no bugreports should be accepted...

/ jhb

<blockquote data-quote="jhb" data-source="post: 409757" data-attributes="member: 24959">Chemelli:I am well aware of that, but it is very useful to have different versions for several reasons:- I am mainly doing it for quality assurance, i.e. verifying where problems are residing. I had a lot of problems with RTSP when switching channels earlier and I have a test-unit (one laptop with Vista on it) where I reinstall frequently to test SVNs and try to pinpoint the problems (hard to do in the &quot;production environment&quot; at home where the entire family is using MP). - when having multiple clients in the network (I have four clients), it is very useful to have the possibility to upgrade them one at the time. I can accept that this fails once in a while, but as long as the protocol between the units have not changed it should be possible. Therefor the version check should be on the communication protocol version, not on the SW-version....- I have once been in the situation where I can not get a fully working system without mixing versions between client and server. There are too many parameters that are not under the control of the developers that may mess things up (e.g. graphic driver versions in cooporation with specific graphic adapters). If I would have requirements on putting the server too sleep (like dino2008 requires) this then requires 1.0 release on the server. However I have had big problems with channel switching in the client of 1.0, which requires me to run 1.0.1 there. If it works it should be OK to match and mix like that to get a working system, if it is not working - no bugreports should be accepted.../ jhb</blockquote>

[QUOTE="jhb, post: 409757, member: 24959"] [B][I]Chemelli:[/I][/B] I am well aware of that, but it is very useful to have different versions for several reasons: - I am mainly doing it for quality assurance, i.e. verifying where problems are residing. I had a lot of problems with RTSP when switching channels earlier and I have a test-unit (one laptop with Vista on it) where I reinstall frequently to test SVNs and try to pinpoint the problems (hard to do in the "production environment" at home where the entire family is using MP). - when having multiple clients in the network (I have four clients), it is very useful to have the possibility to upgrade them one at the time. I can accept that this fails once in a while, but as long as the protocol between the units have not changed it should be possible. Therefor the version check should be on the communication protocol version, not on the SW-version.... - I have once been in the situation where I can not get a fully working system without mixing versions between client and server. There are too many parameters that are not under the control of the developers that may mess things up (e.g. graphic driver versions in cooporation with specific graphic adapters). If I would have requirements on putting the server too sleep (like dino2008 requires) this then requires 1.0 release on the server. However I have had big problems with channel switching in the client of 1.0, which requires me to run 1.0.1 there. If it works it should be OK to match and mix like that to get a working system, if it is not working - no bugreports should be accepted... / jhb [/QUOTE]