Source Control

[Stewart, Mark]

In my opinion only one guy should have source reserved.  If multiple people
have to work on the same source before the code goes into production then
they should both work on the same source.  At that point in time they should
replace the source back into CMS.  This will greatly cut down on generations
because you do not have two people reserving and replacing source a hundred
times so each guy can get a crack at the source hence it's then easier to go
back and look at what changed.  If the two had worked on the source in a
shared directory or one of them has read/write privileges on their account
this would keep your generations to a minimum.  CMS will go and put the
source into a directory somewhere too.  It's probably a good idea to
restrict people to this area.  They should only be able to get there through
CMS.  If you delete something out of CMS it's not good. 


Mark Stewart
Consultant
Victoria's Secret Stores
OpenVMS Alpha  V7.1-1H1
Oracle Rdb     V7.0-1
PowerHouse 4GL 7.10.F4


= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.