doug chanco wrote: >The main issue I am trying to get resolved is to lock the record at the pick level , in >case someone does nto check out a code and then tries to edit it when another developer >already has it checked out, since most of our developers use a "pick aware" editor as >long as the record was locked at the pick level, they would get a warning message, the >question is whats the best way to lock program "x" at the pick level?
Why do you feel the need to do that? Are your developers really stepping on each others toes that much? We use subversion, and don't seem to be having a problem with several developers working on the same system with no locking. We did have a problem with Visual source safe and abandoned check outs. The switch to subversion was a relief. One thing that makes it better for us is using an enhanced TCL stacker that has support for a "stack" of programs you are currently working on. Adding a new program to the stack automatically does a diff with trunk so you know if the program has been diddled. It's always a good idea to do a "svn update" before starting work on a new program, to make sure you're working with the latest version. Ian ----------------------------------------- IMPORTANT NOTICE: This message is intended only for the addressee and may contain confidential, privileged information. If you are not the intended recipient, you may not use, copy or disclose any information contained in the message. If you have received this message in error, please notify the sender by reply e-mail and delete the message. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
