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

Re: What's a "trunk" good for? (apart from eating peanuts)

From: B. Smith-Mannschott <benpsm_at_gmail.com>
Date: 2007-01-12 10:09:41 CET

On 1/11/07, Kenneth Wood <kenneth.wood@e2open.com> wrote:
> I'm experimenting with my own idea on layout, and I'm thinking:
> main (rather than trunk)
> releases (equivalent to branches, but with a specific use)
> builds (equivalent to tags, because we tag each build)
> branches (for doing something that isn't a release)
> personal (for people do create a personal branch as a "sandbox"
> to test something in)

A good insight. It makes sense to separate feature branches
("branches", "personal") from release branches ("releases").


> branches and personal can be deleted. The only difference
> is that "branches" is for some activity that is team wide,
> while "personal" is for individual sandbox activity, and
> expected to often delete branches after sandbox work is done.

For "personal" branches we've established /home/USERNAME at the top
level of our main repository, though this is used for much more than
just that. I, particularly, have a lot of smaller projects there
because, honestly, I've not taken the time to rexamine the
repositorie's structure in order to find an "official" place to put
them. It's a little messy.

We don't make use of feature branches for the main projects, but I do
make use of them within some of my /home projects.

// ben

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 12 10:10:08 2007

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.