[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: Mon, 6 May 2013 22:14:01 -0700

Hi Geoff

Thanks for responding.
So one would not make builds on trunk directly ?

Thanks again

On Mon, May 6, 2013 at 9:18 PM, Geoff Hoffman <ghoffman_at_cardinalpath.com>wrote:

> It's common to have
>
> yourrepo
> /branches
> /tags
> /trunk
>
> Each day, tag the trunk (svn copy) as /tags/<Y-m-d> and build that in your
> CI tool and push it to your testing server.
>
> Branches are typically feature-related or release-related, e.g.
> /branches/feature-name or /branches/development or /branches/v2.0alpha.
> I've also seen it work where each developer has his/her own branch -
> /branches/yourname /branches/hername.
>
> Does that give you some ideas?
>
>
>
>
>
> Geoff Hoffman
> Solutions Architect & LAMP Engineer
> phone +1 623.399.4918
> mobile +1 480.231.8323
> web CardinalPath.com <http://goo.gl/TuuiO>
>
>
>
> On Mon, May 6, 2013 at 8:50 PM, Z W <mpc8250_at_gmail.com> wrote:
>
>> Hi All
>>
>> For the trunk, what's the common practice to name a version of the trunk?
>> We have a trunk and it's not ready for branching.
>> We also feel that we need a more specific name for the trunk than what we
>> have now called version=trunk.
>> However, we can't be specific since we don't know what the branch name
>> would be while at the same time, we need to perform daily builds for QA
>> testing.
>>
>> What's the best practice in use with SVN ?
>>
>> Thanks
>> Sincerely
>>
>
>
> Connect with us on twitter <http://twitter.com/cardinalpath>, google+<https://plus.google.com/108076800625872227241/posts>
> , facebook <http://www.facebook.com/CardinalPath>,** or linkedin<http://www.linkedin.com/company/cardinal-path>
> .
>
> Catch our next training in Washington May 6-10<http://training.cardinalpath.com/google-adwords-analytics/washington/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=washington-2013-05-06>
> , Los Angeles May 13 - 17<http://training.cardinalpath.com/google-adwords-analytics/los-angeles/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=losangeles-2013-05-13>
> , Boston May 20 - 24<http://training.cardinalpath.com/google-adwords-analytics/boston/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=boston-2013-05-20#2013-05-20>
> , Ottawa May 27-31<http://training.cardinalpath.com/google-adwords-analytics/ottawa/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=ottawa-2013-05-27>
> or See All<http://training.cardinalpath.com/locations/?utm_campaign=cp-s4s&utm_source=cp-email-footer&utm_medium=email&utm_content=see-all>
> .
>
> This email, including any attachments, is for the sole use of the intended
> recipient and may contain confidential information. If you are not the
> intended recipient, please immediately notify us by reply email or by
> telephone, delete this email and destroy any copies. Thank you.
>
>
Received on 2013-05-07 07:14:36 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.