Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
爱吃血肠
spring-framework
提交
0b97cc9e
S
spring-framework
项目概览
爱吃血肠
/
spring-framework
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
S
spring-framework
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
前往新版Gitcode,体验更适合开发者的 AI 搜索 >>
提交
0b97cc9e
编写于
5月 05, 2019
作者:
S
Stephane Nicoll
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Polish
上级
7d0a4947
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
8 addition
and
9 deletion
+8
-9
CONTRIBUTING.md
CONTRIBUTING.md
+8
-9
未找到文件。
CONTRIBUTING.md
浏览文件 @
0b97cc9e
...
...
@@ -46,14 +46,13 @@ When ready create a ticket in the [GitHub issue tracker](https://github.com/spri
#### Ticket Lifecycle
When an issue is first created, it may not be assigned and will not have a fix version.
Within a day or two, the issue is assigned to a specific committer and the target
version is set to "Waiting for Triage". The committer will then review the issue, ask for
further information if needed, and based on the findings, the issue is either assigned a fix
version or rejected.
When a fix is ready, the issue is marked "Resolved" and may still be re-opened. Once a fix
is released, the issue is permanently "Closed". If necessary, you will need to create a new,
When an issue is first created, it is flagged
`waiting-for-triage`
waiting for a team
member to triage it. Within a day or two, the issue will then be reviewed and the team
may ask for further information if needed. Based on the findings, the issue is either
assigned a fix version or declined.
When a fix is ready, the issue is closed and may still be re-opened. Once a fix is
released, the issue can't be reopened. If necessary, you will need to create a new,
related ticket with a fresh description.
#### Submit a Pull Request
...
...
@@ -84,7 +83,7 @@ multiple edits or corrections of the same logical change. See
for an overview of streamlining commit history.
1.
Format commit messages using 55 characters for the subject line, 72 characters per line
for the description, followed by the issue fixed, e.g.
`
Fixes #
22276`
. See the
for the description, followed by the issue fixed, e.g.
`
Closes gh-
22276`
. See the
[
Commit Guidelines section of Pro Git
](
https://git-scm.com/book/en/Distributed-Git-Contributing-to-a-Project#Commit-Guidelines
)
for best practices around commit messages and use
`git log`
to see some examples.
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录