[DISCUSS] Monthly release cadence

[James Sirota <js...@hortonworks.com>]

I propose that we move to a monthly release cadence for Metron with the first release being at the end of January.  I would like to cut a beta release this month so we as a community can understand what we have to go through to cut a formal Apache release.  We are also beefing up Metron’s automated installs and regression test suite (which we will be contributing back shortly) and more frequent releases early would help us test our CI infrastructure and get quality and test coverage up

Thanks,
James

Re: [DISCUSS] Monthly release cadence

[Owen O'Malley <om...@apache.org>]

Releasing monthly sounds like a great place to start. It will help build
momentum for the project and get the ball rolling. The first release out of
an incubator project always takes a little longer because of the extra
checking for licenses and headers.

.. Owen

On Wed, Jan 13, 2016 at 5:59 AM, larry mccay <lm...@apache.org> wrote:

> It would be great to start out with such a cadence.
>
> I think that we need to clearly articulate how one goes about testing for
> the apache release.
> Is this already captured somewhere? I don't see it on the site anywhere.
>
> On Wed, Jan 13, 2016 at 8:50 AM, James Sirota <js...@hortonworks.com>
> wrote:
>
> > I propose that we move to a monthly release cadence for Metron with the
> > first release being at the end of January.  I would like to cut a beta
> > release this month so we as a community can understand what we have to go
> > through to cut a formal Apache release.  We are also beefing up Metron’s
> > automated installs and regression test suite (which we will be
> contributing
> > back shortly) and more frequent releases early would help us test our CI
> > infrastructure and get quality and test coverage up
> >
> > Thanks,
> > James
> >
>

Re: [DISCUSS] Monthly release cadence

[larry mccay <lm...@apache.org>]

It would be great to start out with such a cadence.

I think that we need to clearly articulate how one goes about testing for
the apache release.
Is this already captured somewhere? I don't see it on the site anywhere.

On Wed, Jan 13, 2016 at 8:50 AM, James Sirota <js...@hortonworks.com>
wrote:

> I propose that we move to a monthly release cadence for Metron with the
> first release being at the end of January.  I would like to cut a beta
> release this month so we as a community can understand what we have to go
> through to cut a formal Apache release.  We are also beefing up Metron’s
> automated installs and regression test suite (which we will be contributing
> back shortly) and more frequent releases early would help us test our CI
> infrastructure and get quality and test coverage up
>
> Thanks,
> James
>