Feature Request: Freeze Branch

Guest · Post by **Guest** » Wed Feb 18, 2004 5:18 pm

During releases we have what is called a "code freeze"; essentially what this means is that all check-ins must be approved before being comitted. It would be nice if Vault supported this model (for us anyway!).

1. Administrator locks a branch and marks it as "frozen"
2. User creates a change list that they want to commit, but is informed Branch is frozen.
3. User submits the change list to the Admin who approves / rejects it (note rejected change lists should be moved to a "pending" state since they will likely be approved after the release)

I am not sure how common this scenario is but having tool support for it would be very nice.

dan · Post by **dan** » Thu Feb 19, 2004 4:55 pm

These are very advanced features, and we do get requests for them every now and then. We will eventually want to look into doing this, but I have to admit that it will be down the road a bit before we do that.

dan · Post by **dan** » Thu Feb 19, 2004 4:56 pm

I should also say that we already support the Pin command, which does lock a tree. However, without the other features, I suspect it won't be all that useful for what you really want.