You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2016/04/08 17:47:49 UTC
[PROPOSAL] Releases schedule
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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] Releases schedule
Posted by Davor Bonaci <da...@google.com.INVALID>.
Sounds like a plan!
On Fri, Apr 8, 2016 at 9:34 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Yes, agreed.
>
> The runners don't have to all update to Runner API on 0.2.0-incubating.
> They can do it on 0.3.0 or 0.4.0.
>
> Regards
> JB
>
>
> On 04/08/2016 06:30 PM, Amit Sela wrote:
>
>> +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 <lc...@google.com.invalid> 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é <jb...@nanthrax.net>
>>> 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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [PROPOSAL] Releases schedule
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Yes, agreed.
The runners don't have to all update to Runner API on 0.2.0-incubating.
They can do it on 0.3.0 or 0.4.0.
Regards
JB
On 04/08/2016 06:30 PM, Amit Sela wrote:
> +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 <lc...@google.com.invalid> 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é <jb...@nanthrax.net>
>> 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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] Releases schedule
Posted by Amit Sela <am...@gmail.com>.
+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 <lc...@google.com.invalid> 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é <jb...@nanthrax.net>
> 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é
> > jbonofre@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
Re: [PROPOSAL] Releases schedule
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
I like your updated proposal Davor, it's perfectly fine and give some ideas.
Thanks !
Regards
JB
On 04/08/2016 06:28 PM, Davor Bonaci wrote:
> 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 <lc...@google.com.invalid>
> 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é <jb...@nanthrax.net>
>> 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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [PROPOSAL] Releases schedule
Posted by Davor Bonaci <da...@google.com.INVALID>.
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 <lc...@google.com.invalid>
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é <jb...@nanthrax.net>
> 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é
> > jbonofre@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
Re: [PROPOSAL] Releases schedule
Posted by Lukasz Cwik <lc...@google.com.INVALID>.
+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é <jb...@nanthrax.net>
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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>