Assumptions

• Most of the work in deployment customizations are to do with

localization and customizing modules.

• Unlike a release branch the deployment customizations might have

enhancements (release branch only has bug fixes)

• Keeping track of your changes in one branch to apply it to the

other is a hassle for most developers, especially given the time pressures of a deployment

• Though we have recommended the application of fixes to the trunk at

the same time you do it on the branch, this has not happened and is seems not likely to happen.

• Automated merging cannot be trusted especially with a large diff

between the deployment branch and the trunk. Also the deployment branch might have customizations you do not want to see in the trunk. Thus the only option is manual merging.

Thus the only option we have is work with the delta we have between a release/deployment branch. I would like to suggest the following:

• Use a visual merge tool (dedicated to the task of merging) to make

it easier. I am using meld ( http://meld.sourceforge.net/ ).

• Each module/library owner should then use this tool to look at the

diffs and then merge what is relevant back into the trunk.

• We need to assign a list of module/library owners so that all areas

are covered. Also they are the best people to know which merges are relevant.

• Similar to the release cycle we probably need to have a merge cycle

to ensure that all the bug fixes, relevant enhancements get back into the trunk. The only way to make the merge a success is if all areas are covered in one hit so we all need to work together on this.

• Any clear fixes/enhancements we can identify should be recorded in

the bug/enhancement tracker for future reference purposes.