Versions Compared

Old Version 16

changes.mady.by.user Yusaku Sako

Saved on

compared with

New Version 17

changes.mady.by.user Yusaku Sako

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Please make sure you use Use the Apache JIRA for most of the design updates posting design docs and having design discussions (adding detailed descriptions, comments, etc)

  • Create a patch and upload to the Apache JIRA.  The patch should be named AMBARI-XXXX.patch for trunk patches and AMBARI-XXXX_YYYY.patch for branch patches, where XXXX is the JIRA ID and YYYY is the name of the branch (for example, AMBARI-1234_branch-1.7.0.patch). As soon as you think  If the patch is for a release branch, both trunk patch and branch patch must be uploaded.

  • Mark ready for review please mark the patch as Patch Available by clicking on the “Submit Patch” button

  • Wait for the "Hadoop QA" process to post feedback on the patch.  This typically takes 30 mins to an hour and reports back on unit test results, license header compliance, presence of new tests, etc, on the JIRA itself.

  • If "Hadoop QA" checks do not pass but you think the feedback is invalid, state the reasons why you believe it is invalid. 

  • Once "Hadoop QA" checks pass (or if there's a valid reason for ignoring the checks), create a ReviewBoard for the patch and request two Ambari committers (more would not hurt) to review the patch via the code review process below

    • Please note that if the patch is not involved - one committer should suffice

  • On review completion and any further updates, the reviewers give +1 for the patch

    • A +1 from an Ambari committer is mandatory before any patch can be committed (+1 from a non committer, though useful, does not count toward this requirement)

    • There should be 2 +1's from Ambari committers for changes that are involved or if the patch is going into a release branch

  • NOTE: Be sure to include tests in the patch.  If tests are not applicable, provide a good explanation for not having a test case.

  • After the reviewer(s) has approved the patch, the assignee of the JIRA is responsible for getting it committed if that person is a committer.  If not, one of the reviewers needs to commit.

    • If the patch is intended to go into a release branch, make sure that the patch is committed to both the release branch and trunk.

  • Refer to https://cwiki.apache.org/confluence/display/AMBARI/How+to+Commit on how to commit

  • After committing to git, resolve the Apache JIRA as Fixed.

...