Page tree
Skip to end of metadata
Go to start of metadata

Using Git with Atlas

Using Git with Atlas

Committer guidelines

These are the general guidelines that the committers should try to follow always, but can use their discretion, and rely on good faith and trust to do the right thing:

  1. All commits need a JIRA

  2. All jiras need a +1 from a committer (preferably) or subject matter expert (for things like UI - which has fewer experts in the committer list) before committing. Of course, no commit can happen if another contributor/committer has requested time for review. +1 can't be from the same person who has submitted the patch

  3. For bugs and improvements that touch core of Atlas - the type system, metadata repository, notification interface, please wait at least 18 hours from when the patch was submitted(excluding holidays), to give time for contributors/committers in other timezones to review.

  4. Features or large patches that touch many areas should have a proposal about the approach in JIRA and should be reviewed by more than one committer.

  5. Conversely, we can be a little lax with commits that touch peripheral areas that are unlikely to destabilise core - including UI, hooks, documentation and commit more freely.

  6. Exceptions are fixes for bugs that are breaking builds/tests - these can be committed without waiting, irrespective of which area they fall in. But they need +1 from some contributor, not same as patch owner.

  7. Committers should try to closely monitor activity and comments on JIRAs and proactively engage if they have issues with the approach etc.

  8. If any commit is found to break things badly, the right way to fix is to open a new JIRA stating what the issue is, caused by which JIRA and wait for the committer or contributor to respond back. A revert can be proposed depending on how bad the regression is, and the committer / contributor must be open to this in the best interest of the project.

Commit Steps

  1. Apply the patch from the JIRA on the latest codebase with no other local changes
    1. If the patch has been produced in the mail format: 
      1. git am --signoff < ATLAS_xxxx.patch
    2. If the patch has not been produced in the mail format,  you need to supply the author and message on the commit:
      1. Run git apply ATLAS_xxxx.patch
      2. Run git commit --author="<author>" --m="<ATLAS-xxxx message text>" --signoff
  2. Run 'mvn clean install'
  3. If you want to check the commits that will be pushed run 'git cherry -v'
  4. 'git push'. If git push fails because the codebase is out of sync with remote, the differences need to be resolved.
    1. If the conflicts are trivial run 'git pull --rebase'. Please don't run just 'git pull' as it adds merge commits. Resolve conflicts if any and verify the build and commit again.
    2. If the merge is not trivial, send back to the author to resolve conflicts and rerun testing and resubmit with the conflicts resolved.  
  5. Make sure the JIRA has the latest patch and resolve the JIRA with the right fixVersion
  6. Add the commit url to the Jira, run git log and copy and paste the commit information into the Jira. You can add this text at the same time as you resolve the Jira (step 6). 
  7. Rectifying mistakes:
    1. Should be done in new JIRA / commits.
    2. If you commit with the wrong commit message you can alter the commit message if it is the last commit.

Releasing atlas

Note: Replace 0.8.1 with the version that you are releasing

Prepare for release

  1. Send an email to dev@ with the scope of the release and the release timelines atleast a week before the planned release start date
  2. Create a new branch for the release, if necessary.
  3. Update Atlas version in all pom files (to the release version)
  4. Verify the sources in the release branch with the following steps:
    1. builds cleanly with empty local mvn repo(~/.m2/repostory): mvn clean install && 
    2. packaging & distro creation completes successfully: mvn clean package -Pdist,embedded-hbase-solr
    3. Atlas installed with the created binary package is functional

Prepare keys

  1. Generate key:

  2. svn co atlas-release

  3. Add your key to atlas/KEYS: 
    (gpg --list-sigs <your name> \
                 && gpg --armor --export <your name>) >> atlas-release/KEYS
  4. Commit atlas-release

Prepare source package

  1. Go to atlas code with the release branch
  2. git tag -a release-0.8.1-rc0 -m "Atlas 0.8.1-rc0 release"

  3. git push origin release-0.8.1-rc0
  4. mvn clean package -Pdist -DskipTests

Upload source package

  1. svn co atlas-dev

  2. mkdir atlas-dev/0.8.1-rc0
  3. cp atlas/distro/target/apache-atlas-0.8.1-sources.tar.gz atlas-dev/0.8.1-rc0/
  4. cd atlas-dev/0.8.1-rc0/
  5. gpg --armor --output apache-atlas-0.8.1-sources.tar.gz.asc --detach-sig apache-atlas-0.8.1-sources.tar.gz
  6. gpg --print-md MD5 apache-atlas-0.8.1-sources.tar.gz >apache-atlas-0.8.1-sources.tar.gz.md5
  7. gpg --print-md SHA512 apache-atlas-0.8.1-sources.tar.gz > apache-atlas-0.8.1-sources.tar.gz.sha512
  8. Commit atlas-dev


Vote mail template

Subject: [VOTE] Release Apache Atlas version 0.8.1
Atlas team,

Apache Atlas 0.8.1 release candidate #0 is now available for a vote within dev community. Links to the release artifacts are given below. Please review and vote.

The vote will be open for at least 72 hours or until necessary votes are reached.
  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove (and reason why)

List of issues addressed in this release:
Git tag for the release:
Sources for the release:
Source release verification:
  PGP Signature:
  MD5 Hash:
Keys to verify the signature of the release artifacts are available at:

If the above vote passes, send a result vote and the release is now successful.

Post release steps

  1. Publish release artifacts in apache mvn repository using instructions
  2. Publish the release packages:
    1. svn co atlas-release && cd atlas-release
    2. Delete the old releases
    3. Copy the release artifacts from to new release directory 0.8.1
    4. Commit atlas-release
  3. Update atlas website documentation:
    1. Clone Atlas Website sources: git clone atlas-website

    2. Create following directories for release contents: mkdir -p atlas-website/0.8.1/api/v2
    3. Generate documentation from twiki sources with the following command from atlas/docs directory: mvn clean site
    4. Copy documentation to Atlas website repository with: cp -r atlas/docs/target/site/* atlas-website/0.8.1/
    5. Generate Java/REST API docs from Atlas sources with the following command from atlas directory: mvn clean -DskipTests -DskipEnunciate=false package
    6. Copy Java/REST API doc to Atlas website repository with: cp -r atlas/webapp/target/api/v2/apidocs atlas-website/0.8.1/api/v2
    7. Update site's root documentation with the latest version contents: cp -r atlas-website/0.8.1/ atlas-website/
    8. Verify the html files and commit
    9. Verify the site
  4. Send release announcement

    Subject: [ANNOUNCE] Apache Atlas 0.8.1 released
    Hi All,
    The Apache Atlas team is happy to announce the release of Apache Atlas - version 0.8.1.
    Atlas is a scalable and extensible set of core foundational governance
    services – enabling enterprises to effectively and efficiently meet their
    compliance requirements within Hadoop and allows integration with the whole
    enterprise data ecosystem.
    The release artifacts are available at:
    The binary artifacts are available from Maven central and its mirrors.
    To use these artifacts, please use the following documentation:
    More details on Apache Atlas can be found at:
    We thank everyone who made this release possible.
    The Apache Atlas team

Publishing artifacts in apache mvn repository

  1. Generate PGP keys:

  2. Set-up apache id credentials for maven:

  3. Test your settings: 'mvn clean install -Papache-release -DskipTests -DskipDocs' (this will build artifacts, sources and sign)

  4. Deploy the artifacts: 'mvn clean deploy -Papache-release -DskipTests -DskipDocs'
    1. For SNAPSHOT version, verify the artifacts at
    2. For release version, the artifacts are deployed in staging repository.
      1. Login at, go to stagingRepositories
      2. Select the atlas repository and close. This will trigger validations on checksum and signature. If any checks fail, fix the issue, deploy the artifacts and close the repository again. If all checks succeed, release the repository
      3. Verify the artifacts at




  • No labels