Hi Ismael, Thanks for raising this topic Ismael, I like the idea, I think this would bring some more meaningful first-liners on the commits. I guess we could use the scope (what comes within parentheses) to indicate the module the commit refers to (if it's single module) However, I doubt if this can be used for the release notes as we rely on JIra for this purpose.
Some questions that come to mind: - should `feat` only be used for KIPs? - should we use conventional commits to help cut the release (for example, no `feat` commit in a patch version? - should we use the scope to indicate the module the commit touches? - should this be a convention for comitters to rewrite the message before squash-merging? Or will we enforce PR authors to follow this convention? Best, On Thu, Jun 8, 2023 at 8:13 AM Ismael Juma <m...@ismaeljuma.com> wrote: > Hi, > > A number of open source projects have adopted the conventional commits > specification. What do people think about using this for Apache Kafka? > > https://www.conventionalcommits.org/en/v1.0.0/ > > Thanks, > Ismael > -- [image: Aiven] <https://www.aiven.io> *Josep Prat* Open Source Engineering Director, *Aiven* josep.p...@aiven.io | +491715557497 aiven.io <https://www.aiven.io> | <https://www.facebook.com/aivencloud> <https://www.linkedin.com/company/aiven/> <https://twitter.com/aiven_io> *Aiven Deutschland GmbH* Alexanderufer 3-7, 10117 Berlin Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen Amtsgericht Charlottenburg, HRB 209739 B
