...
Work on the issue in your local development environment and when you think it is ready for review or integration upload your patch to the JIRA issue and generated by doing git diff --no-prefix to the JIRA issue. The naming convention of the patch should be OOZIE-<JIRA NUMBER>-1.patch. For eg: OOZIE-2555-1.patch.
After attaching the patch, click on 'Submit Patch' to change the status of the JIRA to 'Patch Available'.Marking Marking the JIRA as 'Patch Available' it will trigger Oozie test-patch Jenkins job that will do an automated analysis of the patch and reported to the JIRA.
...
Refine the patch based on the review discussions. For new patches with changes after review, you can increment the number at the end. For eg: OOZIE-2555-2.patch
Once your patch has been +1ed by Oozie committers the patch can be committed to the Version Control system. If you are a committer, you can commit it yourself. If you are not a committer, one of the committers that +1ed the patch will commit it on your behalf.
...