Archive for category Version Control

CM discussion group

At the end of last year I ran an experimental ‘live discussion’ under the banner ‘The Watercooler’. This was intended to help spark conversation with the hope of encouraging people of all abilities to contribute to the body of knowledge wiki. Given the modest success of that experimental session, I have planned a series of [...]

Leave a Comment

When is a change a change?

A change can be viewed in two ways; conceptually or literally. What I mean by this distinction is that when I say the requested change is to “correct spelling mistakes in the poem” I am specifying conceptually what the change is to achieve (and after the fact, what the change achieved). On the other hand [...]

, , , ,

Leave a Comment

Items have history

As those of you who have been following this blog for any time will know I am currently looking in some detail at parallel development, specifically how it can be managed safely by non-expert version managers. I have used parallel development with much success on many projects but codifying my knowledge into a tool is [...]

4 Comments

Parallel development: theory and practice

Having spent the past couple of weeks with a client working through the issues that need to be carefully considered when version controlling software, and in particular how to manage and control parallel development. I have come to three conclusions: People are often more afraid of the perceived problems than the practical realities of parallel [...]

Leave a Comment

Who’s afraid of the big bad merge?

A common objection to using parallel development is the fear of the inevitable merging required to reintegrate the changes as the development proceeds. In this post I will take a look at some of the issues that arise from managing parallel development and, perhaps more importantly, provide some guidance on how to avoid the pitfalls [...]

, , ,

1 Comment

Basic Branching

This article lays the foundation for a series on branching and the development management techniques it enables. A simple linear development progresses by building one version on another. So, version one is updated to produce version two, version two is changed to make version three, and so on. This form of version progression is well [...]

, , ,

1 Comment

Follow

Get every new post delivered to your Inbox.