Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| Activity: Shelve a Changeset
Developer
|  | Participating Roles Responsible: Developer
### Overview Shelve a changeset when a required task must take priority over a task already in progress. Shelving can also be used for complex integrations where components are mutually dependent. Shelving code places it in a temporary area for later retrieval by the same or another developer. The benefit of shelving code is that the information entered into a particular segment of code is not lost. When the changeset is shelved, the state of the developer's desktop is restored to the state prior to checking out the code for change. # Entry Criteria The code to be shelved is available. # Sub-Activities
1 | Identify Shelved Code | Identify the code that participates in the shelving process. Mark the code using the development tool to identify shelved code from the rest of the code.
2 | Integrate Changes to Version Control | Integrate shelved code into the version control repository.
3 | Record Interruption Scenario | Record the changeset details for the shelved code. Record the setup required to recreate the development environment for the shelved code.
# Exit Criteria
| The code participating in the shelving process does not contribute to the system functionality.
| The state of the code prior to the shelving process is retrievable with prescribed procedures documented during the shelving process.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |