Workflow: How to best land changes on a trunk?

[John Szakmeister]

On Sat, Jan 2, 2010 at 2:04 PM, Max Bowsher <maxb at f2s.com> wrote:
> Consider a project not using PQM, having a central trunk, on which ~6
> developers work, during office hours (so all working simultaneously).

We're in the same boat.

> What's the best (easiest) way for these developers to land their
> branches onto trunk?
>
> Requiring that all developers have a pristine local trunk branch
> (possibly bound), is a possible option, but I'd like to check I haven't
> overlooked anything before I start attempting to make recommendations to
> my colleagues.

We used a local bound branch paradigm as well.  It's worked for us,
but I can imagine it falling over with larger teams.

-John