Note this is a blog version of Release Vote Insights.

Ten years ago, an open-source project joining Apache might have taken weeks to make its first release. Today, most do it in less time and with far fewer errors. Behind that change lies a quiet transformation in how communities learn, collaborate, and share responsibility.

What Is the ASF Incubator?

The ASF Incubator is the entry path for new projects to The Apache Software Foundation (ASF). It helps communities learn how to manage code, releases, and decision-making in an open and transparent way. Every release in the Incubator is more than just code; it marks a community milestone that shows how contributors work together following The Apache Way.

Over the past decade, the Incubator has guided thousands of releases from more than 160 projects. Analysis of 1,600 release votes from 33,000 emails and 1,000 participants shows clear progress: fewer rejections, faster reviews, and more confident communities.

From Rules to Collaboration

In the early years, Incubator release reviews were daunting. Discussions focused on what was wrong, such as missing files, license issues, or packaging errors. Mentors and reviewers acted as gatekeepers, and the process often felt bureaucratic. In 2025, things are different. Reviews are now shorter, friendlier, and move more quickly. Instead of saying, "This violates ASF policy," reviewers now say, "Let's fix this before the next release candidate." This move from strict enforcement to working together shows how the ASF’s mentoring culture has grown. Now, the process feels more like a shared learning experience than just a compliance check.

The Numbers Tell a Story

This progress isn’t because the rules got easier, but because people understand them better. Communities now know what success looks like and how to reach it together.

How the Culture Evolved

2014–2017: Policy-Driven Beginnings
The Incubator grew quickly. Reviews focused on strict compliance and long, detailed discussions. This phase established much-needed governance consistency.

2018–2020: Standardization and Clarity
Better documentation, templates, and policies, such as the Distribution Policy and WIP Disclaimer, simplified expectations. Reusable checklists helped projects make compliant releases without confusion.

2021–2025: Collaboration and Mentorship 
Reviews became more cooperative. Mentors guided projects through pre-vote checks, automation improved, and most procedural errors disappeared. Votes focused on learning, not enforcement.

Why Release Cadence Matters

Healthy projects release regularly. Data show that podlings with releases every one to three months usually graduate from incubation within one to two years. Projects that go long periods without a release are more likely to lose momentum or retire. Frequent releases help communities stay engaged, reduce technical debt, and welcome new contributors. Over time, release rhythm became a reliable sign of community health, even more so than code size or number of features.

Lessons for All Open-Source Projects

The ASF Incubator’s experience reflects a challenge faced by every open-source community: balancing freedom with responsibility.

  1. Mentorship works.
    New contributors learn faster when guidance comes from peers rather than enforcement.

  2. Transparency builds trust.
    Public reviews and open discussions create accountability and help newcomers understand decisions.

  3. Documentation is culture.
    Checklists, templates, and policies encode experience so others can build on it.

  4. Consistency enables diversity.
    Simplifying the process lowers barriers for contributors from different companies and backgrounds.

These lessons are not unique to the ASF. Any open-source project can benefit from clear expectations, open communication, and a culture that supports mentoring.

The Bigger Picture

The past decade of Apache Incubator releases shows how open collaboration evolves. Rules and policies are still important, but mentorship, openness, and good communication help put them into practice. Every successful release is more than just a technical win. It shows that a community has learned to work together, review each other's work, and share responsibility. This spirit defines The Apache Way and helps Incubator projects grow into full ASF communities.


About the Author

Justin Mclean is currently the Vice President of the Apache Incubator, an ASF Director and a long-time ASF Member. Since 2018, he has led initiatives to improve mentorship, release governance, and community health across the Apache Software Foundation.