[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Trunk for "Prod" and a branch for "dev"

From: Ron Wilson <ronw.mrmx_at_gmail.com>
Date: Fri, 2 Sep 2011 13:36:31 -0400

On Thu, Sep 1, 2011 at 8:31 AM, Brendan Flanagan
<brendan.flanagan_at_wegobeyond.co.uk> wrote:
> They want "trunk" to reflect the current Production Release of their
> enhancements only.  They intend creating a branch called "Development" that
> the small number of developers will use day to day - i.e. they will add new
> enhancements, change existing code etc.
>
> Periodically they will merge some of the committed changes (from the Dev
> branch) back to trunk and effectively create a new "Production Release" and
> tag it.

Really it doesn't matter whether you deveop on the trunk or use the
trunk only for released code. If you need to make a fix to an earlier
release, you can still start a fix branch off the commit for that
release.

I am assuming that your client's reason for wanting the use the trunk
only for release is that they think it would be easier for
non-developer users to access the trunk. Really, it doesn't matter. It
is all just folder names to SVN. You could just as easily have a
"Release" branch and a "Development" branch, with no "trunk".

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2834664

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-09-02 19:36:35 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.