In my most recent blog article, Selecting Great UI Text, I suggest that one of the most important things you can do to ensure that you've chosen a great UI text string is,
“5. Solicit FeedbackAsk your teammates. Ask your customers. The more eyeballs, the better.”
Now, I’m going to put my money where my mouth is and ask you--customers, competitors, friends, partners, and co-conspirators--for your thoughts on two important pieces of UI text that will appear in the as-yet unreleased Microsoft Visual Studio Team Foundation: Shelve and Shelveset. My notes on Shelve follow. Please feel free to weigh in on these terms in the comments attending this post.
In Visual Studio Team Foundation, the Shelve command sets aside a set of pending changes in the local workspace, as well as any associated work items and comments, on the server. You can use Shelve to share your changes with another developer when job assignments change or to temporarily set aside your in-progress changes to a set of files or folders in order to work on hotfix or other workspace-altering project. Shelve is a sanity-saver.
Bad alternatives I considered: archive, sideline, set aside, pause, abey, suspend, escrow