Skip to content
GitLab
菜单
为什么选择 GitLab
定价
联系销售
探索
为什么选择 GitLab
定价
联系销售
探索
登录
获取免费试用
主导航
搜索或转到…
项目
GitLab
管理
动态
成员
标记
计划
议题
议题看板
里程碑
迭代
需求
代码
合并请求
仓库
分支
提交
标签
仓库图
比较修订版本
代码片段
锁定的文件
构建
流水线
作业
流水线计划
测试用例
产物
部署
发布
Package registry
Container registry
模型注册表
运维
环境
Terraform 模块
监控
事件
服务台
分析
价值流分析
贡献者分析
CI/CD 分析
仓库分析
代码评审分析
议题分析
洞察
模型实验
效能分析
帮助
帮助
支持
GitLab 文档
比较 GitLab 各版本
社区论坛
为极狐GitLab 提交贡献
提交反馈
隐私声明
快捷键
?
新增功能
4
代码片段
群组
项目
显示更多面包屑
gitlab-cn
GitLab
提交
acdc0d73
提交
acdc0d73
编辑于
6 years ago
作者:
bikebilly
浏览文件
操作
下载
补丁
差异文件
Change Milestone labels to Release Scoping labels
上级
02c007bd
No related branches found
分支 包含提交
No related tags found
标签 包含提交
无相关合并请求
变更
1
隐藏空白变更内容
行内
左右并排
显示
1 个更改的文件
CONTRIBUTING.md
+5
-5
5 个添加, 5 个删除
CONTRIBUTING.md
有
5 个添加
和
5 个删除
CONTRIBUTING.md
+
5
−
5
浏览文件 @
acdc0d73
...
...
@@ -30,7 +30,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
)
-
[
Subject labels (~wiki, ~"container registry", ~ldap, ~api, etc.)
](
#subject-labels-wiki-container-registry-ldap-api-etc
)
-
[
Team labels (~"CI/CD", ~Discussion, ~Quality, ~Platform, etc.)
](
#team-labels-cicd-discussion-quality-platform-etc
)
-
[
Milestone
labels (~Deliverable, ~Stretch, ~"Next Patch Release")
](
#milestone-labels-deliverable-stretch-next-patch-release
)
-
[
Release Scoping
labels (~Deliverable, ~Stretch, ~"Next Patch Release")
](
#milestone-labels-deliverable-stretch-next-patch-release
)
-
[
Priority labels (~P1, ~P2, ~P3 , ~P4)
](
#bug-priority-labels-p1-p2-p3-p4
)
-
[
Severity labels (~S1, ~S2, ~S3 , ~S4)
](
#bug-severity-labels-s1-s2-s3-s4
)
-
[
Label for community contributors (~"Accepting Merge Requests")
](
#label-for-community-contributors-accepting-merge-requests
)
...
...
@@ -132,7 +132,7 @@ Most issues will have labels for at least one of the following:
-
Type: ~"feature proposal", ~bug, ~customer, etc.
-
Subject: ~wiki, ~"container registry", ~ldap, ~api, ~frontend, etc.
-
Team: ~"CI/CD", ~Discussion, ~Quality, ~Platform, etc.
-
Milestone
: ~Deliverable, ~Stretch, ~"Next Patch Release"
-
Release Scoping
: ~Deliverable, ~Stretch, ~"Next Patch Release"
-
Priority: ~P1, ~P2, ~P3, ~P4
-
Severity: ~S1, ~S2, ~S3, ~S4
...
...
@@ -193,10 +193,10 @@ 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
any issue.
###
Milestone
labels (~Deliverable, ~Stretch, ~"Next Patch Release")
###
Release Scoping
labels (~Deliverable, ~Stretch, ~"Next Patch Release")
Milestone
labels help us clearly communicate expectations of the work for the
release. There are three levels of
Milestone
labels:
Release Scoping
labels help us clearly communicate expectations of the work for the
release. There are three levels of
Release Scoping
labels:
-
~Deliverable: Issues that are expected to be delivered in the current
milestone.
...
...
此差异已折叠。
点击以展开。
预览
0%
加载中
请重试
或
添加新附件
.
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
保存评论
取消
想要评论请
注册
或
登录