Required OGAT development practices

Troubleshooting and resolving issues related to CCMS Output Generator in the Development Environment remains the responsibility of your company and the developers identified in the license agreement.

Developers must follow the identified practices at all times:

  1. Change files in the Development Environment with caution, since commits of all changes are all-inclusive, rather than selective.
    CAUTION: Commits include all files in the Development Environment. Developers cannot selectively commit some files without committing all files. Developers must test all modifications to all files in the Development Environment before a commit.
  2. Thoroughly test all changes in the Development Environment before you promote them to the Test Environment.
    Tip: If modifications are unclear or problematic, get a fresh copy of the CCMS Output Generator files and start again from the beginning. To do so, use update_local.bat and select O to overwrite your local changes with those currently deployed in Test.
  3. Thoroughly test all changes in the Test Environment before you request their promotion to the Production Environment.
    CAUTION: MadCap Software does not test changes that developers make. All testing is the responsibility of the developer. MadCap Software performs updates of the Production Environment for change management and tracking purposes only.