Shelving

[rshillington]

Just read that Team System will offer something called Shelving --- to allow a developer to use the SCCS as a kind of backup device, without actually pooching the project with half finished work.

Recently I had to rebuild my workstation --- and had a bunch of stuff that I didn't want to checkin --- so I just imaged my workstation, using Ghost 9, and rebuilt, but had a heck of a time getting my working folders all back in working order.

If I had shelving, I would have shelved my work before reformatting, and then presumably just retrieve from the shelf?

Anyway sounds like a cool feature that would be great to see in Vault.

Cheers,
Ralph Shillington

[lbauer]

This feature request is already in our feature enhancements database, to be considered for Vault 4.0.

I'll add your "vote."

[joshyeager]

Please add my vote to this one, too!

[christian]

I think you may have my vote already logged for this (?)

I think this feature is more generically known as "Private Version"

[lbauer]

I think you may have my vote already logged for this (?)

Yes, we do. There you go again, trying to sneak in more votes.

[christian]

Maybe next time I should sign in as someone else ;-)

[listerp]

Add My Vote

[Saturn]

This has been discussed elsewhere too:

http://support.sourcegear.com/viewtopic.php?t=1620

Basically, there are a few different theories on how people want to use this:

Private version - You check in your files to a private "branch" and no one else can see them until you check them into (merge into?) the main branch.

Programmer QA - You check in your files to a semi-private, temporary "branch" and only people you give access to (or everyone maybe) can see the files, but they have to retrieve them in some special way ("view Xxxx's branch".)

Workflow management - Development gets a "branch", testing gets one, as does release. Files / folders can be promoted from one to the other, keeping their history, etc.

All of these things are probably possible currently, but very cumbersome to implement. I'm very much looking foward to 4.0 if it is going to address this. Currently Programmer QA and any associated changes pretty much has to be done the same day it is checked in. Otherwise the compile server picks up the changes which aren't done, which screws up the testers the next day, etc etc.

[Tonyb]

For "Private version" can't you just create a new repository (e.g. "Tonybs Shelf") and in the repository create a folder for each project/solution that you are working on (so it would somewhat mirror the "Main" Repository).

If you have code you want to shelf you can just check it into the "Private" repository and when you are ready to share it with everyone just check it into the "Main" repository.

I haven't tested this idea but I don't see why it would work as a temporary solution as long as the working folders in the "Main" and "Private" repository are set to the same folder. It should solve the problem for people working on multiple computers and avoid checking incomplete code into your build environment.

[emarthinsen]

Add my vote.

I definitely have the need to version a file that I'm working on that is not yet ready to be added back into the public repository.

Regards-
Eric

[robinz]

Add My Vote as well.

Have you decided if this will make it to 4.0 yet?

[lbauer]

It will probably not make it into 4.0 -- it's currently slated for a later release.

[lbauer]

It will probably not make it into 4.0 -- it's currently slated for a later release.

[dsellers]

Add my vote too!

[lbauer]

Ok.