-
Notifications
You must be signed in to change notification settings - Fork 29
Developer Guide
Dave Nicolette edited this page Mar 17, 2021
·
49 revisions
This document was last updated on March 17, 2021.
This information is for developers who want to contribute to the project.
- Don't introduce regressions.
- Don't introduce regressions.
- Don't introduce regressions.
- Try to keep test suite syntax intuitive for Cobol programmers.
- All executable test cases must be passing before a pull request is accepted.
- Documentation on the project wiki must be updated to correspond with the changes you make to the code.
- Don't introduce regressions.
We are not operating on a fixed release cadence at this time. We are building the functionality planned for each release as quickly as we can, and releasing when functionality is complete. It is possible we will establish a release cadence once we have achieved the first stable production-ready release, 1.0.0.
- 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
- Work Flows by Team Role
- Recommended Reading and References
- Standards and Guidelines
- Tools and Build Notes
- Developer Platforms
- Platform-specific Information
- Problems and Fixes
- Problems
- 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