FixesOnMaster

Bug Fixes done directly on the master

The Reality has shown, that the child workspaces do not fix all issue in advance before the integration of child workspaces into the master. There are several reasons for doing fixes on the master:

• Merge Conflicts: Even though child workspaces are synchronized with a recent milestone, there is still the chance of getting merge conflict when integrating child workspaces on the master. Since the Integration of child workspaces are done by Release Engineering (RE) a Release Engineer is able to resolve the conflict and commit directly to the master workspace.

• Syntax Errors: Child workspaces are already tested with several compiler versions and platforms, but since it can't be required to compile on all platforms and configutation the chance of a remaining syntax error

• Packaging Errors: not all of the product variants are tested on cws.

• Other errors not detected on child workspace:
  • P1 - Issues
    • forgotten to commit files on cws
    • not included in automated test scenario
    • not included in regression tests