Given that the nature of DVCS, it seems that it will be at least possible that at any given time one instance of Veracity will need to push/pull/clone a repository that is in another instance of Veracity that is a different version. Since as new releases are deployed to computers at different times. Vault has the following to say on this topic: **Client/Server Version Compatibility** *It is always recommended that your client and server versions match exactly (e.g., a 5.0.3 client should be connecting to a 5.0.3 server). 5.0.x clients are able to communicate with any 5.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 5.0.x clients and servers are not compatible with 1.x, 2.x, 3.x or 4.x clients and servers.* However, I may work with my company repository with may be version 1.1 and also want to pull code from the public Veracity server which is probably more up to date. might be version 2.0.

Given that the nature of DVCS, it seems that it will be at least possible that at any given time one instance of Veracity will need to push/pull/clone a repository that is in another instance of Veracity that is a different version. Since as new releases are deployed to computers at different times. Vault has the following to say on this topic: **Client/Server Version Compatibility** *It is always recommended that your client and server versions match exactly (e.g., a 5.0.3 client should be connecting to a 5.0.3 server). 5.0.x clients are able to communicate with any 5.0.x server, but specific bug fixes will not work correctly if they required both client and server changes. 5.0.x clients and servers are not compatible with 1.x, 2.x, 3.x or 4.x clients and servers.* However, I may work with my company repository with may be version 1.1 and also want to pull code from the public Veracity server which I hope might be is probably more up to date. date.

Given that the nature of DVCS, it seems that it will be at least possible that at any given time one instance of Veracity will need to push/pull/clone a repository that is in another instance of Veracity that is a different version. I may work with my company repository with may be version 1.1 and also want to pull code from the public Veracity server which I hope might be more up to date.

Given that the nature of DVCS, it seems that it will be at least possible that at any given time one instance of Veracity will need to push/pull/clone a repository that is in another instance of Veracity that is a different version.

Given that the nature of DVCS, it seems that it will be at least possible that at any given time one instance of Veracity will need to push/pull/clone a repository that is in another instance of Veracity that is a different version.