1. Evaluate the priority and add a [Priority label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#bug-priority-labels-p1-p2-p3-p4)
1. Evaluate the priority and add a [Priority label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#bug-priority-labels-p1-p2-p3-p4)
1. Schedule the issue in order to get it fixed as soon as possible, based on severity and priority, following these guidelines:
1. Schedule the issue in order to get it fixed as soon as possible, based on severity and priority, following these guidelines:
- If the regression is ~S1 or ~S2, set the current milestone
- If the regression is ~S1 or ~S2, set the current milestone
- If the regression was introduced in a RC of the current release, label with ~Deliverable
- If the regression was introduced in a RC of the current release, label with ~Deliverable
- If the regression was introduced in the previos release, label with ~"Next Patch Release"
- If the regression was introduced in the previos release, label with ~"Next Patch Release"
- If the regression is ~S3 or ~S4, it can be scheduled for later milestones
When a new issue is found, the fix should start as soon as possible. You can
When a new issue is found, the fix should start as soon as possible. You can
ping the Engineering Manager or the Product Manager for the relative area to
ping the Engineering Manager or the Product Manager for the relative area to
