Hi Madhan, That makes sense. I will correct the wiki, thanks, David -- David Radley - Apache Atlas committer
From: Madhan Neethiraj <[email protected]> To: David Radley <[email protected]> Cc: "[email protected]" <[email protected]> Date: 14/08/2017 15:40 Subject: Re: Committer process Sent by: Madhan Neethiraj <[email protected]> David, > It says that a commits should update the release log, but I notice that this > has not occurred recently. Is this still part of the process? We stopped updating release log, as it caused merge issues while cherry-picking commits to other branches (like 0.8 branch). And with appropriate use of git while dealing with patches (like preserve author information, commit message), maintaining release log file is not necessary. Thanks, Madhan From: David Radley <[email protected]> Date: Monday, August 14, 2017 at 4:58 AM To: Madhan Neethiraj <[email protected]> Cc: "[email protected]" <[email protected]> Subject: Committer process Hi Madhan, I see that on the Apache Atlas wiki there are steps to commit a patch here: https://cwiki.apache.org/confluence/display/ATLAS/Developer+Resources#DeveloperResources-CommitSteps It says that a commits should update the release log, but I notice that this has not occurred recently. Is this still part of the process? Based on your previous suggestion: https://cwiki.apache.org/confluence/display/ATLAS/Using+Git+with+Atlas I assume the committer needs to issue a git commit --patch - so that the original message and authorship are maintained. In this case, we do not include the release log update. I am looking to update the wiki with the current practices. all the best, David Radley - Apache Atlas committer
