Compatibility of BC3.1.X (12204) and 3.2.X (13046)

[chrisjj]

I would like to upgrade to V3.2 but some problems with it I've found in trialling mean I want the option to return to V3.1.

Can I be reasonably sure such a return is painless, esp. with respect to stored settings?

I will be upgrading workstations' main installations and subsequently the portable installations I have (to keep settings separate) placed in project folder trees.

Thanks.

[Aaron]

Hello Chris,

99% of the time the return should be painless. Just in case, before you update you can back up your current version's settings using the Tools menu -> Export Settings, export everything, and name it with the version number.

[chrisjj]

> 99% of the time the return should be painless.

A 1 in 100 failure rate is the kind of thing that worries me. Perhaps you could tell me the nature of the failures you are aware of? Thanks.

[Aaron]

I'm not aware of any actually, and the 99 number is just one I threw out there. I just can't guarantee that all future updates can be downgraded to any past versions without issue.

[chrisjj]

> I'm not aware of any actually

Good news - thanks.

Any Devs here aware of downgrade problems?

[Zoë]

Any Devs here aware of downgrade problems?

No, but it's not something we actively support or test. We try to not make significant changes to settings within a major release, and BC does maintain settings it doesn't understand. Personally I end up running everything from 3.0.0 up through the development releases, and I haven't seen any problems.

The only thing I can think of that's questionable is the sync changes we've already discussed, and, other than the visual glitch on the sync type, I'm pretty sure that's working correctly in 3.2.3.

[chrisjj]

Good to hear, inc. "BC does maintain settings it doesn't understand" so thanks, I'll migrate.