Pinning a stable version, best practices?

[paul-shed]

Our development process typically works as follows.

Developers work on the head of the repository in Vault. Once they add some extra functionality they add their changes that compile into the repository. We then run nightly builds. They label their library versions etc and everything is fine.

Occasionally however, we'd like to be able to check things in that are "work in progress". Now these check ins may break the build. They are useful however as it enables developers to save their work over the weekend or whilst they are on holiday.

So is it possible in vault to work at the head of the repository but to hide your changes to other users. So different users have different views of the current head. When a developer is happy they move the head for other users to their latest and greatest.

The closest solution I came with was using pin. But when you pin you cannot make any changes. So then I tried pin and sharing folders but that got very messy.

Suggestions please?

Regards,

paul - shed

[Beth]

You will probably want to check out branching? That way work can continue to go forward in different directions and then changes can be merged over if needed. We have a couple of articles in our KB Article Indexthat deal with branching. Just look under " Source Control Commands and Practices".