New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

制定开发流程 #71

Open

chirsz-ever opened this issue Jan 20, 2021 · 4 comments

Collaborator

chirsz-ever commented Jan 20, 2021

是否需要单独的 release 分支？
未来是否使用语义化版本号？

Collaborator Author

chirsz-ever commented Jan 30, 2021

理想情况下的主分支中：

每个 commit 应当保持代码合法可构建，且只修改必要的一部分，以方便 BUG 查找；
PR 在合并时应该 rebase 到最新提交并按照第一条所说合并 commit；

Collaborator

royqh1979 commented Feb 1, 2021

是否需要单独的 release 分支？

未来是否使用语义化版本号？

我个人觉得如果不准备单独为某个release发布bug修正版本的话，没必要搞分支

chirsz-ever mentioned this issue

增加mousepressed函数 #76

Closed

Collaborator Author

chirsz-ever commented Mar 13, 2021

@wysaid 咱们搞个审 PR 的流程吧，每个 PR 指定一个负责人来审，不然老是吊着。

Collaborator Author

chirsz-ever commented Sep 4, 2021

如何维护更新日志

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment