We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PaddlePaddle/Paddle使用git-flow分支模型,切换的issue:PaddlePaddle/Paddle#250 ,文档中亦有对PaddlePaddle分支规范的介绍。
PaddlePaddle的主版本库遵循git-flow分支规范。其中: master分支为稳定(stable branch)版本分支。每一个master分支的版本都是经过单元测试和回归测试的 版本。 develop分支为开发(develop branch)版本分支。每一个develop分支的版本都经过单元测试,但并没有经过回归测试。 release/版本号分支为每一次Release时建立的临时分支。在这个阶段的代码正在经历回归测试。
PaddlePaddle的主版本库遵循git-flow分支规范。其中:
建议paddle-mobile采用同样的git分支管理模型,新建一个develop分支,日常的开发工作都提交到develop分支。
paddle-mobile应采用Pull Request的方式提交代码,禁止直接push,所有的代码都需要人工review。贡献代码的流程可以参考Paddle相关文档:如何贡献代码
Pull Request
push
代码强制review,reviewer操作方式:https://help.github.com/articles/approving-a-pull-request-with-required-reviews/
merge PR 时,自动关联的关键字 issue: https://help.github.com/articles/closing-issues-using-keywords/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
PaddlePaddle/Paddle使用git-flow分支模型,切换的issue:PaddlePaddle/Paddle#250 ,文档中亦有对PaddlePaddle分支规范的介绍。
建议paddle-mobile采用同样的git分支管理模型,新建一个develop分支,日常的开发工作都提交到develop分支。
The text was updated successfully, but these errors were encountered: