atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Madhan Neethiraj <mad...@apache.org>
Subject Re: Committer process
Date Mon, 14 Aug 2017 14:40:01 GMT
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 <davidrad@apache.org>
Date: Monday, August 14, 2017 at 4:58 AM
To: Madhan Neethiraj <madhan@apache.org>
Cc: "dev@atlas.apache.org" <dev@atlas.apache.org>
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


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message