多个项目或VOB? [英] Multiple projects or VOBs?

查看:83
本文介绍了多个项目或VOB?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

最近我刚刚接任了ClearCase UCM管理员一职,因此这篇文章的任何建议都会很棒。

I just took over a ClearCase UCM admin position recently, so any input on this post would be great.

我们目前正在将一个VOB用于一个项目。假设我们正在研究的项目是Car X的软件。

We are currently using one VOB with one project. Say the project that we are working on is the software for a Car, CAR X.

现在,有一个VOB,一个组件和一个名为 CAR的项目。每个人(可能是12至15个开发人员)都会在X'上开发汽车软件。

Right now, there is one VOB, one component, and one project called 'CAR X' where everyone (maybe 12-15 developers) works on the software for the car.

将来,我们可能需要为新车开发名为 CAR Y的软件,该软件可能基于用于 CAR的软件X'进行了修改。我们希望这些可以分开。应该在当前VOB中创建一个新的VOB还是仅一个新组件?如果创建了新的VOB和项目,则可以从新项目中导入和修改文件,对吗?在同一个VOB中容纳每个项目要使用一个组件是否有不利之处?

In the future, we will probably need to make software for a new car, called 'CAR Y' which may be based off of the software that is used for 'CAR X' with modifications. We would like these to be somewhat separate. Should a new VOB be created or just a new component within the current VOB? If a new VOB and project is created, the files could be imported and modified from the new project, correct? Is there a downside to having one component used for each project housed in the same VOB?

这很难解释,所以希望我能够理解。如果您需要我提供更多具体信息或回答任何问题,请发表评论。

This is complicated to explain, so hopefully I was able to get the idea across. If you need me to be more specific or answer any questions, please leave a comment.

谢谢!

推荐答案

这取决于您期望在未来几个月/年内创建的vob数量。

It depends on the number of vobs you can expect to create over the next few months /years.

我更喜欢在一个(一般命名的)VOB中创建多个组件,而不是将一个VOB限制为一个组件(尤其是当后一种选择不能撤消时)

I prefer creating multiple components within a (generalically named) vob, rather than limiting a vob to one component (especially when this latter choice cannot be reversed)

您可以轻松地在一个vob中定义100个组件。

就涉及的资源(太多的过程)而言,尝试创建/管理100个vob几乎是不可能的

You easily can define 100 components within a vob.
Trying to create / manage 100 vobs is almost impossible in term of ressources involved (too many processes)

如果您知道,那么您只能创建其中几个,请继续。

但我的观点仍然是:多个组件每个VOB是可以缩放的模型。

If you know you only a few of those vobs to create, go ahead.
But my point remains: multiple components per vob is a model you can scale.

这篇关于多个项目或VOB?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆