Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

A JIRA issue enters the sprint needing no further elaboration. The goal is to close out the issue before the end of the sprint. The steps below list the process through with an issue is closed:1.
  1. JIRA issue set to "in progress"

...

  1. Completion criteria are met

...

  1. Unit tests have been written

...

...

  1. Changeset pushed to personal repository
  2. Local build succeeds

...

  1. Code review completed
7. CI passed
  1. Personal repository merged to main repository

...

  1. CI passed
  2. JIRA issue set to "resolved"

...

  1. QA completed

...

  1. JIRA issue set to "closed"

Code Review

Per the DCDT development team's policy, code reviews must be completed within three core working hours of the time that they are opened. All assigned reviewers must complete the review within that time. Currently, the entire development team is listed on every code review. Code reviews are of the highest priority because failure to complete code reviews blocks team progress. Before a code review can be marked as complete all comments from team members must be addressed.

...