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

Re: trunk naming best practice question

From: Z W <mpc8250_at_gmail.com>
Date: Thu, 9 May 2013 22:53:22 -0700

Hi Ze, Bob, Les

Thanks for writing back.
From your experience, with new features being worked on the trunk, and but
the planning and sizing is poor during developemnt, when it comes to
releasing but the feature is incomplete, how would you turn "on" or "off"
features development at code-freeze before creating a release branch.


On Thu, May 9, 2013 at 10:21 AM, Zé <jose.passes_at_gmx.com> wrote:

> On 05/07/2013 04:50 AM, Z W wrote:
>> What's the best practice in use with SVN ?
> Maybe this can give you some ideas on how to organize your subversion
> repositories:
> http://svnbook.red-bean.com/**en/1.7/svn-book.html#svn.**
> branchmerge.commonpatterns<http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.branchmerge.commonpatterns>
> From your description, it sounds like you are trying to implement the
> release branches approach.
> --
> Zé
Received on 2013-05-10 07:53:55 CEST

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

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