[news.eclipse.tools] eclipse, cvs, and a central integration machine?

["JLM" <jlm_one@xxxxxxxxx>]

Hi all -- I Haven't been able to find a discussion about this topic: Has
anyone implemented an extreme programming-style central integration machine,
with a serialized integration process?

We've been doing XP (not the OS...) in our group for over 3 years, using
VisualAge for Java.  We're still on VAJ mostly because of our integration
process: we use the shared repository and a central integration machine in
order to serialize integrations, true XP style.  Once upon a time we tried
doing integrations at our local machines, but inevitably the integrations
were messy, and we ended up back at the central "master" machine.  The
shared repository is really great for comparing any version (or open
edition, or anything you want) from any location.

Now we're ready to move to Eclipse since we all use it in our side projects,
but the only thing we have a big question about is how to implement the
central integration point using CVS -- does anyone have experience doing
this?  Do all developers, for example, refresh their local machines with the
main trunk code, then immediately create a branch locally for their current
work, then merge it into the main trunk at integration time?  This seems
like the most logical thing to do, implementing the rule that no actual
development is done on the main trunk -- it is always the "master image",
and development happens on the branches.  But, since we haven't tackled it
yet, we're not sure.

We're going to spike test it anyway, but any stories or anecdotes would be
greatly appreciated.  If a deeper description of our current process would
help, I can describe it in more detail.

-- Joe