Developer Guide

Home

This document was last updated on February 11, 2021.

This information is for developers who want to contribute to the project.

"Definition of Done" checklist for changes

1. Don't introduce regressions.
2. Don't introduce regressions.
3. Don't introduce regressions.
4. Try to keep test suite syntax intuitive for Cobol programmers.
5. All executable test cases must be passing before a pull request is accepted.
6. Documentation on the project wiki must be updated to correspond with the changes you make to the code.
7. Don't introduce regressions.

Documentation for Developers

• General
  • Overall Design Goals
  • Implementation Notes
    • Cobol Coding Styles
    • Compiler Compatibility
    • Nature of the Beast Considerations
    • Approach to Mocks
    • Batch I/O Stubbing
  • Contributing
    • Team Roles and Responsibilities
    • How We Use Github Issues, Commit Message Standards
    • Developer Work Flows
    • Recommended Reading and References
• Standards and Guidelines
  • Help the User
  • Java Coding Standards
  • Versioning
  • Exception Handling
  • Logging
  • Internationalization
  • Copyright Notice
• Tools and Build Notes
  • Tools and Versions
  • Helper Scripts
• Developer Platforms
  • Choosing a Developer Platform
  • Certified Developer Platforms
  • Platform Certification
• Platform-specific Information
  • Unix and Linux Platform Guide
  • Microsoft Windows Platform Guide
  • Apple OS X Platform Guide
  • IBM z/OS Platform Guide
• Problems and Fixes
  • Problems
    • FreeBSD 12 IntelliJ IDEA issue
    • FreeBSD 12 Eclipse IDE issue
  • Fixes
    • [FIXED] Eclipse IDE: Enable Preview Features
    • [FIXED] FreeBSD 12 pipefail issue
    • [FIXED] IntelliJ IDEA: Change the JDK Version
    • [FIXED] Jacoco Issues
    • [FIXED] SonarQube Conflict with JDK15 preview features
    • [FIXED] SonarQube runs out of metaspace on Ubuntu Linux
    • [FIXED] VSCode: Enable Preview Features