Promotion The process for a new feature DP 0 1. The DP exists or will be created automatic. Feat 1 2. The branch will be created automatic for the view. 1 2 3. The developer will add whats specified. 4. When the task is tested (FT=“OK”) and complete, the developer will promote this change to the DP- branch by setting an attribute PRO=“INT”. FT=“OK” PRO=“INT” 1 5. When IM recieves the FT=“OK” and PRO= “INT”, the merge to the DP will be initiated. PRO=“IT1 TEST” 6. When IM have completed the merge and compiled all elements, a promotion of next state change will be performed. PRO will initiate TM for different test cases. IT1 7. When TM have performed all testcases defined for the integrationmodel and approved the tests, a baseline for IT model will be executed. State=“Submit, assigned, open, integrate, test,close”
Integration with Clearcase file version Reason for change foo.c184.108.40.206fixed bug bar.c2.7. frams.c4.3added doc frap.c220.127.116.11fixed Ralph’s problem blarg.c7.2 main.c3.7Bill will like this file version Change ID Reason for change foo.c18.104.22.168QTCth03173 SegVs when user directory is 700 permissions bar.c2.7QTCth03520 delete children core dumps xxigt(1) on dec frams.c4.3QTKqa00018 reports of mailfile(1) hanging forever frap.c22.214.171.124QTKqa00656 Need an example of read access control blarg.c7.2QTKqa00775 mailfile(1) produces garbage in the Defaults field main.c3.7QTKqa00958 atoi(1) fails if there are more than 9 integers Meaningful Release Notes Meaningless Release Notes
Implementation 025 Part 1 Part 2 Part 3 CM-PlanCCB Model and CR-process Effort
Your consent to our cookies if you continue to use this website.