2011/8/29 Lorenz Mösenlechner <
moesenle@in.tum.de>:
> normally, people develop in trunk and whenever the code is ready, a
> release is done.
That is how we do it, too.
Developing in trunk minimizes merging, and releases provide a sequence
of stable integration points for users.
You can still use a branch for highly experimental changes, merging
them back into trunk when they are ready. But, we rarely find that
necessary or convenient.
--
joq