Re: code release cycle under svn

2007/3/14, matt farey <matt.farey@gmail.com>:
> Hiya,
> I've come late to SVN use, so I apologise if this question gives you a
> bored sinking feeling!
> A web dev project is getting increasingly complex, I would like to know
> how to stage the release of the code to the web server, so that each
> month I can use SVN to push a working set of files to the server
> delivering a predictable code release cycle to the client.
> I realise I could just commit (with note "release 1.0" in the log) from
> my working copy, then from the server check out a particular revision
> into the web root for that app, but was wondering if I could get some
> thoughts from more experienced users. In major opensource releases I
> notice there are often multiple directories corresponding to each new
> release, I like this structure.
>
Hello Matt,

'Tags' brach is used for 'stable' releases read more about this branch
and the other involved on the svn book here's the link
http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.branchmerge.maint.layout
>

-- 
Iván Alemán -- bonovoxmofo.blogspot.com
Cambia ya!
http://goodbye-microsoft.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org