Version Control & BOX

[Greg Tataryn]

We have implemented Basic Security in test and will be rolling it into production soon. With this, it will be great to gain version control on files and we plan to use BOX to move files from test to prod from now on. I have been doing a little testing with BOX as I had not previously used it and it sort of seems to keep up with versioning between environments, however if a file is version 1.2 in test and does not yet exist in prod it seems it starts back at 1.0 in prod so the versions could be out of synch. Is there any way to prevent this?

It also appears that when a file is moved from one site to another, or one environment to another, it has to be checked in on the new location for versioning to happen, or am I mistaken?

I have noticed that it seems the NetConfig does not get versioned when a BOX package is deployed to it. Is there something I may be missing to get the NetConfig to version?

And finally on the topic of versioning, when does a file jump to a major version (ie from 1.x to 2.x)? There does not appear to be much documentation on Version Control in the help guides.

Topic