You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Johan Pretorius <jo...@bialliance.co.za> on 2009/02/19 19:03:51 UTC
Concepts of how to promote Development Code to Production Code
I'm currently using Tortoise SVN with Visual SVN Server and it's working
great.
I understand the basic work cycle (checkout/update working copy --> change
working copy --> commit/merge changes to repository)
What I don't understand is how to "promote" current development code to
production (currently I simply merge the changes by using a diff program
(WinMerge), but this is a lot of work, especially if the project has a lot
of files)
Any Ideas of how I can streamline this process? I will also like to control
the production code (in order to track updates of the production code)
Johan Pretorius
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1193510
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Concepts of how to promote Development Code to Production Code
Posted by Toby Thain <to...@telegraphics.com.au>.
On 19-Feb-09, at 2:03 PM, Johan Pretorius wrote:
> I'm currently using Tortoise SVN with Visual SVN Server and it's
> working
> great.
>
> I understand the basic work cycle (checkout/update working copy -->
> change
> working copy --> commit/merge changes to repository)
> What I don't understand is how to "promote" current development
> code to
> production (currently I simply merge the changes by using a diff
> program
> (WinMerge), but this is a lot of work, especially if the project
> has a lot
> of files)
You can serve the production site out of a working copy and use svn
update or svn switch to manage it. That will be easier than what you
are doing. For tracking changes, you'll want to learn about branches
(and tags) as Stefan mentioned.
--Toby
>
> Any Ideas of how I can streamline this process? I will also like to
> control
> the production code (in order to track updates of the production code)
>
> Johan Pretorius
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?
> dsForumId=1065&dsMessageId=1193510
>
> To unsubscribe from this discussion, e-mail: [users-
> unsubscribe@subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1200720
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Concepts of how to promote Development Code to Production Code
Posted by Stefan Sperling <st...@elego.de>.
On Thu, Feb 19, 2009 at 09:03:51PM +0200, Johan Pretorius wrote:
> I'm currently using Tortoise SVN with Visual SVN Server and it's working
> great.
>
> I understand the basic work cycle (checkout/update working copy --> change
> working copy --> commit/merge changes to repository)
> What I don't understand is how to "promote" current development code to
> production (currently I simply merge the changes by using a diff program
> (WinMerge), but this is a lot of work, especially if the project has a lot
> of files)
>
> Any Ideas of how I can streamline this process? I will also like to control
> the production code (in order to track updates of the production code)
See http://svnbook.red-bean.com/en/1.5/svn.branchmerge.html
and specifically http://svnbook.red-bean.com/en/1.5/svn.branchmerge.commonpatterns.html#svn.branchmerge.commonpatterns.release
Stefan