[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Repository branch (and tags) diagram?

From: Jean-Marc Saffroy
Subject: Re: Repository branch (and tags) diagram?
Date: Thu, 16 Nov 2006 15:06:30 +0100 (CET)

On Mon, 13 Nov 2006, Alan Dayley wrote:

On the other hand, let me state the big picture. I am trying to solve the problem of tracking branches. Our development team is relatively small, we have fairly good communication and we strive to minimize the number of active branches. However, when we make a branch and then 3 months later need to understand why and where, I'd like to have an easy way to point to the location of the branch within the context of the overall project history.

What are the practices others in the group use to solve this issue, if not a tool that uses the data and meta-data from the repository?

In my team we have a set of rules and conventions for using CVS, among which:

* First commandment: *always* create a tag to root a new branch. Our practice is to use a descriptive tag name, often including the date and time. Of course we end up with overly long names, but in the end scripts can do most of the work. If you suspect developpers could forget to do so, it's certainly possible to enforce this with a script in CVSROOT/taginfo.

* Second commandment: use "cvs rtag" instead of "cvs tag", this way the repository history adds a log entry that can later be browsed with "cvs history -T", something like:

T 2006-11-14 13:43 +0000 saffroy lustre

Meaning I put the tag T-1_4_7_1-MERGE-20061114_1443 on what was the tip of branch B-1_4_7_1-MERGE at the time.

Then of course you that does not give you the nice graphical view of branches (I wish we had such a tool), but at least with these practices you *can* retrieve such vital piece of information from your repo.


Jean-Marc Saffroy - address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]