...
Most of the development is done on "trunkmaster" and then backported (if required) to release branches.
Development can be done directly in a release branch only if the change is not meaningful on "trunkmaster".
Oozie committers can create release and development branches. A development branch is commonly used to work on a complex issue(s) that requires several JIRAs and eventually it will be merged back into "master".
Note: Prior to migrating from svn to git, the branch was named "trunk". As a consequence, many developers use "trunk" and "master" interchangeably, and many places, including JIRA, still refer to it as "trunk".
Making Changes to Oozie
First create an issue in Oozie Issue Tracking System describing the bug, improvement, new feature, task; and discuss if appropiate. It is important that the subject of the issue to be descriptive of the issue, and concise, as it will be used for the RELEASE LOG. All discussions should be done in the Issue Tracking System to make easier for developers to follow or come back in the future.
...