Re: Branching scenario

In a message dated: 12 Mar 2003 14:00:25 EST
"Adam T. Gautier" said:

>I am somewhat new to version control systems and I need to solve a
>problem. I have searched the srchives and I still believe that my
>answer is in there but I have been unable to find it.

[...snip...]

>I need a flag of some sort that all developers can set on the sandbox
>version that upgrades that code to production.
>This way pre-release code can sit side by side with the current
>production code. Again this is only for new directories on the website
>that are under development.

I'm a little confused about what you're asking here. Are you looking
for some mechanism by which, when present, automatically promotes the
sandbox code to production?

I think the way I would structure your repository would be something
more along the lines of this:

---root
 |-sandboxes/
    |---index.jsp
    |---customer1
    | |---index.jsp
    | |---other.jsp
    |---customer2
    | |---index.jsp
    | |---other.jsp
 |-production
    |---index.jsp
    |---customer1
    | |---index.jsp
    | |---other.jsp
    |---customer2
    | |---index.jsp
    | |---other.jsp

Where the sandboxes/ area is all developmental code, and production/
is all released working code. Basically what you have here are
branches or copies. Then, when a certain sandbox rev becomes
"releaseable", you merge it into the production track.

Now, if you're looking for a way to automate this, then you'd have to
establish some sort of policy around what your 'release' criteria is,
and what determines that code is ready to be 'released'. Once this
policy is established, you can probably code that into a chekin
-trigger script to live on the svn server.

Does that help?

Also, I'd recommend reading the subversion handbook at:

        http://svnbook.red-bean.com/

Available in HTML or PDF :)

-- 
Seeya,
Paul
--
Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE
	It may look like I'm just sitting here doing nothing,
   but I'm really actively waiting for all my problems to go away.
	 If you're not having fun, you're not doing it right!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org