Skip to content

Github Issues Workflow

Markus Goetz edited this page Mar 17, 2016 · 3 revisions

Process

Triaging: we go over the issues briefly and try to guess tags and assignee and milestone

The milestone is an indication, gold-ticket however are the important issues for the releases. Anything else can be pushed to any milestone at any moment. One should therefore not look at the total amount of open bug in the milestone, only the amount of gold-ticket minus ReadyToTest.

Assignement: issue should be assigned to someone. This means that this bug will be taken care of. If someone think he cannot do it or does not want to do it, the assignement shall be removed.

When an issue is fixed, we set the ReadyToTest tag, so QA can test.

Milestones

Severities

  • sev1-critical:
  • sev2-high:
  • sev3-medium:
  • sev4-low:

Meaning of tags

ReadyToTest

When an issue is fixed, the developer sets the ReadyToTest tag. QA can then test the issue and close it if it is indeed fixed.

gold-ticket

This ticket is an important issue and is blocking the release

blue-ticket / green-ticket

Requested internally by support/sales/...

Needs Info

The reporter should give more information

Server involved

We think the problem is a problem issue. Unfortunately github does not allow to move tasks from one repository to the other. But really, the reporter shoud probably re-open the task on the server and this one be closed.