On Jun 11, 2008, at 10:01, Mike.Hiland_at_bd-bgi.com wrote:
> I am new to Subversion and trying to understanding if and how it
> can be
> used in our environment (which I imagine is similar to others). I
> am also
> not a developer, so these topics and concepts are new to me.
>
> We work in three development stages: Development, QC, and
> Production. Our
> developers work in “dev” until they have what they need. They will
> then
> push the code to “QC” for testing. Once approved, our Operations
> group
> will move the code from QC to Production.
>
> I’m not seeing this process clearly when I read the Subversion
> book. Maybe
> I am just missing the terminology?
>
> Can someone either point me to a resource that explains how
> Subversion is
> used in a production environment as I have described? Or, send me
> a basic
> flowchart-style explanation of how Subversion would be used in this
> environment?
You could have the trunk (where development occurs) and two branches,
QC and Production. You could "svn merge" changes from trunk
(Development) to the QC branch and from the QC branch to the
Production branch.
Or, you could just have trunk (for development) and use tags for
everything else. You could have two tag directories -- QC and
Production. When developers are done with what they're doing, copy
trunk to a new QC tag with a certain name (maybe including the date
or revision number to make it unique). QC checks out and tests a
particular tag. If QC finds problems with it they tell the developers
to fix it and create a new QC tag. Once QC is happy with a tag and
wants to release it to production, they can copy that QC tag to the
Production tag directory. You can have a script (like SVN Notify)
monitor the Production tag directory and cause something to happen
when a new tag appears there (like check it out and copy it to a
production server). You can use permissions to e.g. permit developers
to create tags in the QC directory but only permit members of the QC
group to create tags in the Production directory.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-12 00:14:53 CEST