I'm trying to think of a good promotion scheme and figure somebody else
has probably already figured it out. Subversion is the "authoritative
source" of source code and configurations - that part we have. But once
we are ready to move things to other platforms which are usually on
other physical servers, further down the lifecycle stream, what is the
best? Tags? Changesets? Currently files are cp'd or ftp'd from server to
The system I'm thinking of in particular involves source code that has
to be compiled on the target server for licensing reasons, so we can't
just move binaries. Here's an example of what my source tree looks like
for some accounting functions
Beneath each of these are source code files for a proprietary language,
but basically they are text files that get compiled into binaries.
Typically a change request will come in for one file, say
gl/posting_report. This file will be changed by the developer, committed
Now what? Should he tag the gl directory? The whole tree? Can he use the
same tag, say "test", and somehow repoint that tag to a new revision?
(even possible?) Then, the test platform will checkout or update their
directory with the "test" tag. When they're done, the "qa" tag gets
moved, and so on.
Thanks in advance,
Received on 2008-07-22 22:00:55 CEST