Version change rationale.

Hello.

I would like to be able to record why changes were made to a revision in
a separate file to the one subject to the revision. I would like to keep
this revision file under version control as well.

That is, if a change is made to a file under change management, I would
like to be able to keep a record of why that change was made in a
separate file. I'm managing a collection of Java projects, and this
serves two purposes: for files that permit comments, it keeps them to a
minimum, and for files that do not permit comments, it allows me to keep
some idea of why a change was made. In either case, this allows me the
opportunity to include a comprehensive rationale for changes that, say,
might link back to program specs, design documents or other sources of
info.

I have a very rough idea of how this might be implemented. I'm almost
sure someone would have come up with something like this before, and I'd
like to know what is out there before I plunge in to doing my own thing.

Suggestions accepted with compliments,

  Owen.
Received on Wed Jan 10 07:41:56 2007