I think even nit/trivial changes need to get reviewed and documented in JIRA - as trivial/nit is a very subjective concept, and some "nit" change could cause risk to the project.
Thanks, Junping tison <wander4...@gmail.com> 于2020年1月9日周四 上午9:46写道： > +1 for option A and note that we might allow [hotfix] as a replacement of > [TUBEMQ-XXX] for nit changes. > > Best, > tison. > > > kaynewu <kayn...@apache.org> 于2020年1月9日周四 上午9:42写道： > > > +0, for all. No clear info about it's for bug fix or improvement or new > > feature > > > > 俊平堵 <junping...@apache.org>于2020年1月8日 周三19:57写道： > > > > > +0 for all. No preference. :) > > > > > > Thanks, > > > > > > Junping > > > > > > Yiheng Wang <yihe...@gmail.com> 于2020年1月8日周三 下午7:49写道： > > > > > > > Hi Community > > > > > > > > I would like to call a vote on standardizing the code commit title > > > format. > > > > > > > > Currently, the patch title format is a little casual. This is not > good > > > for > > > > project maintenance and development. I propose several options for > code > > > > commit title format. > > > > > > > > Option A: > > > > [TUBEMQ-XXX][optional components] PR description > > > > > > > > Option B: > > > > TUBEMQ-XXX: (optional components) PR description > > > > > > > > Option C: > > > > TUBEMQ-XXX. (optional components) PR description > > > > > > > > TUBEMQ-XXX is the JIRA number. > > > > > > > > The vote is open until this Friday(Jan 10). > > > > > > > > [] +1 for option [A|B|C] or other: Vote for option [A|B|C] or another > > > > format > > > > [] +0 > > > > [] -1: I don't think this is a good idea because ... > > > > > > > > Thanks > > > > Yiheng > > > > > > > > > >
