version control - UCM Clear Case: Hiereachy of streams in one project vs multiple projects -


We have a project and otherwise adding a new piece of functionality to a stable codebase, without fixing a big change. This scheme is making intermediate construction and testing of new facility for different time (maybe one month) and the facility is ending and merged the code of new facility in the main branch in the quality admissible.

The question below is better in case of a clear case of two scenarios:

  1. A new project based on the baseline in the existing project integration stream With the intermediate distribution for the integration of the developing new project, the construction of this new project in a separate project and the integration from the stream created. And ultimately delivers changes to the new project integration stream for the main project (aka or dev).

  2. Using the hierarchy of streams in the main project: Child stream of integration stream (it is called template_in) in main project and a child stream of temp_iit (it is called temp_adv ). Develops a new feature in Temp_dev, from temp_int and temp_int with periodic distribution, and then provides new functionality from temp_int to the main integration stream.

The question is whether you need to create or create a new project Sub-section is a classical one.

In my opinion, both options are quite similar.

The only important difference is the base baseline, which you will be able to choose during the new creation, for this special development effort, Section:

  • For sub-section, you Only will be able to select the base line produced on the original stream.
  • A new project for the mainstream, you will be able to choose any of the baseline as you wish.

In addition to:

  • A new project provides a new location to isolate several streams in a consistent container but if you have new feature development If there is a need to include some small development of the static code made, the quote will be in order.
  • After the development is over, a sub-stream end allows the client to visualize clearly: Distributed original stream will be a natural operation for the merger. In addition, it is possible to keep it up to date in your development stream from the periodic rebase original stream.

So if you have only one stream with clear delivery, the sub-stream option is sufficient.
If you are getting more complex than ever before, then a good project is good.


Comments

Popular posts from this blog

asp.net - Javascript/DOM Why is does my form not support submit()? -

sockets - Delphi: TTcpServer, connection reset when reading -

javascript - Classic ASP "ExecuteGlobal" statement acting differently on two servers -