I think it is very hard to commit to specific dates right now.
Certainly, the bar for the first release is set -- code cleanup and
renaming completed. There's plenty of uncertainty here -- unclear about the
specific date, but the ballpark sounds about right.
The new Runner / Fn API is the biggest piece of work -- unclear when this
may land, but the ballpark would probably be in early summer. In terms of
new SDKs/DSLs, no plans there. There'll be new IOs, Kafka at a minimum.
I think we should commit to the following:
- Two releases during Q2:
- The first release in early-to-mid May, with renaming completed.
- The second release by the end June -- payload unclear.
- A release every 1-2 months after that.
- Incubator graduation in early Q4.
- The first stable release in Q4, with a promise of future
backward-compatibility from that point onward.
I think this is very much aligned with what JB proposed, but with slightly
different guarantees.
On Fri, Apr 8, 2016 at 9:20 AM, Lukasz Cwik <[email protected]>
wrote:
> +1 for 0.1.0-incubating release
> unsure that progress and timelines will match up for the others
>
> On Fri, Apr 8, 2016 at 8:47 AM, Jean-Baptiste Onofré <[email protected]>
> wrote:
>
> > Hi beamers !
> >
> > In order to give some visibility, I would like to propose the following
> > releases schedule:
> >
> > 0.1.0-incubating (on vote May 6th): first release with code cleanup and
> > renaming (with only org.apache.beam packages). The purpose of this
> release
> > is to test a first release, check the legal, and ask review from the
> > Incubator PMC.
> >
> > 0.2.0-incubating (on vote July 1st): adding the new Runner and IO APIs.
> > Including new IOs and SDKs/DSLs.
> >
> > 0.3.0-incubating (on vote July 29th): stabilization and bug fixing, new
> > IOs and SDKs/DSLs. Breaking changes can be acceptable there.
> >
> > 0.4.0-incubating (on vote August 26th): stabilization and bug fixing, new
> > IOs and SDKs/DSLs.
> >
> > We can target graduation for September.
> >
> > WDYT ?
> >
> > Regards
> > JB
> > --
> > Jean-Baptiste Onofré
> > [email protected]
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
