HyukjinKwon edited a comment on pull request #28403: URL: https://github.com/apache/spark/pull/28403#issuecomment-621244671
The benefit from this is to make it easier to track what caused a specific regression or behaviour change. Spark is being mature, and now it's getting more and more difficult to track the changes in the history. Also, note that this is rather a guidance than a strict requirement. I believe this doesn't block a PR. Well, this will likely be asked by a committer though. It actually makes the review/merge process faster. I myself happen to duplicate some contents time to time but I still see this is missing in other PR descriptions. I don't think the meaning vs k8s template is very different. We're just more conservative on the user-facing change - think about the Micheal's rubric of the amended semver as well. More importantly, what this PR proposes is just to guide contributors to know what to write there more explicitly and remove the ambiguity there. Changing the contents is orthogonal. ---------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
