looks good to me.
Could you please update the doc?

docs/zh-CN/developer-guide/commit-format-specification.md
docs/en/developer-guide/commit-format-specification.md







--

此致!Best Regards
陈明雨 Mingyu Chen

Email:
chenmin...@apache.org





在 2021-11-25 10:54:41,"Shuo Wang" <wangshuo...@gmail.com> 写道:
> I think the three below items are ambiguous and misleading:
>
>*feat-new: New function
>New feature or just a new expression function?  And is the abbreviation
>`feat` sort for the word feature?
>
>The following ones are all `optimization`, it's sometimes hard to tell the
>difference.
>*feat-opt: Optimization and improvement of original functions
>*optimize:Performance optimization
>
>I suggest:
>`feat-new` ->  `feature` : to add a new feature.
>`feat-opt` -> `Improvement`: improvement of original functions.
>`optimize` -> `Performance` : Performance related optimization.
>
>
>陈明雨 <morning...@163.com> 于2021年11月24日周三 下午5:43写道:
>
>> Hi all:
>>
>>
>> We have added a document[1][2] to guide the format of the commit log to
>> help us write a more standardized commit message.
>> Through standardized commit message, we can automatically generate a
>> change log, or know more clearly about function changes or bug fixes.
>>
>>
>> [1]
>> http://doris.incubator.apache.org/master/zh-CN/developer-guide/commit-format-specification.html#commit-%E6%A0%BC%E5%BC%8F%E8%A7%84%E8%8C%83
>> [2]
>> http://doris.incubator.apache.org/master/en/developer-guide/commit-format-specification.html#commit-format-specification
>>
>> --
>>
>> 此致!Best Regards
>> 陈明雨 Mingyu Chen
>>
>> Email:
>> chenmin...@apache.org

Reply via email to