upgrading 3.7 beta to stable?

[osayidan]

I would like to know if upgrading from 3.7.x beta to 3.7 stable (or whatever you guys call it) will be possible without anything being changed too much in the templates and in the database.

The reason for this is that i am working on a large project where VB will be integrated into other systems, as well as have tons of customizations to itself, therefore upgrading from say 3.6.8 to 3.7 stable would probably be a nightmare, so the only hope of having 3.7 in this project (which would be very desirable) is to start from as close as possible to what 3.7 will be like (so 3.7 betas) when working on the project and then upgrade it to stable when it comes.

However if doing this upgrade will undo or mess up many customizations i would have to either delay this project until stable is released or stick to 3.6.8, both of which no one here is happy about.

[Zachery]

You're always going to have schema changes between beta changes both files and templates, and no one here is going to tell you nothing is going to change between beta and stable versions of vBulletin.

What you can do however is use the tools we provide to see what has changed between versions for example in templates with the template history.

[osayidan]

I've never used template history before, but using this method would i be to update manually to avoid any destruction of customizations? So long as i can perform the updates from beta to stable manually then theres no problem.

[Zachery]

If you are skilled with html/css/etc you should be able to compare the new and old templates and figure out what got added.