| Table of Contents |
|---|
Developer Environment
- Please setup your development environment according to ONAP guidelines. Doing so eases the review process for the committers and SME's review your submission.
- Also, go through the following link for Policy Framework environment recommendations - Policy Framework Project: Software Development Best Practices
Sprint Planning User Story Estimations
...
13 - 2x Extra Large - 4-6 weeks
JIRA Status Updates
| Move To | When |
|---|---|
| In-progress | The moment you start working on it. |
| Submitted | The review is merged, merge & CSIT jobs are successful. |
| Delivered | The code changes have passed the Sonar, CLM & Integration Gating jobs. |
| Closed | The related OOM charts & documentations are updated. |
Note: Incase you are blocked or need to stop progress on the JIRA for longer duration, please click on "Stop progress" and move it back to "Open" state. We really appreciate if you can provide appropriate comments on the JIRA as well.
Code Submissions
- All code submissions should not degrade the quality of the policy/* project codebase.
- Any sonar, checkstyle issues must be fixed in the current review or a subsequent review.
- The same JIRA should be used for these submissions.
- API changes most likely will require updates to CSIT tests. It is the responsibility of the contributor to provide a code review to update/enhance the CSIT tests for their contribution.
...