Switching Changes

• Changelogic
• Switching Changes

Why switch changes?
Being able to switch changes comes in handy when you are working on one change and for some reason need to develop another change before finishing the first one. A need for urgent fix or waiting for refined requirements are a couple of examples of why you would want to something like this.

Changelogic supports putting aside one change to work on another and return later. A similar feature is called shelving in Visual Studio Team Foundation.

When switching to another change, you may either commit your uncommitted code into the old change, or make it a part of the new change.

You may have multiple changes set aside at the same time, and you may switch back and forth between any of those changes. When switching to a change that is not in state “being developed”, development of the change is started.

Switching to another change is similar to starting development.

1. Run ant commit if you wish to commit your uncommitted edits to current change. Skip this step if you want to make the uncommitted edits part of the other change or you are certain you do not have anything uncommitted.
2. Run ant edit
3. Enter the number of the other change when prompted so.