Re: Repository without a trunk

We have a trunk which maps to our production environment. We create branches from the trunk for different bugfixes/new features. Those changes are then merged into the trunk working copy on the QA server and after testing, they are committed to the trunk and production.

It sounds like maybe you should be using tags for different releases of the software. You can use branches off of the trunk to

A. Work on different releases of the software.
B. Have dev branches for developers to test out their code.

You don't necessarily need the trunk... Its just a branch really that contains the latest version of the software by convention.

Russ
Sent wirelessly via BlackBerry from T-Mobile.

-----Original Message-----
From: <brian-dev@kaiserdigital.com>
Date: Wed, 26 Jul 2006 05:52:20
To:<users@subversion.tigris.org>
Subject: Repository without a trunk

Hi
 
 
 
I work in an environment where each group of features is pre-assigned to a release and each release corresponds to a branch in the source code repository. Consequently, our subversion has been setup without a trunk. All work is done on a branch and each branch is created from another branch.
 
 
 
 
 
I'm looking for as much feedback as possible on this decision (i.e. not having a trunk). What are the benefits; what are the drawbacks?
 
 
 
Thanks
 
Received on Wed Jul 26 15:59:35 2006