[p4] Does this workflow seem odd to you?

[David Weintraub]

On 5/11/07, Ivey, William <william_ivey at bmc.com> wrote:
> That's the problem - they aren't submitting at all until after a
> week or two of resolving changes into their local file. I don't
> see anything intrinsically bad about that

Two weeks without syncing or submitting changes? There's your real
problem. Many shops have a policy of submitting changes before a
developer leaves for the day. Some feel that's a little extreme, but
when I was handling ClearCase (which used private developer branches),
I got concerned when a developer had gone three days without
delivering their changes.

Unless a developer is working on long term changes (like a feature
that will be added not to the next release, but some release after
it), they should be biting off smaller chucks of changes, and
submitting them on a regular (i.e. almost daily) basis.

If a developer needs code checked out longer than a day or two (like
working on a feature in a future release), they should have a separate
feature branch. AND, they should be merging changes from the main
branch into that feature branch on a regular basis.

--
David Weintraub
qazwart at gmail.com