Complete History

Previous Next 1 2 3 4 5 6 7 8 9 10

Firefly keeps a comprehensive and complete history of its controlled assets. Any action done on such assets will be recorded. Aside from the usual recorded history items by legacy version control tools, Firefly also provides true support for Rename, Move, Delete and Undelete. Move and Rename in Firefly is not a delete and create process. The moved/renamed file retains its history instead starts anew. And as a result, Firefly handles Refactoring with ease. For example, if a Java package name was changed, the IDE and Firefly will work together to handle the changes.

File version conflicts are also fully recorded in Firefly. Let’s look at a situation: Main.java was concurrently modified by Tom and Jerry to product version 1.1.1 and 1.1.2. When both versions were check in and the conflict is resolved, what matters is how the system record what happened. Firefly will remember that version 1.2 has two parents, 1.1.1 and 1.1.2. Both versions will exist on the server for later use.

To make it even easier, Firefly provides a graphical version tree to intuitive display of file versions. ( Click here to take a look at the version tree and Hansky Visual Diff Merge Tools in action.) It is able to display file versions in two modes: file complete versions and file versions by streams.

Stream history is recorded in form of Changeset. A stream history might contain one or more Changeset and each Changeset is composed of file level changes. What’s exciting is that such file level changes will be visible inside each Changeset, giving the user a clear picture of how the stream has evolved.

Previous Next 1 2 3 4 5 6 7 8 9 10