Code should be checked in when work has progressed to a point that there would significant rework if the file was left checked out for long periods of time. Check in your work at least every day. Remember, views are throw away constructs.
PDH
------------------------------------------
I'm sort of new as a CC admin, but this statement sort of piqued my
interest. Let's pretend that I'm Joe Developer and I'm working in a
personal branch. If I have hacked heavily on a module and I want to check
it in simply as a means of checkpointing my work, is there anything wrong
with that? Or is there some reason that I should discourage this? I do
understand that the code should be functional when we merge back onto a
previous branch, but I didn't think there was a problem in the personal
branch.
TIA
-- -Time flies like the wind. Fruit flies like a banana. steveo@world.std.com- -Stranger things have happened but none stranger than this. Steven W. Orr- Does your driver's license say Organ Donor?Black holes are where God \ -------divided by zero. Listen to me! We are all individuals!---------On Thu, 24 Feb 2000, Sussmilch, John wrote:
=> =>Hi Julie, => => I encountered the same problems with my developers. Part of it is =>related to poor coding practice - checking in files that don't compile is =>something Configuration management is supposed to discourage.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:23:25 EDT