Jeffrey Blattman wrote:
Allen Gilliland wrote:
the problem is when features are worked on the trunk. then they are
forcefully committed to the next release. which is why it makes sense
to use the sandbox model for feature dev. in my professional life, we
do the same thing, except that we actually create CVS branches for
feature dev, and merge back into the trunk only when the feature is
release ready (well, that's how it works in theory).
This seems like a double edged sword though. If all features are
worked on in branches then we lose some ability to collaborate.
Obviously, at the same time, if someone is going to work on something
that would make the trunk unstable for a while then that's not good
either.
how do we lose ability to collaborate? when i say branch, i mean branch.
they collaborate on the branch, in the same way they collab on the
trunk. there's no diff, other than that the larger project is isolated
from the work of the few.
i wasn't suggesting we do this ... just a case study :)
well, i meant that when people work in separate branches its easier to
lose track of the work they are doing since most people are mainly just
concerned about what's happening in the trunk. obviously working in a
branch is technically no different than working out of the trunk.
-- Allen
