BTV Link backwards-compatible?

[optikhog]

Before I jump into beta, I just wanted to see if anyone knew whether or not the latest version of BTV Link is backwards-compatible. I'm going to put the beta onto my second server and will test using my BTV Link box, but would like to maintain 3.5.3 on my main box until we're out of beta...

[nanook105]

I believe that link has to be the same version as the server it is connecting to. So if you upgrade a test server and link, you you have to connect link to the test server. I do it all of the time, is there an issue doing this ?

[optikhog]

Originally Posted by nanook105

I believe that link has to be the same version as the server it is connecting to. So if you upgrade a test server and link, you you have to connect link to the test server. I do it all of the time, is there an issue doing this ?

Hmm, well I was hoping to have access to both servers (beta and 3.5.3) using my BTV Link machine. I guess I'll just sit tight and not jump to the beta then.

[nanook105]

Originally Posted by optikhog

Hmm, well I was hoping to have access to both servers (beta and 3.5.3) using my BTV Link machine. I guess I'll just sit tight and not jump to the beta then.

You can still set up folders on your test/beta server that point to your 3.5.3 shows, so that shouldn't be an issue.

[bnflaherty]

I can attest to the fact that the beta link will not connect to anything less than the beta btv server... tried it last night but got the error about the versions...

[noodleNT]

I thought they made BLink version independent in these latests releases.

[merrypig]

It had to be the same version but not same build no I think was the change. But since the versions go up and down all over the place, it probably didn't make much difference

Wanna know what I mean? We're currently testing a 3.7.2 release candidate. Yet according to the website, 3.5.3 is the currently public one.

It won't be at all odd to go from a 3.5.3 to a 3.7.2 publicly. Nope. It won't smell of lots of broken builds on the way, or fragile version numbering/control.

Maybe I'm just picky about these things. I know it's the same program and will work or not work either way, but I bet I aint the only one who mentions it

Or maybe ss will go and release it as 3.6 instead =)

[Schro]

My link copy (3.5.2) will connect to both a 3.5.2 server and a 3.7... no exceptions noted...

[optikhog]

Originally Posted by Schro

My link copy (3.5.2) will connect to both a 3.5.2 server and a 3.7... no exceptions noted...

Sweet. Thanks for the info!

[nanook105]

Originally Posted by Schro

My link copy (3.5.2) will connect to both a 3.5.2 server and a 3.7... no exceptions noted...

Unless something changed, this is probably a fluke. I believe that they must be the same up to the second character. So 3.5.1 should work with 3.5.2 and 3.5.3, but 3.5.X and 3.7.X is not guarenteed to work. I'm glad the current combination works for you, but I wouldn't count on it going forward.

[Schro]

Originally Posted by nanook105

Unless something changed, this is probably a fluke. I believe that they must be the same up to the second character. So 3.5.1 should work with 3.5.2 and 3.5.3, but 3.5.X and 3.7.X is not guarenteed to work. I'm glad the current combination works for you, but I wouldn't count on it going forward.

I didn't expect it to work either- I just bumped the 3.7 to 3.7.2... I'll try link out and see what happens...

[rkuo]

Originally Posted by merrypig

It had to be the same version but not same build no I think was the change. But since the versions go up and down all over the place, it probably didn't make much difference

Wanna know what I mean? We're currently testing a 3.7.2 release candidate. Yet according to the website, 3.5.3 is the currently public one.

It won't be at all odd to go from a 3.5.3 to a 3.7.2 publicly. Nope. It won't smell of lots of broken builds on the way, or fragile version numbering/control.

Maybe I'm just picky about these things. I know it's the same program and will work or not work either way, but I bet I aint the only one who mentions it

Let's try to stay constructive.

Here's how it's working at the moment. 3.6 is a separate branch of BTV with localization for different countries. 3.7 is what you folks are testing at the moment. The revision numbers (3.7.x) change for various internal releases.

No grand conspiracy here. Just ordinary people working to improve the software.

[noodleNT]

Conspiracies are more fun though.

[merrypig]

odd, I never said there was a conspiracy. Just that the public versioning was a tad unconventional.

3.7 would have been the sensible public release imho, the internal builds should _not_ have affected that. that's why you have build id's...

but anyway.. moot point. I'll move on and go read the news on Brum.