Skip to content

Commit 43c6883

Browse files
committed
Add contributing guide.
1 parent 140655d commit 43c6883

File tree

1 file changed

+56
-0
lines changed

1 file changed

+56
-0
lines changed

CONTRIBUTING.md

+56
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
# Contributing to WCDB
2+
Welcome to [report issues](https://github.com/Tencent/wcdb/issues) or [pull requests](https://github.com/Tencent/wcdb/pulls). It's recommended to read the following Contributing
3+
Guide first before contributing.
4+
5+
## Issues
6+
We use Github Issues to track public bugs and feature requests.
7+
8+
### Search Known Issues First
9+
Please search the existing issues to see if any similar issue or feature request has already been filed. You should make sure your issue isn't redundant.
10+
11+
### Reporting New Issues
12+
If you open an issue, the more information the better. Such as detailed description, screenshot or video of your problem, logcat or code blocks for your crash.
13+
14+
## Pull Requests
15+
We strongly welcome your pull request to make WCDB better.
16+
17+
### Branch Management
18+
There are three main branches here:
19+
20+
1. `master` branch.
21+
* It is the latest (pre-)release branch. We use `master` for tags, with version number `1.1.0`, `1.2.0`, `1.3.0`...
22+
* **Don't submit any PR on `master` branch.**
23+
2. `dev` branch.
24+
* It is our stable developing branch. After full testing, `dev` will be merged to `master` branch for the next release.
25+
* **You are recommended to submit bugfix or feature PR on `dev` branch.**
26+
3. `hotfix` branch.
27+
* It is the latest tag version for hot fix. If we accept your pull request, we may just tag with version number `1.1.1`, `1.2.3`.
28+
* **Only submit urgent PR on `hotfix` branch for next specific release.**
29+
30+
Normal bugfix or feature request should be submitted to `dev` branch. After full testing, we will merge them to `master` branch for the next release.
31+
32+
If you have some urgent bugfixes on a published version, but the `master` branch have already far away with the latest tag version, you can submit a PR on hotfix. And it will be cherry picked to `dev` branch if it is possible.
33+
34+
```
35+
master
36+
37+
dev <--- hotfix PR
38+
39+
feature/bugfix PR
40+
```
41+
42+
### Make Pull Requests
43+
The code team will monitor all pull request, we run some code check and test on it. After all tests passed, we will accecpt this PR. But it won't merge to `master` branch at once, which have some delay.
44+
45+
Before submitting a pull request, please make sure the followings are done:
46+
47+
1. Fork the repo and create your branch from `master` or `hotfix`.
48+
2. Update code or documentation if you have changed APIs.
49+
3. Add the copyright notice to the top of any new files you've added.
50+
4. Check your code lints and checkstyles.
51+
5. Test and test again your code.
52+
6. Now, you can submit your pull request on `dev` or `hotfix` branch.
53+
54+
## License
55+
By contributing to WCDB, you agree that your contributions will be licensed
56+
under its [BSD LICENSE](https://github.com/Tencent/wcdb/blob/master/LICENSE.txt)

0 commit comments

Comments
 (0)