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

Re: Trunk and Branch

From: VK Sameer <sameer_at_collab.net>
Date: 2005-10-14 12:15:21 CEST

On Fri, 2005-10-14 at 03:56 +0000, Sri wrote:
> Hi,
> I have a doubt in Mainline(trunk) of developement and branch.Im clear
> about the usage of trunk and branch and the concepts of branching and
> merging. But my doubt is , How it is represented by subversion?

Subversion doesn't do anything to restrict use of trunk, branches, or
tags, or any other name. This is the recommended usage, helped by hook

> At one time, in my project, they didnt use the mainline (trunk) for
> development and its not updated at all(not used).For every release
> they are keeping on branching and merges between the branches. can we
> proceed like this?


> My question is, do we have any internal representation by subversion
> that this codebase is mainline(trunk)and this dir is branch...


> Also, please suggest me, whether at somepoint we should merge the
> branches to trunk or we can proceed with braching for new release from
> existing brach and then merging between branches?

It depends on your project's development policy. If you'd like to work
on trunk and branching for releases, like the Subversion project, yes,
merging everything to trunk makes sense. Otherwise keep doing what
you're doing now, especially if people are happy with the process.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 14 12:17:31 2005

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.