"Tal, Shachar" <[EMAIL PROTECTED]> writes: > > From: Shachar Shemesh [mailto:[EMAIL PROTECTED] > > > > Lets separate what the app can do, with the way it is being > > typically deployed. I am yet to see a deployment of clearcase > > where developers were given commit access to certain parts of a > > program, but not to others. You can define code owners for code > > areas, and enforce that each commit to a given code be approved > > (or at least acknoledged) by the relevant owner. This can be done > > in CVS too, however.
UNIX permissions would suffice, actually, on a per-module basis. > While agreeing with most of your post, I can testify to previously > working for a company with a state-of-the-art ClearCase > implementation. Each R&D team has it's own branch to work on, and > only the integration team merged files from these branches to our > /main branch. Furthermore, each feature had its own branch, which > was merged to relevant team branches once matured and tested. I may be missing something, but at first glace there is nothing here that cannot be done with CVS. Ouch! What have I done?! I am an IBM employee, and now I am saying that an amateurish piece of half-baked open source code can do what a "state of the art" instance of proprietary "software configuration" tool can do? Wait... I use CVS at work... ;-) > The company I work for currently does not allow engineers access to > code they have no business reading in the first place. They must have a *really* good reason for it. The disadvantages of this approach are too many to count. The more code your programmers read the better code they will write. External security restrictions or "clean room" requirements can justify this, but hardly anything else. In any case, the above exceptions should be just that - exceptions. Usually companies write more code for internal consumption than for customers. -- Oleg Goldshmidt | [EMAIL PROTECTED] ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
