Hi,
DISCLAIMER : Total newbie to both VCS and Subversion,
although have used CVS for simplest things.
I'm evaluating if Subversion is the right way for us to go, and as
much as I've been reading up on it, it looks like the beast we
might go for. But I have a few questions;
How do you best handle a workflow situation where committers
committ to the system, but administrators must approve their
changes before allowed further? My thinking is along having
three copies; "play", "approved", and "production" (where the
latter two are more or less mirrors). Normal users committ
changes to the "play" copy, and the system notifies an/several
administrators of changes for review, and they further approve
(into "production") or rollback changes (in "play"). Any best
practices? Ideas? (Have googled a bit for this, but all have turned
up nil)
If we store things in the metadata repository, does it exsist
hooks to link these to other systems? Our system has content
files and separate metadata, and it would be beneficial for us if
our templating system could read the metadata for processing.
(Alternativly we seperate metadata into XML files, or somesuch)
Some have stated some unstability with BerkleyDB. Any plans on a
replacement, ever?
Kind regards,
Alexander
NLA, ACT, Australia
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 13 03:11:58 2004