Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
11661d1d
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,发现更多精彩内容 >>
提交
11661d1d
编写于
4月 27, 2017
作者:
R
Rémy Coutable
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Move retro/kickoff doc to PROCESS.md
Signed-off-by:
N
Rémy Coutable
<
remy@rymai.me
>
上级
ccb8e693
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
32 addition
and
16 deletion
+32
-16
CONTRIBUTING.md
CONTRIBUTING.md
+0
-13
PROCESS.md
PROCESS.md
+32
-3
未找到文件。
CONTRIBUTING.md
浏览文件 @
11661d1d
...
...
@@ -540,19 +540,6 @@ There are a few rules to get your merge request accepted:
See the instructions in that document for help if your MR fails the
"license-finder" test with a "Dependencies that need approval" error.
## Changes for Stable Releases
Sometimes certain changes have to be added to an existing stable release.
Two examples are bug fixes and performance improvements. In these cases the
corresponding merge request should be updated to have the following:
1.
A milestone indicating what release the merge request should be merged into.
1.
The label "Pick into Stable"
This makes it easier for release managers to keep track of what still has to be
merged and where changes have to be merged into.
Like all merge requests the target should be master so all bugfixes are in master.
## Definition of done
If you contribute to GitLab please know that changes involve more than just
...
...
PROCESS.md
浏览文件 @
11661d1d
## GitLab Core Team & GitLab Inc. Team Contributing Process
---
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
**Table of Contents**
*generated with [DocToc](https://github.com/thlorenz/doctoc)*
-
[
GitLab Co
ntributing Process
](
#gitlab
-contributing-process
)
-
[
GitLab Co
re Team Contributing Process
](
#gitlab-core-team
-contributing-process
)
-
[
Purpose of describing the contributing process
](
#purpose-of-describing-the-contributing-process
)
-
[
Common actions
](
#common-actions
)
-
[
Merge request coaching
](
#merge-request-coaching
)
-
[
Workflow labels
](
#workflow-labels
)
-
[
Assigning issues
](
#assigning-issues
)
-
[
Be kind
](
#be-kind
)
-
[
Feature freeze on the 7th for the release on the 22nd
](
#feature-freeze-on-the-7th-for-the-release-on-the-22nd
)
-
[
Between the 1st and the 7th
](
#between-the-1st-and-the-7th
)
-
[
On the 7th
](
#on-the-7th
)
-
[
After the 7th
](
#after-the-7th
)
-
[
Release retrospective and kickoff
](
#release-retrospective-and-kickoff
)
-
[
Retrospective
](
#retrospective
)
-
[
Kickoff
](
#kickoff
)
-
[
Copy & paste responses
](
#copy-&-paste-responses
)
-
[
Improperly formatted issue
](
#improperly-formatted-issue
)
-
[
Issue report for old version
](
#issue-report-for-old-version
)
...
...
@@ -28,7 +34,7 @@
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
# GitLab Core Team Contributing Process
---
## Purpose of describing the contributing process
...
...
@@ -153,6 +159,29 @@ release should have the correct milestone assigned _and_ have the label
Merge requests without a milestone and this label will
not be merged into any stable branches.
## Release retrospective and kickoff
### Retrospective
After each release, we have a retrospective call where we discuss what went well,
what went wrong, and what we can improve for the next release. The
[retrospective notes] are public and you are invited to comment on them.
If you're interested, you can even join the
[
retrospective call
][
retro-kickoff-call
]
, on the first working day after the
22nd at 6pm CET / 9am PST.
### Kickoff
Before working on the next release, we have a
kickoff call to explain what we expect to ship in the next release. The
[kickoff notes] are public and you are invited to comment on them.
If you're interested, you can even join the
[
kickoff call
][
retro-kickoff-call
]
,
on the first working day after the 7th at 6pm CET / 9am PST..
[
retrospective notes
]:
https://docs.google.com/document/d/1nEkM_7Dj4bT21GJy0Ut3By76FZqCfLBmFQNVThmW2TY/edit?usp=sharing
[
kickoff notes
]:
https://docs.google.com/document/d/1ElPkZ90A8ey_iOkTvUs_ByMlwKK6NAB2VOK5835wYK0/edit?usp=sharing
[
retro-kickoff-call
]:
https://gitlab.zoom.us/j/918821206
## Copy & paste responses
### Improperly formatted issue
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录