[Top][All Lists]

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

Re: [Gnu-arch-users] Working out a branching scheme [was: tag --seal --f

From: Robin Farine
Subject: Re: [Gnu-arch-users] Working out a branching scheme [was: tag --seal --fix]
Date: Thu, 01 Apr 2004 23:19:37 +0200
User-agent: Mozilla Thunderbird 0.5 (X11/20040306)

Andrew Suffield wrote:

A branch that never has any commits is probably not useful.

Branches containing tags only can be useful to transform a growing 'dist' project into an almost fixed size project. For example, based on Andrew's dists/configs/ tree, one could have something like:

|-- tla
|     |-- debian
|     |    |-- tla.release
|     |    `-- tla.mainline
|     `-- upstream
|          |-- tla.release
|          |-- tla.integration
|          `-- tla.lord

On version tla-release--debian--1.0, one could tag release candidates of the configuration project as base-0, patch-1, ..., and actual releases as version-0, versionfix-1, ... Here, the configuration 'tla.release' defines snapshots of 'tla.mainline', the set of versions that constitute the main debian development branches.

By getting tla-release--debian--1.0--versionfix-1 and building the configuration tla/debian/tla.release, one would obtain the source tree used to build the debian binary package tla-1.0-1. Or, building the configuration tla/upstream/tla.release would result into the upstream project tree from which debian's tla-1.0-1 derives.

When upstream (say Tom's) tla-1.0.1 comes out, one would create a new version tla-release--debian--1.0.1 to track debian releases based on tla-1.0.1.

Thus, assuming I have not missed something big, this scheme transforms the addition of new configuration snapshot files into creation of new <version>--<revision> in a tag only branch, but both schemes track the same information. Well, hopefully.


reply via email to

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