We'd like to make clear how this project works and who holds what responsibilities. We want everyone involved to understand how decisions are made and where they can contribute. If you feel this page does not reflect the current state of project ownership and responsibilities, please contact the team on IRC or the Mailing List.


This project is developed and released by Red Hat with assistance from the Java developer community. The project lead is appointed by Red Hat, and has the power to accept and reject contributions to the project and set the roadmap. Red Hat employees assigned to work on apiman as well as community contributors, in this regard, all answer to the project lead.

Requirement Definition

The requirements and roadmap for apiman are driven by Red Hat and by the community. Typically, when a major release is being planned, the project lead will take input from both Red Hat and the community, and evaluate what can be done in the necessary time. This will define what features will be addressed in a given release. The project lead will then publish the roadmap in the project Issue Tracker (JIRA).

The best way for you to suggest requirements for a future release of apiman is to enter a feature request in JIRA. Lobbying for features using the voting functionality in JIRA, and sending email to the mailing list are all great ways to express interest as well. Of course, contributing is the single most expedient way to get a capability into a particular release.

Release Cycle

The apiman project releases major (new features and API changes), minor (new features but no breaking API changes) and micro releases (patches). Once a version of apiman is included in a Red Hat product release, apiman moves on to its next minor version.


The apiman project welcomes, thrives on and greatly values community contribution, and makes the bar to contributing as low as possible. If you have any questions on contributing, join us on IRC and speak to a member of the core apiman team!