Concurrent Development

[Sequeira, Brian]

Hello,

Need clarification from CM gurus. Below is the method suggested for concurrent development for additional projects that are gong to be worked on concurrently which will take over the old process once the project is complete.

Any suggestions/ideas, any additional info we might need to look at. Any help greatly appreciated. Thanks

Shared Components

Once a component has been identified as being a shared component and changes need to be made to that component, an evaluation is needed.  There are several types of changes that can be made to a shared component, with differing effects to the other projects:

·         addition of new functions – as long as the core functions of the component are unchanged, and the new functions do not interact with the old functions, then there should be no impact to the other projects.  A simple regression test should suffice to ensure that no side effects have been introduced

• change of existing functions/no interface change – if an existing function is changed internally with no external change of interface, then this can be treated as above, and a regression test can be run to ensure there are no side effects.  If the internal changes are large, then a branch might be considered
• change of interface/major function change – if the interface to the component changes or major internal , then a branch of the code base would normally be required.  The developer would create a branch in CVS for this component

CVS Branching and Tagging

A branch is used to create two or more parallel lines of development for a configuration item (in our case, Java code).  CVS can be used to create a branch, select a branch to work on, and to merge branches together. 

When merging a branch to the main-line development, a merge process must be accomplished.  The CVS tool assists in this merge process, but if there are conflicts (i.e. changes made to the same code area in two branches), then they must be resolved.  Each merged file should be examined to ensure the merge went smoothly.

Proper CVS operation in this regard can be found at http://www.computas.com/pub/wincvs-howto/ .

In addition, CVS tags can be assigned anywhere on a branch hierarchy, so a build can extract the proper version of code by project.  In the current case, there are three tags available:

·         QAVerx.x.x – used for main line, RTE tasks

• apply_ix  - used for APP UI project (ix = iteration number)
• ccsite_ix used for CC Site project (ix = iteration number)

With the combination of branches and tags each individual project can maintain its own code base and builds.  Each build will extract the proper tagged components and build the correct software for the project.  When the project is complete, the tags will be changed to the main line development build (QAVerXXX) so the project can be included in the standard Juniper build process.

Brian Sequeira
Technology

Juniper Financials
100 S. West St
Wilmington, DE 19801
(302) 255 8144
Page:   1(877) 6273017
Email:   address@hidden
            address@hidden

 

_______________________________________________________

Juniper Bank

"Rated #1 in Customer Confidence"

Gomez Inc., Summer 2001 Internet Credit Card Scorecard

www.juniper.com

_______________________________________________________

This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on.