Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
GitLab
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
GitLab
Commits
2e88192b
Commit
2e88192b
authored
6 years ago
by
Fabio Busatto
Browse files
Options
Downloads
Patches
Plain Diff
Update regression labeling
parent
d7db1fd5
No related branches found
No related tags found
1 merge request
!6332
CE upstream - 2018-06-29 18:21 UTC
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
PROCESS.md
+4
-4
4 additions, 4 deletions
PROCESS.md
with
4 additions
and
4 deletions
PROCESS.md
+
4
−
4
View file @
2e88192b
...
...
@@ -249,11 +249,11 @@ When a regression is found:
the
[
subject label
](
../CONTRIBUTING.md#subject-labels-wiki-container-registry-ldap-api-etc
)
and any other label that may apply in the specific case
1.
Add the ~bug and ~regression labels
1.
Evaluate the Severity of the regression and add a Severity level
1.
Add the proper milestone and priority label:
-
If the issue is for a feature that was introduced in the previous release.
label with the previous milestone and ~"Next Patch Release"
-
If the issue is for a feature that is introduced in a RC version for the
current release, label with the current milestone and ~"Deliverable"
-
If the regression is ~S1 or ~S2, label 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 the previos release, label with ~"Next Patch Release"
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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment