+1 on first release. Maybe after 0.2.0-incubating we should give more time for runner developers to adjust to new APIs, or consider this work as ongoing during 0.3.0 and 0.4.0 (incubating).
On Fri, Apr 8, 2016, 12:20 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 > > >
