Creating Change

What is a change?

In Changelogic we call changes objects that bind together tasks and real changes to source code – the differences. While task was a description why and how to implement something, change is realization of that on code base.

In terms of version control, every change is separate branch, which is isolated from other branches and most importantly, from the main branch until it is reviewed for correctness and integrated. You can't propagate unverified code.

Changes are separate objects because they have different life cycle – changes are developed, reviewed and integrated.

To start an implementation of tasks or to bind already implemented tasks to a source code you have to create a change. Privileged users can find the menu item New under the Change menu or on the front page in the My changes section a link New change.

You have to:

choose the right project
choose a reason
- bug – implementable task are bugfixes
- development – start a new development. This type of change can not be planned backward
- enhancement
- maintenance
write a description for the change
plan the change to a release cycle or to a macrochange

You can also:

bind existing tasks to the change (comma separated list is accepted for multiple tasks)
write a comment about the change
set the change dependent of another change
assign a developer

Here is an example of this form: