+1 for this. Also we can put description of what changes might be required to make in the current running release. But that might be cumbersome. Just a thought.
Thanks, Mayuresh On Wed, Aug 19, 2015 at 2:29 PM, Jiangjie Qin <j...@linkedin.com.invalid> wrote: > I am thinking can we put some notes in commit message when commit a patch > which introduces introduce some API change or backward compatible change? > > It mainly serves two purposes: > 1. Easier for people to track the changes they need to make to run a new > version > 2. Easier for us to write the release note. > > If we assume all the API change or backward incompatible change are going > through a KIP then we can put the KIP number in the commit message. > Otherwise, maybe we can put [INTERFACE CHANGE] in the commit message? > > Thoughts? > > Jiangjie (Becket) Qin > -- -Regards, Mayuresh R. Gharat (862) 250-7125
