SCM questions
Hi all,
I regrouped all my questions in one topic :D
Thank you for your answers.
Is it possible to define new attributes for files and folders (notion of meta-data), the value of which must be exploitable in different processes, such as checking naming rules, checking content and an installation method in the target environments...
Is it to merge more than two versions at the same time (in the case of parallel processing of multiple change requests on separate branches).
When a new deliverable version is finalised, i should be able to select the change requests to be included. In such a case, the tool must check the consistency of the configuration, or offer to re-establish this consistency by merging code. For example, if a source code has been successively modified according to requests D1, D2 and D3, and if D1 and D3 are to be delivered, the tool must detect that D2 must also be delivered because of this file, as well as all the files modified for D2. right?
Is it possible to have for each Work Item a link corresponding to the baseline where it is included ? not only a link to change sets
Tarik
I regrouped all my questions in one topic :D
Thank you for your answers.
Is it possible to define new attributes for files and folders (notion of meta-data), the value of which must be exploitable in different processes, such as checking naming rules, checking content and an installation method in the target environments...
Is it to merge more than two versions at the same time (in the case of parallel processing of multiple change requests on separate branches).
When a new deliverable version is finalised, i should be able to select the change requests to be included. In such a case, the tool must check the consistency of the configuration, or offer to re-establish this consistency by merging code. For example, if a source code has been successively modified according to requests D1, D2 and D3, and if D1 and D3 are to be delivered, the tool must detect that D2 must also be delivered because of this file, as well as all the files modified for D2. right?
Is it possible to have for each Work Item a link corresponding to the baseline where it is included ? not only a link to change sets
Tarik
One answer
No, no, yes, and too expensive.
(:-).
Cheers,
Geoff
tmlahi wrote:
(:-).
Cheers,
Geoff
tmlahi wrote:
Hi all,
I regrouped all my questions in one topic :D
Thank you for your answers.
Is it possible to define new attributes for files and folders (notion
of meta-data), the value of which must be exploitable in different
processes, such as checking naming rules, checking content and an
installation method in the target environments...
Is it to merge more than two versions at the same time (in the case of
parallel processing of multiple change requests on separate
branches).
When a new deliverable version is finalised, i should be able to
select the change requests to be included. In such a case, the tool
must check the consistency of the configuration, or offer to
re-establish this consistency by merging code. For example, if a
source code has been successively modified according to requests D1,
D2 and D3, and if D1 and D3 are to be delivered, the tool must detect
that D2 must also be delivered because of this file, as well as all
the files modified for D2. right?
Is it possible to have for each Work Item a link corresponding to the
baseline where it is included ? not only a link to change sets
Tarik