accounting/bench
2
0
Fork 0
mirror of https://github.com/frappe/bench.git synced 2025-01-10 00:37:51 +00:00
Code Issues Releases Activity

[fix] branching details

Browse Source
This commit is contained in:
Saurabh 2017-07-24 12:40:48 +05:30
parent 3b2c1ca4b3
commit c1767f8a43
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
bench/docs/branch_details.md Normal file
View File

@ -0,0 +1,13 @@
### ERPNext/Frappe Branching
#### Branch Description
- `develop` Branch: All new feature developments will go in develop branch
- `staging` Branch: This branch serves as a release candidate. Before a week, release team will pull the feature from develop branch to staging branch.
EG: if the feature is in 25 July's milestone then it should go in staging on 19th July.
- `master` Branch: Community release.
- `hotFix` Branch: mainly define for support issues. This will include bugs or any high priority task like security patches.
#### Where to send PR?
- If you are working on a new feature, then PR should point to develop branch
- If you are working on support issue / bug / error report, then PR should point to hotfix brach
- While performing testing on Staging branch, if any fix needed then only send that fix PR to staging.