...
- Integration tests between different components can be started early and in parallel.
- Code reviews to be strict and strengthened
- A code review checklist can be maintained (including checkstyles, coverage, tests done, functionality covered, pending work , definition of done etc), we pushed code that did not build and did not have tests.
- Internal demos can be started and made more frequent, when there is a demoable component.
- Dedicated page of instructions for new joiners for Checkstyle/SONAR etc.
- Good knowledge of Policy and the Policy Framework codebase and practices work.
- Add good descriptions of the reason for a commit and an explanation of the commit in comments in the review
- How does our architecture align with the existing CLAMP springboot approach?
- Understand the architectural path into the future.
Overall:
- Wiki page should be updated and kept aligned before design start, as component functionality can be agreed among all. +
- Jira tickets can be updated with new subtasks, an acceptance criteria defined and agreed per sub-task
- Jira Tickets can be updated with progress and gerrit links, if acceptable.
...