Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
367bb81f
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
367bb81f
编写于
7月 16, 2017
作者:
C
C.J. Jameson
提交者:
Tushar Dadlani
7月 18, 2017
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
readme: remove Glossary, move Vagrant instructions
上级
1dc684a3
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
12 addition
and
24 deletion
+12
-24
README.md
README.md
+12
-24
未找到文件。
README.md
浏览文件 @
367bb81f
...
...
@@ -281,6 +281,10 @@ Known issues:
*
The Native macOS docker client available with docker 1.12+ (beta) or
Community Edition 17+ may also work
## Development with Vagrant
There is a Vagrant-based
[
quickstart guide for developers
](
src/tools/vagrant/README.md
)
.
## Code layout
The directory layout of the repository follows the same general layout
...
...
@@ -362,7 +366,7 @@ It is also recommend that you follow the [developer's mailing list](http://green
since some of the contributions may generate more detailed discussions there.
Once you have your GitHub account,
[
fork
](
https://github.com/greenplum-db/gpdb/fork
)
repository so that you can have your private copy to start hacking on and to
this
repository so that you can have your private copy to start hacking on and to
use as source of pull requests.
Anybody contributing to Greenplum has to be covered by either the Corporate or
...
...
@@ -390,7 +394,7 @@ Apache Software Foundation maintains a list of these licenses under [Category A]
Finally, keep in mind that it is NEVER a good idea to remove licensing headers from
the work that is not your original one. Even if you are using parts of the file that
originally had a licensing header at the top you should err on the side of preserving it.
As always, if you are no
quite sure about the licensing implications of your contributions
As always, if you are no
t quite sure about the licensing implications of your contributions,
feel free to reach out to us on the developer mailing list.
### Coding guidelines
...
...
@@ -413,12 +417,10 @@ We recommend using ```git diff --color``` when reviewing your changes so that yo
don't have any spurious whitespace issues in the code that you submit.
All new functionality that is contributed to Greenplum should be covered by regression
tests that are contributed alongside it. If you are uncertain on how to test
,
or document
your work, please raise the question on the gpdb-dev mailinglist and the developer
tests that are contributed alongside it. If you are uncertain on how to test or document
your work, please raise the question on the gpdb-dev mailing
list and the developer
community will do its best to help you.
### Testing guidelines
At the very minimum you should always be running
```
make installcheck-world```
to make sure that you're not breaking anything.
...
...
@@ -436,10 +438,8 @@ you can be sure whether your changes may need to be forward-ported.
To improve the odds of the right discussion of your patch or idea happening, pay attention
to what the community work cycle is. For example, if you send in a brand new idea in the
beta phase, don't be surprised if no one is paying attention because we are focused on
release work. Come back when the beta is done, please!
You can read more on Greenplum release policy and timing in the RELEASE.md
beta phase of a release, we may defer review or target its inclusion for a later version.
Feel free to ask on the mailing list to learn more about the Greenplum release policy and timing.
### Patch submission
...
...
@@ -465,7 +465,7 @@ Keep in mind that the most common reason for a failed CLA check is a mismatch
between an email on file and an email recorded in the commits submitted as
part of the pull request.
If you can
not figure out why a certain validation check failed, feel free to
If you cannot figure out why a certain validation check failed, feel free to
ask on the developer's mailing list, but make sure to include a direct link
to a pull request in your email.
...
...
@@ -511,22 +511,10 @@ If, on the other hand, the change is in the non-functional part of the code base
(such as fixing a typo inside of a comment block) core team members can decide to
just commit to the repository directly.
## Glossary
* __QD__
Query Dispatcher. A synonym for the master server.
* __QE__
Query Executor. A synonym for a segment server.
## Documentation
For Greenplum Database documentation, please check online docs:
For Greenplum Database documentation, please check
the
online docs:
http://greenplum.org/docs/
For further information beyond the scope of this README, please see
[our wiki](https://github.com/greenplum-db/gpdb/wiki)
There is also a Vagrant-based quickstart guide for developers in `src/tools/vagrant/README.md`.
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录