Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Léo-Paul Géneau
gitlab-ce
Commits
83bef167
Commit
83bef167
authored
Mar 05, 2018
by
Fabio Busatto
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update CONTRIBUTING.md
parent
5a1da682
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
4 deletions
+11
-4
CONTRIBUTING.md
CONTRIBUTING.md
+11
-4
No files found.
CONTRIBUTING.md
View file @
83bef167
...
@@ -26,7 +26,7 @@ _This notice should stay as the first item in the CONTRIBUTING.md file._
...
@@ -26,7 +26,7 @@ _This notice should stay as the first item in the CONTRIBUTING.md file._
-
[
Type labels (~"feature proposal", ~bug, ~customer, etc.)
](
#type-labels-feature-proposal-bug-customer-etc
)
-
[
Type labels (~"feature proposal", ~bug, ~customer, etc.)
](
#type-labels-feature-proposal-bug-customer-etc
)
-
[
Subject labels (~wiki, ~"container registry", ~ldap, ~api, etc.)
](
#subject-labels-wiki-container-registry-ldap-api-etc
)
-
[
Subject labels (~wiki, ~"container registry", ~ldap, ~api, etc.)
](
#subject-labels-wiki-container-registry-ldap-api-etc
)
-
[
Team labels (~"CI/CD", ~Discussion, ~Edge, ~Platform, etc.)
](
#team-labels-cicd-discussion-edge-platform-etc
)
-
[
Team labels (~"CI/CD", ~Discussion, ~Edge, ~Platform, etc.)
](
#team-labels-cicd-discussion-edge-platform-etc
)
-
[
Priority labels (~Deliverable
and ~Stretch)
](
#priority-labels-deliverable-and-stretch
)
-
[
Priority labels (~Deliverable
, ~Stretch, ~"Next Patch Release")
](
#priority-labels-deliverable-stretch-next-patch-release
)
-
[
Label for community contributors (~"Accepting Merge Requests")
](
#label-for-community-contributors-accepting-merge-requests
)
-
[
Label for community contributors (~"Accepting Merge Requests")
](
#label-for-community-contributors-accepting-merge-requests
)
-
[
Implement design & UI elements
](
#implement-design-ui-elements
)
-
[
Implement design & UI elements
](
#implement-design-ui-elements
)
-
[
Issue tracker
](
#issue-tracker
)
-
[
Issue tracker
](
#issue-tracker
)
...
@@ -126,7 +126,7 @@ Most issues will have labels for at least one of the following:
...
@@ -126,7 +126,7 @@ Most issues will have labels for at least one of the following:
-
Type: ~"feature proposal", ~bug, ~customer, etc.
-
Type: ~"feature proposal", ~bug, ~customer, etc.
-
Subject: ~wiki, ~"container registry", ~ldap, ~api, ~frontend, etc.
-
Subject: ~wiki, ~"container registry", ~ldap, ~api, ~frontend, etc.
-
Team: ~"CI/CD", ~Discussion, ~Edge, ~Platform, etc.
-
Team: ~"CI/CD", ~Discussion, ~Edge, ~Platform, etc.
-
Priority: ~Deliverable, ~Stretch
-
Priority: ~Deliverable, ~Stretch
, ~"Next Patch Release"
All labels, their meaning and priority are defined on the
All labels, their meaning and priority are defined on the
[
labels page
][
labels-page
]
.
[
labels page
][
labels-page
]
.
...
@@ -185,7 +185,7 @@ indicate if an issue needs backend work, frontend work, or both.
...
@@ -185,7 +185,7 @@ indicate if an issue needs backend work, frontend work, or both.
Team labels are always capitalized so that they show up as the first label for
Team labels are always capitalized so that they show up as the first label for
any issue.
any issue.
### Priority labels (~Deliverable
and ~Stretch
)
### Priority labels (~Deliverable
, ~Stretch, ~"Next Patch Release"
)
Priority labels help us clearly communicate expectations of the work for the
Priority labels help us clearly communicate expectations of the work for the
release. There are two levels of priority labels:
release. There are two levels of priority labels:
...
@@ -195,6 +195,13 @@ release. There are two levels of priority labels:
...
@@ -195,6 +195,13 @@ release. There are two levels of priority labels:
-
~Stretch: Issues that are a stretch goal for delivering in the current
-
~Stretch: Issues that are a stretch goal for delivering in the current
milestone. If these issues are not done in the current release, they will
milestone. If these issues are not done in the current release, they will
strongly be considered for the next release.
strongly be considered for the next release.
-
~"Next Patch Release": Issues to put in the next patch release. Work on these
first, and add the "Pick Into X" label to the merge request, along with the
appropriate milestone.
Each issue scheduled for the current milestone should be labeled ~Deliverable
or ~"Stretch". Any open issue for a previous milestone should be labeled
~"Next Patch Release", or otherwise rescheduled to a different milestone.
### Severity labels (~S1, ~S2, etc.)
### Severity labels (~S1, ~S2, etc.)
...
@@ -685,4 +692,4 @@ available at [http://contributor-covenant.org/version/1/1/0/](http://contributor
...
@@ -685,4 +692,4 @@ available at [http://contributor-covenant.org/version/1/1/0/](http://contributor
[
us-english
]:
https://en.wikipedia.org/wiki/American_English
[
us-english
]:
https://en.wikipedia.org/wiki/American_English
[
^1
]:
Please
note that specs other than JavaScript specs are considered backend
[
^1
]:
Please
note that specs other than JavaScript specs are considered backend
code.
code.
\ No newline at end of file
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment