Shelves: una funcion muy util de control de versiones

Las Shelves son un concepto muy práctico en control de versiones, son una versión "ligera" de la creación de ramas. Este artículo explica cómo usar Subversion para crear Shelves.

Shelves in Subversion

Shelves in Subversion There is a popular feature called "shelves" that was included in Microsoft's Visual Studio Team System. I am fairly certain that VSTS is not the first or only tool to have this feature and in this article I will show you how to get the same feature from Subversion. I think of shelves as essentially creating and using a branch to save some changes you have been working on, but now need to set aside, or shelve, for a while.

Documentación Visual Studio:

The Purpose of Shelving

Shelve your pending changes when you are not ready to or cannot check in a set of pending changes. There are primarily five shelve scenarios:

• Interrupt When you have pending changes that are not ready for check in but you need to work on a different task, you can shelve your pending changes to set them aside.

• Integration When you have pending changes that are not ready for check in but you need to share them with another team member, you can shelve your pending changes and ask your team member to unshelve them.

• Review When you have pending changes that are ready for check-in and have to be code-reviewed, you can shelve your changes and inform the code reviewer of the shelveset.

• Backup When you have work in progress that you want to back up, but are not ready to check in, you can shelve your changes to have them preserved on the Team Foundation server.

• Handoff When you have work in progress that is to be completed by another team member, you can shelve your changes to make a handoff easier.