Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
4d0add35
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
未验证
提交
4d0add35
编写于
11月 08, 2017
作者:
R
Rémy Coutable
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Use the new simpler `Pick into X.Y` labels workflow after the 7th
Signed-off-by:
N
Rémy Coutable
<
remy@rymai.me
>
上级
07ab4ad6
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
23 addition
and
15 deletion
+23
-15
PROCESS.md
PROCESS.md
+23
-15
未找到文件。
PROCESS.md
浏览文件 @
4d0add35
...
@@ -141,21 +141,29 @@ the stable branch are:
...
@@ -141,21 +141,29 @@ the stable branch are:
*
Fixes for security issues
*
Fixes for security issues
*
New or updated translations (as long as they do not touch application code)
*
New or updated translations (as long as they do not touch application code)
During the feature freeze all merge requests that are meant to go into the upcoming
During the feature freeze all merge requests that are meant to go into the
release should have the correct milestone assigned _and_ have the label
upcoming release should have the correct milestone assigned _and_ the
~"Pick into Stable" set, so that release managers can find and pick them.
`Pick into X.Y`
label where
`X.Y`
is equal to the milestone, so that release
Merge requests without a milestone and this label will
managers can find and pick them.
not be merged into any stable branches.
Merge requests without this label will not be picked into the stable release.
Fixes marked like this will be shipped in the next RC for that release. Once
For example, if the upcoming release is
`10.2.0`
you will need to set the
the final RC has been prepared ready for release on the 22nd, further fixes
`Pick into 10.2`
label.
marked ~"Pick into Stable" will go into a patch for that release.
Fixes marked like this will be shipped in the next RC (before the 22nd), or the
If a merge request is to be picked into more than one release it will also need
next patch release.
the ~"Pick into Backports" label set to remind the release manager to change
the milestone after cherry-picking. As before, it should still have the
If a merge request is to be picked into more than one release it will need one
~"Pick into Stable" label and the milestone of the highest release it will be
`Pick into X.Y`
label per release where the merge request should be back-ported
picked into.
to.
For example, if the current patch release is
`10.1.1`
and a regression fix needs
to be backported down to the
`9.5`
release, you will need to assign it the
`10.1`
milestone and the following labels:
-
`Pick into 10.1`
-
`Pick into 10.0`
-
`Pick into 9.5`
### Asking for an exception
### Asking for an exception
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录