Skip to content
GitLab
菜单
为什么选择 GitLab
定价
联系销售
探索
为什么选择 GitLab
定价
联系销售
探索
登录
获取免费试用
主导航
搜索或转到…
项目
GitLab
管理
动态
成员
标记
计划
议题
议题看板
里程碑
迭代
需求
代码
合并请求
仓库
分支
提交
标签
仓库图
比较修订版本
代码片段
锁定的文件
构建
流水线
作业
流水线计划
测试用例
产物
部署
发布
Package registry
容器镜像库
模型注册表
运维
环境
Terraform 模块
监控
事件
服务台
分析
价值流分析
贡献者分析
CI/CD 分析
仓库分析
代码评审分析
议题分析
洞察
模型实验
效能分析
帮助
帮助
支持
GitLab 文档
比较 GitLab 各版本
社区论坛
为极狐GitLab 提交贡献
提交反馈
隐私声明
快捷键
?
新增功能
4
代码片段
群组
项目
显示更多面包屑
gitlab-cn
GitLab
提交
35ff10f7
提交
35ff10f7
编辑于
5 years ago
作者:
Lucas Charles
提交者:
Evan Read
5 years ago
浏览文件
操作
下载
补丁
差异文件
Update PROCESS.md - fix grammar
上级
262a1ca1
No related branches found
No related tags found
无相关合并请求
变更
1
隐藏空白变更内容
行内
左右并排
显示
1 个更改的文件
PROCESS.md
+2
-2
2 个添加, 2 个删除
PROCESS.md
有
2 个添加
和
2 个删除
PROCESS.md
+
2
−
2
浏览文件 @
35ff10f7
...
@@ -113,7 +113,7 @@ corresponding exception request to be created.
...
@@ -113,7 +113,7 @@ corresponding exception request to be created.
A level of common sense should be applied when deciding whether to have a feature
A level of common sense should be applied when deciding whether to have a feature
behind a feature flag off or on by default.
behind a feature flag off or on by default.
The following guidelines
s
can be applied to help make this decision:
The following guidelines can be applied to help make this decision:
*
If the feature is not fully ready or functioning, the feature flag should be disabled by default.
*
If the feature is not fully ready or functioning, the feature flag should be disabled by default.
*
If the feature is ready but there are concerns about performance or impact, the feature flag should be enabled by default, but
*
If the feature is ready but there are concerns about performance or impact, the feature flag should be enabled by default, but
...
@@ -125,7 +125,7 @@ For more information on rolling out changes using feature flags, read [through t
...
@@ -125,7 +125,7 @@ For more information on rolling out changes using feature flags, read [through t
In order to build the final package and present the feature for self-hosted
In order to build the final package and present the feature for self-hosted
customers, the feature flag should be removed. This should happen before the
customers, the feature flag should be removed. This should happen before the
22nd, ideally _at least_ 2 days before. That means MRs with feature
22nd, ideally _at least_ 2 days before. That means MRs with feature
flags being picked at the 19th would have
a
quite tight schedule, so picking
flags being picked at the 19th would have quite
a
tight schedule, so picking
these _earlier_ is preferable.
these _earlier_ is preferable.
While rare, release managers may decide to reject picking a change into a stable
While rare, release managers may decide to reject picking a change into a stable
...
...
此差异已折叠。
点击以展开。
预览
0%
加载中
请重试
或
添加新附件
.
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
保存评论
取消
想要评论请
注册
或
登录