Update CONTRIBUTING.md

PoeBlu · Dec 6, 2018 · e79010a · e79010a
1 parent 0117e0b
commit e79010a
Showing 1 changed file with 6 additions and 1 deletion.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -135,4 +135,9 @@ git push
 
 ## Bug Handling
 
-If a user reports unexpected behavior, it's not necessarily a bug. The issue supervisor has to identify, it's indeed an unintended behavior or just unintuitive behavior for the user reporting the issue. The first level is `bug/0-needs-info`, which means that it has been reported, but the information provided is not sufficient to reproduce the problem. As soon as the user has provided a reproduction, that the issue supervisor can reproduce, the issue goes into the next state: `bug/1-repro-available` . This state implies, that there is a reproduction available, which needs to be looked at by a support engineer. As soon as a Prisma support engineer looked into this reproduction and can actually reproduce the issue, too, the issue get be moved into the last stage: `bug/2-confirmed` . From this moment on, it's officially a bug. This bug can now be added to the Project `PM Core`. From here it will be picked up in a weekly planning session and scheduled for the engineering team.
+If a user reports unexpected behavior, it's not necessarily a bug. The issue supervisor has to identify, it's indeed an unintended behavior or just unintuitive behavior for the user reporting the issue.
+The first level is `bug/0-needs-info`, which means that it has been reported, but the information provided is not sufficient to reproduce the problem.
+
+As soon as the user has provided a reproduction, that the issue supervisor can reproduce, the issue goes into the next state: `bug/1-repro-available`. This state implies, that there is a reproduction available, which needs to be looked at by a support engineer. As soon as a Prisma support engineer looked into this reproduction and can actually reproduce the issue, too, the issue get be moved into the last stage: `bug/2-confirmed`.
+
+From this moment on, it's officially a bug. This bug can now be added to the Project `PM Core`. From here it will be picked up in a weekly planning session and scheduled for the engineering team.