CalvinKirs opened a new issue #3110:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/3110
I read RIP-14 RocketMQ Community Operation Conventions, I think we also
need to make such a specification, as follows
1:Test
Standardized testing can reduce the cost of review and quickly find problems
to confirm the problem, so the test code link is more important than the code
itself to a certain extent. When new code is submitted, we should also care
about the quality of the test code.
2:Commit Message
Good commit messages should contain some contextual information. We can get
the specific work of the commit from the commit messages, and we can use git
instructions to quickly track related issues.
3:Isuess
Good issues labeling and naming can help us organize existing problems in
the community, and can also effectively avoid repeated problems
Label Conventions
ISSUE Label Conventions
Each issue needs to be labeled. Generally, an issue needs to have two types
of labels, including
Type
new feature
bug
enhancement
test
code style
doc
question
discuss
wontfix
duplicate
...
Module
server
remote
service
spi
...
4:Pull Request
A good pull request can help the reviewer quickly understand the purpose of
the request and improve the efficiency of the reviewer. We should make format
requirements for the relevant requests and organize the standard documents.
Related documentation referenceļ¼
https://docs.google.com/document/d/1fo_Z4_nUOyykkmQOE2kEmxcLwhhFiQENQwQiy852XUM/edit#heading=h.nwczedg8v2na
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
