While not strictly required, some IPMC members like to see a project evaluate itself against the Apache Project Maturity Model.
https://community.apache.org/apache-way/apache-project-maturity-model.html I’ve found that if a podling addresses all points in the maturity model before the vote, then it makes for an extremely smooth and uncontroversial vote. In addition to the obvious matter of publishing a few successful approved Apache releases, see below for a few points from the maturity model that could use attention. These are largely matters of deciding on policy and documenting it. If needed, the mentors can help point out how other Apache projects handle these concerns. QU30 The project provides a well-documented channel to report security issues, along with a documented way of responding to them. QU40 The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features. --Chris Nauroth On 10/10/16, 9:41 AM, "JG Homan" <jgho...@gmail.com> wrote: +1 On Mon, Oct 10, 2016 at 8:37 AM -0700, "Chris Riccomini" <criccom...@apache.org> wrote: This is the official check list: http://incubator.apache.org/projects/airflow.html Most if it is in pretty good shape. There's some copyright stuff that we already did. We just need to date it. Other than that, a release or two and we should be good to go. I'd say after 1.8, we can probably call for a vote. On Sat, Oct 8, 2016 at 11:00 AM, siddharth anand wrote: > Folks! > What are our remaining requirements to graduate from the incubator? My > understanding is that we need to start doing Apache releases. If that is > the case, can we prioritize this and have someone lead it? > > I know Max/Bolke were working on a 1.7.3 apache release, so we could follow > up with a 1.8 apache release. I suggest we do the 1.7.3 release. > > Max/Bolke, > Can one of you list what remains to be done for that? > > -s