From e79010a182dfe8e10e780ff304aae41e3b18f61a Mon Sep 17 00:00:00 2001 From: Tim Suchanek Date: Thu, 6 Dec 2018 15:47:29 +0100 Subject: [PATCH] Update CONTRIBUTING.md --- CONTRIBUTING.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 04fe4807d5..3c75bd1bee 100644 --- 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.