The Apache Software Foundation
The Apache Software Foundation Incubator

Oozie Incubation Status

This page tracks the project status, incubator-wise. For more general project status, look on the project website.

The Oozie project graduated on 2012-08-28


Oozie is a server-based workflow scheduling and coordination system to manage data processing jobs for Apache Hadoop. More specifically, this includes:

  • XML-based declarative framework to specify a job or a complex workflow of dependent jobs.
  • Support different types of job such as Hadoop Map-Reduce, Pipe, Streaming, Pig, Hive and custom java applications.
  • Workflow scheduling based on frequency and/or data availability.
  • Monitoring capability, automatic retry and failure handing of jobs.
  • Extensible and pluggable architecture to allow arbitrary grid programming paradigms.
  • Authentication, authorization, and capacity-aware load throttling to allow multi-tenant software as a service.


  • 2012-08-28 Apache Oozie graduates from Incubator
  • 2012-06-06 Oozie Release - version 3.2.0-incubating
  • 2012-05-14 New Committer: Harsh Chouraria
  • 2012-05-14 New Committer: Virag Kothari
  • 2012-03-01 Oozie Release - version 3.1.3-incubating
  • 2011-07-11 Project enters incubation

Project info

item type reference
Website www
. wiki
Mailing list dev
. users
. commits
Bug tracking .
Source code SVN
Mentors gates Alan Gates
. cdouglas Chris Douglas
. ddas Devaraj Das
Committers . Mohammad K Islam
. Angelo Huang
. Mayank Bansal
. Andreas Neumann
. Alejandro Abdelnur
. Chao Wang
. Virag Kothari
. Harsh Chouraria

Incubation status reports

  • none yet

Incubation work items

Project Setup

This is the first phase on incubation, needed to start the project at Apache.

Item assignment is shown by the Apache id. Completed tasks are shown by the completion date (YYYY-MM-dd).

Identify the project to be incubated

date item
2011-07-07 Make sure that the requested project name does not already exist and check to be sure that the name is not already trademarked for an existing software product.
Not Applicable If request from an existing Apache project to adopt an external package, then ask the Apache project for the SVN module and mail address names.
Not Applicable If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.
Not Applicable If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted.


date item
2011-08-19 Ask infrastructure to create source repository modules and grant the committers karma.
2011-07-12 Ask infrastructure to set up and archive mailing lists.
2011-07-12 Ask infrastructure to set up issue tracker (JIRA, Bugzilla).
2011-08-19 Ask infrastructure to set up wiki (Confluence, Moin).
2011-10-05 Migrate the project to our infrastructure.

Mentor-related responsibility/oversight

date item
2011-07-07 Identify all the Mentors for the incubation, by asking all that can be Mentors.
2011-10-05 Subscribe all Mentors on the pmc and general lists.
2011-10-05 Give all Mentors access to the incubator SVN repository. (to be done by the Incubator PMC chair or an Incubator PMC Member wih karma for the authorizations file)
2011-09-08 Tell Mentors to track progress in the file 'incubator/projects/{}.html'
date item
2011-08-27 Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.
2012-02-22 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.

Verify distribution rights

date item
2012-02-22 Check and make sure that for all code included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute.
2012-06-06 Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.

Establish a list of active committers

date item
2011-09-08 Check that all active committers have submitted a contributors agreement.
2011-09-08 Add all active committers in the STATUS file.
2011-07-12 Ask root for the creation of committers' accounts on

Project specific

Add project specific tasks here.


These action items have to be checked for during the whole incubation process.

These items are not to be signed as done during incubation, as they may change during incubation. They are to be looked into and described in the status reports and completed in the request for incubation signoff.

Collaborative Development

  • Have all of the active long-term volunteers been identified and acknowledged as committers on the project? - YES
  • Are there three or more independent committers? (The legal definition of independent is long and boring, but basically it means that there is no binding relationship between the individuals, such as a shared employer, that is capable of overriding their free will as individuals, directly or indirectly.) - YES
  • Are project decisions being made in public by the committers? - YES
  • Are the decision-making guidelines published and agreed to by all of the committers? - YES

Licensing awareness

  • Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers? - YES

Project Specific

Add project specific tasks here.


Things to check for before voting the project out.

Organizational acceptance of responsibility for the project

  • If graduating to an existing PMC, has the PMC voted to accept it?
  • If graduating to a new PMC, has the board voted to accept it? - YES

Incubator sign-off

  • Has the Incubator decided that the project has accomplished all of the above tasks? - YES