Shelving Question

[btd]

When I shelve code into Vault, why does the file stay checked out?
I thought when you shelve and give it a unique name it checked the code in but in an area outside the main area where we have our builds running.

Maybe I am missing something here but I thought Shelving allowed you to store the untested uncompiled code into Vault. In my experience it keeps the files checked out, why?

Thanks

btd

[lbauer]

You have the option to keep files checked out. But if you don't want the files to be checked out, check the box for "Undo Changes in the Working Folder" before you save the Shelve Set.

[btd]

That worked.

Thanks

[lbauer]

You're welcome. Some users want to keep files checked out because they're still working on them, but want to save their "in progress" changes in the database, just in case.

[Mordachai]

I'd like to ask why this isn't the default behavior?

If you're shelving it for later, but it remains in your working folder, then ... what's the point?

[lbauer]

Sometimes you just want to shelve a backup of your changes, but you want to continue working on the files in the working folder. Then if your newer changes don't work, you can revert to the last good set of changes.

[Mordachai]

I'm new to shelving... but it seems to me that it's counter-intuitive that shelving doesn't actually shelve the changes... only labels a change-set in vault that isn't checked in.

Can you make further changes and then somehow update your shelved set?

[lbauer]

If you make changes and shelve those using the same shelveset name, Vault Client will ask if you want to replace the existing shelveset. That's a way of updating the shelveset.

Or you can create a new shelveset with a different name for those changes.