What about a SourceSafe EXPORT tool?

[THONA]

Any chance we get this?`

Sounds stupid?

Not so much.

We are thinking aobut moving to Vault. Clearly.

OTOH all customers have sourcesafe. We normally gave them so far exported sourcesafe archives of their projects, so that they can see the development. They loved this.

With Vault we loose this capability.

[ericsink]

Any chance we get this?

Realistically, no.

I understand the reasoning, but the practical reality is that we have too many far more important things on our To-Do list.

[THONA]

Hm, given that there is a free 1 user version of vaultI could atually live with an export TO vault, do send users just a sql database with only their projects.

But this brings eme back to another area where vault is lacking - there i no way to transfer a project (hierarchy) to another instance of vault - may it be another repository, or another server. This means there is no way and mechanism to restructure a vault databae once it has been created. This means that the only sensible way to set vault up is to set up ONE server, with ONE repository, for anything that MAY be shared at one point - multiple repositories are only an alternative if you run something like a hosted system (orcsweb - btw., what are the requirements for this? I think about offerinng the same, but for sensible prices) and separate hosted customers.

What about a mechanism to export/import projects to your own form,et, or at least a mechanism to copy/move projects between servers (including the same server in different repositories)?

[dan]

This is very high on our priority list, and it will be part of our next major release (4.0, due out at the end of the year)