Forgot to include the list in the reply!
Vandenbroucke Sander schrieb:
> Hi,
>
> We are working with SVN for a couple of months now but we're not quite
> on top of it.
> What we struggle with most is a good branch policy. Now we have each a
> branch in which we do our daily development for new features as well as
> for bug fixes. When things are tested they get merged into trunk. This
> leads to many intermediate commits to our branches in order to be able
> to merge a small bug fix to trunk without merging any ongoing work on a
> new feature.
>
> Apart from bug fixes and new features we also have 'test software'. This
> is highly experimental software mainly to be able to trace and diagnose
> bugs. Most of these tests get obsolete once the bug is fixed. Some stay
> alive.
>
> Any ideas on how to handle this situation?
>
> Sander.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
Why the need for every developer to have a separate branch? Let all work
on the trunk and just use branch for releases and experimentell stuff.
After all having more than one developer work on the same code base is
what subversion is all about. If you need greater controll use a checkin
checkout model.
Regards
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 10 11:04:34 2007