Greg@QSI
September 11th, 2003, 07:25 PM
So my company is debating how to manage a body of engine code that is used by multiple projects. Currently any project that makes a change during its development, including when under deadline pressure, is seen by all other projects (on CVS). This, in my opinion, is bad. Especially for the long term health of the code.
I want to institute a body of code that is not directly included in any one project, and is updated only after code reviews. That body of code is then merged down to individual projects to spread changes.
Others are resistant to this idea because they fear the extra work of additional merging and not getting fixes in a timely fashion.
What are the experiences of other people in this area?
-Greg!
I want to institute a body of code that is not directly included in any one project, and is updated only after code reviews. That body of code is then merged down to individual projects to spread changes.
Others are resistant to this idea because they fear the extra work of additional merging and not getting fixes in a timely fashion.
What are the experiences of other people in this area?
-Greg!