Repository Layout

Guys,

this has probably asked a zillion times, but I could not find suitable hits
in the archive.

I am in the process of setting up a new repository layout for our dev group.
We are moving away from the concept of bigger releases every few months to
rather small feature releases on a weekly basis, just when stable code for
the relevant features is ready. On another project the release frequency
even could become shorter, a release every day or two.

The old concept was easy. Mainline-dev on the trunk, that branches to
release- or hotfix-branches when the product is release. Fixes were merged
from the branch to the trunk.

But now noone knows when which feature becomes availabe. In addition we have
a test systems which all code has to go through before its release. And in
exactly this case its quite possible that one feature is released earlier
than another which appeared on the test system earlier.

I´m not too happy with the concept of feature branches as I suppose I´m not
able to find things in the repo sooner or later as all will become cluttered
with hundreds of feature branches.
How do I ensure that no developer will kill his colleagues code when
releasing his code to the test system. Do I have to set up a test branch?
What happens on the trunk? Only "RTM" code there?

How do you handle this?

Daniel
Received on Tue Oct 18 08:45:03 2005