Development Processes

Development work of PRADO can be roughly classified as feature development and bug fixes. The following steps should be followed as a general guidance.

Feature Development

• Open ticket: create a ticket to describe the feature to be developed. This ticket may be created by a user or a developer. The decision to develop this feature should be approved by a project leader.
• Design: detailed design for the feature. For complex features, design documents should be prepared and saved under the docs directory.
• Review: the design should be reviewed and approved by a project leader.
• Implementation: implementation of the feature design. For complex features, unit tests and/or functionality tests should also be written.
• Test: run unit and/or functionality tests to verify the correctness of the code.
• Code review: the code should be reviewed by another developer.
• Check-in: check in the code to the PRADO repository.
• Close ticket: update the ticket status to fixed.

Bug Fixes

• Open ticket: create a ticket to describe the bug. This ticket may be created by a user or a developer. It is recommended to write a testcase to reproduce the bug. The testcase may be saved under tests.
• Fix: fix the bug.
• Test: run unit and/or functionality tests to verify the correctness of the code.
• Code review: the code should be reviewed by another developer.
• Check-in: check in the code to the PRADO repository.
• Close ticket: update the ticket status to fixed.

Release

• Build
• Test
• Package
• Release