In my opinion, you'ld be better to stay with std /branches, /trunk,
/tags, and then tag each release using prefixes/suffixes to say which
environment each is deployed on etc
keep your dev running on the trunk (or branch as necessary), then when
ready to go into test, tag this as a test tag
ie /project/tags/1.0DEV
/project/tags/1.0STG
/project/tags/1.0
ie /project/tags/1.1DEV
/project/tags/1.1STG
/project/tags/1.1
You can export or checkout the relevant tag to the relevant server
ie svn export stagetag stagedir
However, I can't really see why your dev/stage/live versions would
differ, as this can be dangerous for testing/QA etc (unless you have
different configurations across the servers/apache instances)? You could
always use svn keywords to insert revision numbers into a config/help
file that gets checked out with the tag if you need to find out what
version is on what box..??
Hope that helps,
cheers,
Rachael
Steve Rieger wrote:
> say that i want to create three branches
> /dev
> /stg
> /prod
>
> all development goes into dev, once the dev people say that its ready
> for stg i export it and import it into the /stg branch, same goes for
> when moving from stg to prod. once there i can export to the
> appropriate (apache )servers, is this a good idea. the reason i am
> thinking along this line, like this i can always keep a history of
> what changed on the /dev /stg and /prod and on their respective
> servers. or would you say that i should create a seperate repository
> for each server and import/export that way.
>
>
> just asking
>
> --
> Steve Rieger
> AIM chozrim
> ICQ 53956607
> Cell 646 335 8915
> steve.rieger@tbwachiat.com
>
>
>
>
> This e-mail is intended only for the named person or entity to which
> it is addressed and contains valuable business information that is
> privileged, confidential and/or otherwise protected from disclosure.
> Dissemination, distribution or copying of this e-mail or the
> information herein by anyone other than the intended recipient, or an
> employee or agent responsible for delivering the message to the
> intended recipient, is strictly prohibited. All contents are the
> copyright property of TBWA\Chiat\Day, its agencies or a client of such
> agencies. If you are not the intended recipient, you are nevertheless
> bound to respect the worldwide legal rights of TBWA\Chiat\Day, its
> agencies and its clients. We require that unintended recipients
> delete the e-mail and destroy all electronic copies in their system,
> retaining no copies in any media. If you have received this e-mail in
> error, please immediately notify us via e-mail to
> disclaimer@tbwachiat.com. We appreciate your cooperation.
>
> We make no warranties as to the accuracy or completeness of this
> e-mail and accept no liability for its content or use. Any opinions
> expressed in this e-mail are those of the author and do not
> necessarily reflect the opinions of TBWA\Chiat\Day or any of its
> agencies or affiliates.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 11 15:49:01 2005