Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
After we migrated to Clearcase UCM , we have created stream for each sub team.
Often we are facing merging issue as people tend to work with old version without rebase. [ As rebase takes time]
Some times same files are being changed by 2 person in the same stream as they do unreserved checkout.
Is there any set of best practices to be followed in UCM so that we can reduce the merging issues?
[ I think this question should be the community wiki , but i don’t know how to make it as wiki]
Usually, the concurrent modifications are mitigated by:
There are also cases of modifying a generic config file in order to put a local path specific to one programmer’s workstation, but in that case, an hijacked file is prefered to a checkout unreserved (see “Clearcase: checkout and modify but forbid checkin“).