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

Re: [Subclipse-users] Recommendations for branch/tag structure for multi-developer project

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-14 00:31:12 CET

I suspect you meant to send this to users@subversion.tigris.org, not
Subclipse. You will certainly hit a wider audience with more opinions.

I would create a branch for a task, perhaps with a by developer grouping
layer above it to break up the tree. Then just delete the branches when
they are done.

Personally, I prefer the model that Subversion (and to a much lesser extent
Subclipse) follow. Generally people work on trunk. Development branches
are reserved for special cases such as large or length changes. Release
branches are created from trunk and then stabilized by selectively
backporting fixes from trunk to the release branch.

There are literally a hundred different ways to approach this and they all
have pluses and minuses.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Mar 14 00:31:29 2006

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

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