Issue management

We use the radgrad/radgrad issues along with radgrad/radgrad projects to manage work on the system.

We follow these conventions for development:

  1. We document each significant task through a GitHub issue.
  2. We assign each task to a single owner.
  3. We carry out the work on each task in a branch named "issue-NNN", where NNN is the issue number.
  4. We group tasks into a sequence of GitHub milestones named "M1", "M2", etc.
  5. We manage work within a milestone by a GitHub project with the same name as its associated Milestone.
  6. Each GitHub project has three columns: Backlog, In Progress, Done.
  7. When we finish a task, if we do not believe the work warrants review by other team members, then we close its corresponding issue and merge its branch into master. If we want our work reviewed by team members first, then we do not close the issue or merge the branch. Instead, we issue a pull request on master and use Slack to notify members of the need for review.

results matching ""

    No results matching ""