streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sblackmon <>
Subject Re: [DISCUSS] Apache Maturity Model Assessment
Date Mon, 13 Feb 2017 17:17:03 GMT

Following up on this thread - completing the Apache Maturity Model Assessment and proposing

Thank you Suneel for contributing to the AMMA in December and January.

Everyone else - please take a look and contribute comments or changes in the document, on
this thread, and/or add tickets in JIRA.

This is the time to call out any areas where you think we should make adjustments prior to
a graduation vote.

The plan is to perform 0.5-incubating release by the end of February, so now is a great time
to fit in improvement to POMs and documentation.

On January 26, 2017 at 12:06:05 PM, sblackmon ( wrote:

Happy 2017 Streams committers and well-wishers.

For those unfamiliar, the Apache Maturity Model Assessment is a essentially a checklist
assessment of project health based on many of the principles of the Apache Software Foundation.

I’ve started an AMMA for Streams here:

All in all, Streams already stacks up pretty well against the ~35 items on the AMMA. There
are some gaps - and opportunities to improve of course.

I think we have reached the point where the project can make a strong case to graduate to
TLP, following a concerted effort to address the gaps that remain. 

So my ask to everyone is:
 - review and bookmark the Streams AMMA doc in confluence.
 - confirm that you have edit or at least comment privileges.  let me know if you don’t.
 - prepare and share notes on any areas of concern to you personally
 - identify and share specific ideas that we could act on to improve our score on any items,
especially those where we are falling short of a definitive YES.

Personally I want to see the project achieve TLP status prior to ApacheCon NA 2017, after
one more major release.

I will respond personally to any feedback on this and future related threads, and reach out
to the list regarding our progress about once a week from here on out to push us forward.

Thanks in advance for your support.


On November 25, 2016 at 12:21:50 PM, Steve Blackmon ( wrote:
On Nov 25, 2016 11:58 AM, "Suneel Marthi" <> wrote:
> Thanks for starting this @sblackmon.
> Could we make 2 releases (both releases managed by folks != "sblackmon").
> Since the recent 0.4 release, there have been minor bug fixes and
> performance improvements, we could cut a release in the next one week -
> call it 0.4.1.

I think all of the changes that have merged are suitable for a minor release. There were changes
made to the facebook module translations, but those had fallen out of sync with the provider
to the point that documents coming out of the 0.4 release providers were missing a ton of
useful informaton.  So i think we can make an exception to the a general preference to not
change data schemas in a non-backwards compatible way in a minor release.
> We do have a planned major release 0.5 for end of December.
> The idea is to have more frequent releases to demonstrate maturity in the
> release process and each release managed by a different Release Meister.
> Thoughts?
> On Fri, Nov 25, 2016 at 12:35 PM, sblackmon <> wrote:
> > Hello,
> >
> > Last week at ApacheCon EU I attended a walkthrough about the Apache
> > Maturity Model [1]
> >
> > As we close in on graduation, it should be helpful to evaluate the project
> > against the Maturity Model and work to close any gaps we see.
> >
> > To help start this effort, I’ve created a page on the wiki with a draft
> > assessment, and some notes for discussion in italics.
> >
> >
> > Assessment+for+Streams
> >
> > Please take a look - if you have thoughts to contribute please do so in
> > this thread or edit the wiki page directly (LMK if you need permissions to
> > view or edit)
> >
> > Cheers,
> > Steve
> >
> > [1]
> > maturity-model.html

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message