Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Good point Kenn. I will do the list of what we need to do a release with gradle.

Regards
JB

On 01/29/2018 07:31 PM, Kenneth Knowles wrote:
> I'd also love if we can use the notes to keep track of what needs to be done 
> for
> Gradle.
> 
> On Mon, Jan 29, 2018 at 10:29 AM, Jean-Baptiste Onofré  > wrote:
> 
> Sure, I will ;)
> 
> First steps:
> 
> 0. Validate the build: mvn clean install -Prelease,sign
> 0bis. dryRun on the release: mvn release:prepare -DdryRun
> 
> After that, I start the formal process. I keep you posted.
> 
> Regards
> JB
> 
> On 01/29/2018 07:23 PM, Alan Myrvold wrote:
> > Great. I'm interested in any pain points in the process, and steps we 
> can
> > automate. Can you keep a rough log of issues you run into?
> >
> > On Mon, Jan 29, 2018 at 10:16 AM, Jean-Baptiste Onofré 
> 
> > >> wrote:
> >
> >     We are now ready for the release. I'm starting the process.
> >
> >     Thanks again for your help and support !
> >
> >     Regards
> >     JB
> >
> >     On 01/29/2018 02:22 PM, Jean-Baptiste Onofré wrote:
> >     > Hi,
> >     >
> >     > new update (and I hope the last one ;)):
> >     >
> >     > - BEAM-3551 has been reviewed and merged. This Jira is fixed for 
> 2.3.0.
> >     > - I just updated the PR for BEAM-793 (testing with write with 
> backoff
> >     feature in
> >     > JdbcIO). I hope Eugene will give his green light to merge ;)
> >     > - we have a new Jira (BEAM-3559) that has been created this 
> morning and
> >     targeted
> >     > to 2.3.0. I asked for detail in the Jira and no update yet. Can I
> have an
> >     update
> >     > on this one ? Else I will bump it to 2.4.0.
> >     >
> >     > I will cut the 2.3.0 release tonight my time then.
> >     >
> >     > Thanks,
> >     > Regards
> >     > JB
> >     >
> >     > On 01/29/2018 07:14 AM, Jean-Baptiste Onofré wrote:
> >     >> Hi,
> >     >>
> >     >> As BEAM-793 and BEAM-3551 are not release blocker, if I don't 
> have
> update
> >     in the
> >     >> PRs in the coming couple of hours, I will bump these Jiras to 
> 2.4.0
> and start
> >     >> the release process.
> >     >>
> >     >> Thanks !
> >     >> Regards
> >     >> JB
> >     >>
> >     >> On 01/28/2018 08:29 PM, Jean-Baptiste Onofré wrote:
> >     >>> Hi guys,
> >     >>>
> >     >>> a new update about 2.3.0 release preparation. Only 2 Jira are
> pending (not
> >     >>> blocker for the release but good to have):
> >     >>>
> >     >>> - BEAM-793: I updated the PR (#4500), waiting Eugene's feedback.
> >     >>> - BEAM-3551: I created a PR (#4516), waiting Luke's feedback.
> >     >>>
> >     >>> Thanks to the timezone, I hope to have feedbacks soon.
> >     >>>
> >     >>> Anyway, these Jiras are not release blocker, so I will start the
> release
> >     process
> >     >>> tomorrow morning my time.
> >     >>>
> >     >>> By the way, I created 2.4.0 version in Jira.
> >     >>>
> >     >>> Thanks all for your help and support !
> >     >>>
> >     >>> Regards
> >     >>> JB
> >     >>>
> >     >>> On 27/01/2018 13:00, Jean-Baptiste Onofré wrote:
> >      Hi guys,
> >     
> >      we still have 7 Jira targeted to 2.3.0.
> >     
> >      For most of them, Ismaël and I are doing the PRs/fixes and we 
> have
> >     review in
> >      progress.
> >     
> >      I'm a little bit concerned by BEAM-3392: it's flagged as 
> blocker
> but it's
> >      related to a specific branch. Can you please provide an update 
> asap ?
> >     
> >      However, I didn't have any update for BEAM-3087 (related to 
> the Flink
> >     runner).
> >      Without update soon, I will bump to 2.4.0.
> >     
> >      I would need a review on PR for BEAM-793 (PR #4500). To avoid 
> to
> break
> >     anything
> >      for existing user, I set the backoff strategy optional, the 
> user
> has to
> >      explicitly set to use it.
> >     
> >      I'm waiting a little more before cutting the release 
> (especially for
> >     BEAM-3392
> >      and BEAM-3087). However, I would like to cut the release asap.
> >     
> >      Thanks,
> >      Regards
> >      JB
> >     
> >     
> >      On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> >     > Hi guys,
> >     >
> >     > Some days ago, I proposed to start Beam 2.3.0 around January
> 26th. So,
> 

Re: [HEADS UP] Preparing Beam 2.3.0

[Kenneth Knowles]

I'd also love if we can use the notes to keep track of what needs to be
done for Gradle.

On Mon, Jan 29, 2018 at 10:29 AM, Jean-Baptiste Onofré 
wrote:

> Sure, I will ;)
>
> First steps:
>
> 0. Validate the build: mvn clean install -Prelease,sign
> 0bis. dryRun on the release: mvn release:prepare -DdryRun
>
> After that, I start the formal process. I keep you posted.
>
> Regards
> JB
>
> On 01/29/2018 07:23 PM, Alan Myrvold wrote:
> > Great. I'm interested in any pain points in the process, and steps we can
> > automate. Can you keep a rough log of issues you run into?
> >
> > On Mon, Jan 29, 2018 at 10:16 AM, Jean-Baptiste Onofré  > > wrote:
> >
> > We are now ready for the release. I'm starting the process.
> >
> > Thanks again for your help and support !
> >
> > Regards
> > JB
> >
> > On 01/29/2018 02:22 PM, Jean-Baptiste Onofré wrote:
> > > Hi,
> > >
> > > new update (and I hope the last one ;)):
> > >
> > > - BEAM-3551 has been reviewed and merged. This Jira is fixed for
> 2.3.0.
> > > - I just updated the PR for BEAM-793 (testing with write with
> backoff
> > feature in
> > > JdbcIO). I hope Eugene will give his green light to merge ;)
> > > - we have a new Jira (BEAM-3559) that has been created this
> morning and
> > targeted
> > > to 2.3.0. I asked for detail in the Jira and no update yet. Can I
> have an
> > update
> > > on this one ? Else I will bump it to 2.4.0.
> > >
> > > I will cut the 2.3.0 release tonight my time then.
> > >
> > > Thanks,
> > > Regards
> > > JB
> > >
> > > On 01/29/2018 07:14 AM, Jean-Baptiste Onofré wrote:
> > >> Hi,
> > >>
> > >> As BEAM-793 and BEAM-3551 are not release blocker, if I don't
> have update
> > in the
> > >> PRs in the coming couple of hours, I will bump these Jiras to
> 2.4.0 and start
> > >> the release process.
> > >>
> > >> Thanks !
> > >> Regards
> > >> JB
> > >>
> > >> On 01/28/2018 08:29 PM, Jean-Baptiste Onofré wrote:
> > >>> Hi guys,
> > >>>
> > >>> a new update about 2.3.0 release preparation. Only 2 Jira are
> pending (not
> > >>> blocker for the release but good to have):
> > >>>
> > >>> - BEAM-793: I updated the PR (#4500), waiting Eugene's feedback.
> > >>> - BEAM-3551: I created a PR (#4516), waiting Luke's feedback.
> > >>>
> > >>> Thanks to the timezone, I hope to have feedbacks soon.
> > >>>
> > >>> Anyway, these Jiras are not release blocker, so I will start the
> release
> > process
> > >>> tomorrow morning my time.
> > >>>
> > >>> By the way, I created 2.4.0 version in Jira.
> > >>>
> > >>> Thanks all for your help and support !
> > >>>
> > >>> Regards
> > >>> JB
> > >>>
> > >>> On 27/01/2018 13:00, Jean-Baptiste Onofré wrote:
> >  Hi guys,
> > 
> >  we still have 7 Jira targeted to 2.3.0.
> > 
> >  For most of them, Ismaël and I are doing the PRs/fixes and we
> have
> > review in
> >  progress.
> > 
> >  I'm a little bit concerned by BEAM-3392: it's flagged as
> blocker but it's
> >  related to a specific branch. Can you please provide an update
> asap ?
> > 
> >  However, I didn't have any update for BEAM-3087 (related to the
> Flink
> > runner).
> >  Without update soon, I will bump to 2.4.0.
> > 
> >  I would need a review on PR for BEAM-793 (PR #4500). To avoid
> to break
> > anything
> >  for existing user, I set the backoff strategy optional, the
> user has to
> >  explicitly set to use it.
> > 
> >  I'm waiting a little more before cutting the release
> (especially for
> > BEAM-3392
> >  and BEAM-3087). However, I would like to cut the release asap.
> > 
> >  Thanks,
> >  Regards
> >  JB
> > 
> > 
> >  On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> > > Hi guys,
> > >
> > > Some days ago, I proposed to start Beam 2.3.0 around January
> 26th. So,
> > we are
> > > few days from this date.
> > >
> > > As a best effort, can you please in Jira flag the Jira with fix
> > version 2.3.0
> > > and blocker for the release. Then, I will know when I can
> start the
> > release
> > > process.
> > >
> > > Thanks !
> > >
> > > Regards
> > > JB
> > >
> > 
> > >>
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org 
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Alan Myrvold]

Great. I'm interested in any pain points in the process, and steps we can
automate. Can you keep a rough log of issues you run into?

On Mon, Jan 29, 2018 at 10:16 AM, Jean-Baptiste Onofré 
wrote:

> We are now ready for the release. I'm starting the process.
>
> Thanks again for your help and support !
>
> Regards
> JB
>
> On 01/29/2018 02:22 PM, Jean-Baptiste Onofré wrote:
> > Hi,
> >
> > new update (and I hope the last one ;)):
> >
> > - BEAM-3551 has been reviewed and merged. This Jira is fixed for 2.3.0.
> > - I just updated the PR for BEAM-793 (testing with write with backoff
> feature in
> > JdbcIO). I hope Eugene will give his green light to merge ;)
> > - we have a new Jira (BEAM-3559) that has been created this morning and
> targeted
> > to 2.3.0. I asked for detail in the Jira and no update yet. Can I have
> an update
> > on this one ? Else I will bump it to 2.4.0.
> >
> > I will cut the 2.3.0 release tonight my time then.
> >
> > Thanks,
> > Regards
> > JB
> >
> > On 01/29/2018 07:14 AM, Jean-Baptiste Onofré wrote:
> >> Hi,
> >>
> >> As BEAM-793 and BEAM-3551 are not release blocker, if I don't have
> update in the
> >> PRs in the coming couple of hours, I will bump these Jiras to 2.4.0 and
> start
> >> the release process.
> >>
> >> Thanks !
> >> Regards
> >> JB
> >>
> >> On 01/28/2018 08:29 PM, Jean-Baptiste Onofré wrote:
> >>> Hi guys,
> >>>
> >>> a new update about 2.3.0 release preparation. Only 2 Jira are pending
> (not
> >>> blocker for the release but good to have):
> >>>
> >>> - BEAM-793: I updated the PR (#4500), waiting Eugene's feedback.
> >>> - BEAM-3551: I created a PR (#4516), waiting Luke's feedback.
> >>>
> >>> Thanks to the timezone, I hope to have feedbacks soon.
> >>>
> >>> Anyway, these Jiras are not release blocker, so I will start the
> release process
> >>> tomorrow morning my time.
> >>>
> >>> By the way, I created 2.4.0 version in Jira.
> >>>
> >>> Thanks all for your help and support !
> >>>
> >>> Regards
> >>> JB
> >>>
> >>> On 27/01/2018 13:00, Jean-Baptiste Onofré wrote:
>  Hi guys,
> 
>  we still have 7 Jira targeted to 2.3.0.
> 
>  For most of them, Ismaël and I are doing the PRs/fixes and we have
> review in
>  progress.
> 
>  I'm a little bit concerned by BEAM-3392: it's flagged as blocker but
> it's
>  related to a specific branch. Can you please provide an update asap ?
> 
>  However, I didn't have any update for BEAM-3087 (related to the Flink
> runner).
>  Without update soon, I will bump to 2.4.0.
> 
>  I would need a review on PR for BEAM-793 (PR #4500). To avoid to
> break anything
>  for existing user, I set the backoff strategy optional, the user has
> to
>  explicitly set to use it.
> 
>  I'm waiting a little more before cutting the release (especially for
> BEAM-3392
>  and BEAM-3087). However, I would like to cut the release asap.
> 
>  Thanks,
>  Regards
>  JB
> 
> 
>  On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > Some days ago, I proposed to start Beam 2.3.0 around January 26th.
> So, we are
> > few days from this date.
> >
> > As a best effort, can you please in Jira flag the Jira with fix
> version 2.3.0
> > and blocker for the release. Then, I will know when I can start the
> release
> > process.
> >
> > Thanks !
> >
> > Regards
> > JB
> >
> 
> >>
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

We are now ready for the release. I'm starting the process.

Thanks again for your help and support !

Regards
JB

On 01/29/2018 02:22 PM, Jean-Baptiste Onofré wrote:
> Hi,
> 
> new update (and I hope the last one ;)):
> 
> - BEAM-3551 has been reviewed and merged. This Jira is fixed for 2.3.0.
> - I just updated the PR for BEAM-793 (testing with write with backoff feature 
> in
> JdbcIO). I hope Eugene will give his green light to merge ;)
> - we have a new Jira (BEAM-3559) that has been created this morning and 
> targeted
> to 2.3.0. I asked for detail in the Jira and no update yet. Can I have an 
> update
> on this one ? Else I will bump it to 2.4.0.
> 
> I will cut the 2.3.0 release tonight my time then.
> 
> Thanks,
> Regards
> JB
> 
> On 01/29/2018 07:14 AM, Jean-Baptiste Onofré wrote:
>> Hi,
>>
>> As BEAM-793 and BEAM-3551 are not release blocker, if I don't have update in 
>> the
>> PRs in the coming couple of hours, I will bump these Jiras to 2.4.0 and start
>> the release process.
>>
>> Thanks !
>> Regards
>> JB
>>
>> On 01/28/2018 08:29 PM, Jean-Baptiste Onofré wrote:
>>> Hi guys,
>>>
>>> a new update about 2.3.0 release preparation. Only 2 Jira are pending (not
>>> blocker for the release but good to have):
>>>
>>> - BEAM-793: I updated the PR (#4500), waiting Eugene's feedback.
>>> - BEAM-3551: I created a PR (#4516), waiting Luke's feedback.
>>>
>>> Thanks to the timezone, I hope to have feedbacks soon.
>>>
>>> Anyway, these Jiras are not release blocker, so I will start the release 
>>> process
>>> tomorrow morning my time.
>>>
>>> By the way, I created 2.4.0 version in Jira.
>>>
>>> Thanks all for your help and support !
>>>
>>> Regards
>>> JB
>>>
>>> On 27/01/2018 13:00, Jean-Baptiste Onofré wrote:
 Hi guys,

 we still have 7 Jira targeted to 2.3.0.

 For most of them, Ismaël and I are doing the PRs/fixes and we have review 
 in
 progress.

 I'm a little bit concerned by BEAM-3392: it's flagged as blocker but it's
 related to a specific branch. Can you please provide an update asap ?

 However, I didn't have any update for BEAM-3087 (related to the Flink 
 runner).
 Without update soon, I will bump to 2.4.0.

 I would need a review on PR for BEAM-793 (PR #4500). To avoid to break 
 anything
 for existing user, I set the backoff strategy optional, the user has to
 explicitly set to use it.

 I'm waiting a little more before cutting the release (especially for 
 BEAM-3392
 and BEAM-3087). However, I would like to cut the release asap.

 Thanks,
 Regards
 JB


 On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> Hi guys,
>
> Some days ago, I proposed to start Beam 2.3.0 around January 26th. So, we 
> are
> few days from this date.
>
> As a best effort, can you please in Jira flag the Jira with fix version 
> 2.3.0
> and blocker for the release. Then, I will know when I can start the 
> release
> process.
>
> Thanks !
>
> Regards
> JB
>

>>
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Awesome, thanks Ahmet !

It's what I thought, but wanted to have team agreement ;)

Regards
JB

On 01/29/2018 06:19 PM, Ahmet Altay wrote:
> I moved BEAM-3559 out of 2.3.0, it is not targeted for this release.
> 
> On Mon, Jan 29, 2018 at 5:22 AM, Jean-Baptiste Onofré  > wrote:
> 
> Hi,
> 
> new update (and I hope the last one ;)):
> 
> - BEAM-3551 has been reviewed and merged. This Jira is fixed for 2.3.0.
> - I just updated the PR for BEAM-793 (testing with write with backoff 
> feature in
> JdbcIO). I hope Eugene will give his green light to merge ;)
> - we have a new Jira (BEAM-3559) that has been created this morning and 
> targeted
> to 2.3.0. I asked for detail in the Jira and no update yet. Can I have an 
> update
> on this one ? Else I will bump it to 2.4.0.
> 
> I will cut the 2.3.0 release tonight my time then.
> 
> Thanks,
> Regards
> JB
> 
> On 01/29/2018 07:14 AM, Jean-Baptiste Onofré wrote:
> > Hi,
> >
> > As BEAM-793 and BEAM-3551 are not release blocker, if I don't have 
> update
> in the
> > PRs in the coming couple of hours, I will bump these Jiras to 2.4.0 and 
> start
> > the release process.
> >
> > Thanks !
> > Regards
> > JB
> >
> > On 01/28/2018 08:29 PM, Jean-Baptiste Onofré wrote:
> >> Hi guys,
> >>
> >> a new update about 2.3.0 release preparation. Only 2 Jira are pending 
> (not
> >> blocker for the release but good to have):
> >>
> >> - BEAM-793: I updated the PR (#4500), waiting Eugene's feedback.
> >> - BEAM-3551: I created a PR (#4516), waiting Luke's feedback.
> >>
> >> Thanks to the timezone, I hope to have feedbacks soon.
> >>
> >> Anyway, these Jiras are not release blocker, so I will start the 
> release
> process
> >> tomorrow morning my time.
> >>
> >> By the way, I created 2.4.0 version in Jira.
> >>
> >> Thanks all for your help and support !
> >>
> >> Regards
> >> JB
> >>
> >> On 27/01/2018 13:00, Jean-Baptiste Onofré wrote:
> >>> Hi guys,
> >>>
> >>> we still have 7 Jira targeted to 2.3.0.
> >>>
> >>> For most of them, Ismaël and I are doing the PRs/fixes and we have 
> review in
> >>> progress.
> >>>
> >>> I'm a little bit concerned by BEAM-3392: it's flagged as blocker but 
> it's
> >>> related to a specific branch. Can you please provide an update asap ?
> >>>
> >>> However, I didn't have any update for BEAM-3087 (related to the Flink
> runner).
> >>> Without update soon, I will bump to 2.4.0.
> >>>
> >>> I would need a review on PR for BEAM-793 (PR #4500). To avoid to break
> anything
> >>> for existing user, I set the backoff strategy optional, the user has 
> to
> >>> explicitly set to use it.
> >>>
> >>> I'm waiting a little more before cutting the release (especially for
> BEAM-3392
> >>> and BEAM-3087). However, I would like to cut the release asap.
> >>>
> >>> Thanks,
> >>> Regards
> >>> JB
> >>>
> >>>
> >>> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
>  Hi guys,
> 
>  Some days ago, I proposed to start Beam 2.3.0 around January 26th. 
> So,
> we are
>  few days from this date.
> 
>  As a best effort, can you please in Jira flag the Jira with fix 
> version
> 2.3.0
>  and blocker for the release. Then, I will know when I can start the 
> release
>  process.
> 
>  Thanks !
> 
>  Regards
>  JB
> 
> >>>
> >
> 
> --
> Jean-Baptiste Onofré
> jbono...@apache.org 
> http://blog.nanthrax.net
> Talend - http://www.talend.com
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Hi,

As BEAM-793 and BEAM-3551 are not release blocker, if I don't have update in the
PRs in the coming couple of hours, I will bump these Jiras to 2.4.0 and start
the release process.

Thanks !
Regards
JB

On 01/28/2018 08:29 PM, Jean-Baptiste Onofré wrote:
> Hi guys,
> 
> a new update about 2.3.0 release preparation. Only 2 Jira are pending (not
> blocker for the release but good to have):
> 
> - BEAM-793: I updated the PR (#4500), waiting Eugene's feedback.
> - BEAM-3551: I created a PR (#4516), waiting Luke's feedback.
> 
> Thanks to the timezone, I hope to have feedbacks soon.
> 
> Anyway, these Jiras are not release blocker, so I will start the release 
> process
> tomorrow morning my time.
> 
> By the way, I created 2.4.0 version in Jira.
> 
> Thanks all for your help and support !
> 
> Regards
> JB
> 
> On 27/01/2018 13:00, Jean-Baptiste Onofré wrote:
>> Hi guys,
>>
>> we still have 7 Jira targeted to 2.3.0.
>>
>> For most of them, Ismaël and I are doing the PRs/fixes and we have review in
>> progress.
>>
>> I'm a little bit concerned by BEAM-3392: it's flagged as blocker but it's
>> related to a specific branch. Can you please provide an update asap ?
>>
>> However, I didn't have any update for BEAM-3087 (related to the Flink 
>> runner).
>> Without update soon, I will bump to 2.4.0.
>>
>> I would need a review on PR for BEAM-793 (PR #4500). To avoid to break 
>> anything
>> for existing user, I set the backoff strategy optional, the user has to
>> explicitly set to use it.
>>
>> I'm waiting a little more before cutting the release (especially for 
>> BEAM-3392
>> and BEAM-3087). However, I would like to cut the release asap.
>>
>> Thanks,
>> Regards
>> JB
>>
>>
>> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
>>> Hi guys,
>>>
>>> Some days ago, I proposed to start Beam 2.3.0 around January 26th. So, we 
>>> are
>>> few days from this date.
>>>
>>> As a best effort, can you please in Jira flag the Jira with fix version 
>>> 2.3.0
>>> and blocker for the release. Then, I will know when I can start the release
>>> process.
>>>
>>> Thanks !
>>>
>>> Regards
>>> JB
>>>
>>

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

OK, thanks. I keep you posted ;)

Regards
JB

On 28/01/2018 15:06, Romain Manni-Bucau wrote:

Will be online this afternoon. Ping me if you need help.

Le 28 janv. 2018 11:36, "Jean-Baptiste Onofré" > a écrit :


By the way, I created BEAM-3551 for the tracking.

I will work on it today.

Regards
JB

On 01/28/2018 09:50 AM, Romain Manni-Bucau wrote:
 > Hi guys
 >
 > Out if curiosity, can -parameters (javac) be part of the 2.3 if
not already?
 >
 > Le 27 janv. 2018 18:39, "Jean-Baptiste Onofré" 
 > >> a écrit :
 >
 >     Hi Reuven,
 >
 >     I gonna bump 3392 and 3087 to 2.4.0. For the PR, yes Eugene
did a first round
 >     review, I will work on it now.
 >
 >     We will pretty close !
 >
 >     Thanks !
 >     Regards
 >     JB
 >
 >     On 01/27/2018 05:58 PM, Reuven Lax wrote:
 >     > Seems that 3392 is not a blocker, and neither is 3087.
Looks like Eugene is
 >     > already reviewing the PR form BEAM-793.
 >     >
 >     > Reuven
 >     >
 >     > On Sat, Jan 27, 2018 at 4:00 AM, Jean-Baptiste Onofré

 >     >
 >     > 
     >
 >     >     Hi guys,
 >     >
 >     >     we still have 7 Jira targeted to 2.3.0.
 >     >
 >     >     For most of them, Ismaël and I are doing the PRs/fixes
and we have
 >     review in
 >     >     progress.
 >     >
 >     >     I'm a little bit concerned by BEAM-3392: it's flagged
as blocker but it's
 >     >     related to a specific branch. Can you please provide an
update asap ?
 >     >
 >     >     However, I didn't have any update for BEAM-3087
(related to the Flink
 >     runner).
 >     >     Without update soon, I will bump to 2.4.0.
 >     >
 >     >     I would need a review on PR for BEAM-793 (PR #4500). To
avoid to break
 >     anything
 >     >     for existing user, I set the backoff strategy optional,
the user has to
 >     >     explicitly set to use it.
 >     >
 >     >     I'm waiting a little more before cutting the release
(especially for
 >     BEAM-3392
 >     >     and BEAM-3087). However, I would like to cut the
release asap.
 >     >
 >     >     Thanks,
 >     >     Regards
 >     >     JB
 >     >
 >     >
 >     >     On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
 >     >     > Hi guys,
 >     >     >
 >     >     > Some days ago, I proposed to start Beam 2.3.0 around
January 26th.
 >     So, we are
 >     >     > few days from this date.
 >     >     >
 >     >     > As a best effort, can you please in Jira flag the
Jira with fix
 >     version 2.3.0
 >     >     > and blocker for the release. Then, I will know when I
can start the
 >     >     release process.
 >     >     >
 >     >     > Thanks !
 >     >     >
 >     >     > Regards
 >     >     > JB
 >     >     >
 >     >
 >     >     --
 >     >     Jean-Baptiste Onofré
 >     > jbono...@apache.org 
>
 >     
>>
 >     > http://blog.nanthrax.net
 >     >     Talend - http://www.talend.com
 >     >
 >     >
 >
 >     --
 >     Jean-Baptiste Onofré
 > jbono...@apache.org 
>
 > http://blog.nanthrax.net
 >     Talend - http://www.talend.com
 >

--
Jean-Baptiste Onofré
jbono...@apache.org 
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Romain Manni-Bucau]

Will be online this afternoon. Ping me if you need help.

Le 28 janv. 2018 11:36, "Jean-Baptiste Onofré"  a écrit :

> By the way, I created BEAM-3551 for the tracking.
>
> I will work on it today.
>
> Regards
> JB
>
> On 01/28/2018 09:50 AM, Romain Manni-Bucau wrote:
> > Hi guys
> >
> > Out if curiosity, can -parameters (javac) be part of the 2.3 if not
> already?
> >
> > Le 27 janv. 2018 18:39, "Jean-Baptiste Onofré"  > > a écrit :
> >
> > Hi Reuven,
> >
> > I gonna bump 3392 and 3087 to 2.4.0. For the PR, yes Eugene did a
> first round
> > review, I will work on it now.
> >
> > We will pretty close !
> >
> > Thanks !
> > Regards
> > JB
> >
> > On 01/27/2018 05:58 PM, Reuven Lax wrote:
> > > Seems that 3392 is not a blocker, and neither is 3087. Looks like
> Eugene is
> > > already reviewing the PR form BEAM-793.
> > >
> > > Reuven
> > >
> > > On Sat, Jan 27, 2018 at 4:00 AM, Jean-Baptiste Onofré <
> j...@nanthrax.net
> > 
> > > >> wrote:
> > >
> > > Hi guys,
> > >
> > > we still have 7 Jira targeted to 2.3.0.
> > >
> > > For most of them, Ismaël and I are doing the PRs/fixes and we
> have
> > review in
> > > progress.
> > >
> > > I'm a little bit concerned by BEAM-3392: it's flagged as
> blocker but it's
> > > related to a specific branch. Can you please provide an update
> asap ?
> > >
> > > However, I didn't have any update for BEAM-3087 (related to
> the Flink
> > runner).
> > > Without update soon, I will bump to 2.4.0.
> > >
> > > I would need a review on PR for BEAM-793 (PR #4500). To avoid
> to break
> > anything
> > > for existing user, I set the backoff strategy optional, the
> user has to
> > > explicitly set to use it.
> > >
> > > I'm waiting a little more before cutting the release
> (especially for
> > BEAM-3392
> > > and BEAM-3087). However, I would like to cut the release asap.
> > >
> > > Thanks,
> > > Regards
> > > JB
> > >
> > >
> > > On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> > > > Hi guys,
> > > >
> > > > Some days ago, I proposed to start Beam 2.3.0 around January
> 26th.
> > So, we are
> > > > few days from this date.
> > > >
> > > > As a best effort, can you please in Jira flag the Jira with
> fix
> > version 2.3.0
> > > > and blocker for the release. Then, I will know when I can
> start the
> > > release process.
> > > >
> > > > Thanks !
> > > >
> > > > Regards
> > > > JB
> > > >
> > >
> > > --
> > > Jean-Baptiste Onofré
> > > jbono...@apache.org 
> > >
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> > >
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org 
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

By the way, I created BEAM-3551 for the tracking.

I will work on it today.

Regards
JB

On 01/28/2018 09:50 AM, Romain Manni-Bucau wrote:
> Hi guys
> 
> Out if curiosity, can -parameters (javac) be part of the 2.3 if not already?
> 
> Le 27 janv. 2018 18:39, "Jean-Baptiste Onofré"  > a écrit :
> 
> Hi Reuven,
> 
> I gonna bump 3392 and 3087 to 2.4.0. For the PR, yes Eugene did a first 
> round
> review, I will work on it now.
> 
> We will pretty close !
> 
> Thanks !
> Regards
> JB
> 
> On 01/27/2018 05:58 PM, Reuven Lax wrote:
> > Seems that 3392 is not a blocker, and neither is 3087. Looks like 
> Eugene is
> > already reviewing the PR form BEAM-793.
> >
> > Reuven
> >
> > On Sat, Jan 27, 2018 at 4:00 AM, Jean-Baptiste Onofré  
> > >> wrote:
> >
> >     Hi guys,
> >
> >     we still have 7 Jira targeted to 2.3.0.
> >
> >     For most of them, Ismaël and I are doing the PRs/fixes and we have
> review in
> >     progress.
> >
> >     I'm a little bit concerned by BEAM-3392: it's flagged as blocker 
> but it's
> >     related to a specific branch. Can you please provide an update asap 
> ?
> >
> >     However, I didn't have any update for BEAM-3087 (related to the 
> Flink
> runner).
> >     Without update soon, I will bump to 2.4.0.
> >
> >     I would need a review on PR for BEAM-793 (PR #4500). To avoid to 
> break
> anything
> >     for existing user, I set the backoff strategy optional, the user 
> has to
> >     explicitly set to use it.
> >
> >     I'm waiting a little more before cutting the release (especially for
> BEAM-3392
> >     and BEAM-3087). However, I would like to cut the release asap.
> >
> >     Thanks,
> >     Regards
> >     JB
> >
> >
> >     On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> >     > Hi guys,
> >     >
> >     > Some days ago, I proposed to start Beam 2.3.0 around January 26th.
> So, we are
> >     > few days from this date.
> >     >
> >     > As a best effort, can you please in Jira flag the Jira with fix
> version 2.3.0
> >     > and blocker for the release. Then, I will know when I can start 
> the
> >     release process.
> >     >
> >     > Thanks !
> >     >
> >     > Regards
> >     > JB
> >     >
> >
> >     --
> >     Jean-Baptiste Onofré
> >     jbono...@apache.org 
> >
> >     http://blog.nanthrax.net
> >     Talend - http://www.talend.com
> >
> >
> 
> --
> Jean-Baptiste Onofré
> jbono...@apache.org 
> http://blog.nanthrax.net
> Talend - http://www.talend.com
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Hi,

it's not yet done. Let me do a PR to test that.

Regards
JB

On 01/28/2018 09:50 AM, Romain Manni-Bucau wrote:
> Hi guys
> 
> Out if curiosity, can -parameters (javac) be part of the 2.3 if not already?
> 
> Le 27 janv. 2018 18:39, "Jean-Baptiste Onofré"  > a écrit :
> 
> Hi Reuven,
> 
> I gonna bump 3392 and 3087 to 2.4.0. For the PR, yes Eugene did a first 
> round
> review, I will work on it now.
> 
> We will pretty close !
> 
> Thanks !
> Regards
> JB
> 
> On 01/27/2018 05:58 PM, Reuven Lax wrote:
> > Seems that 3392 is not a blocker, and neither is 3087. Looks like 
> Eugene is
> > already reviewing the PR form BEAM-793.
> >
> > Reuven
> >
> > On Sat, Jan 27, 2018 at 4:00 AM, Jean-Baptiste Onofré  
> > >> wrote:
> >
> >     Hi guys,
> >
> >     we still have 7 Jira targeted to 2.3.0.
> >
> >     For most of them, Ismaël and I are doing the PRs/fixes and we have
> review in
> >     progress.
> >
> >     I'm a little bit concerned by BEAM-3392: it's flagged as blocker 
> but it's
> >     related to a specific branch. Can you please provide an update asap 
> ?
> >
> >     However, I didn't have any update for BEAM-3087 (related to the 
> Flink
> runner).
> >     Without update soon, I will bump to 2.4.0.
> >
> >     I would need a review on PR for BEAM-793 (PR #4500). To avoid to 
> break
> anything
> >     for existing user, I set the backoff strategy optional, the user 
> has to
> >     explicitly set to use it.
> >
> >     I'm waiting a little more before cutting the release (especially for
> BEAM-3392
> >     and BEAM-3087). However, I would like to cut the release asap.
> >
> >     Thanks,
> >     Regards
> >     JB
> >
> >
> >     On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> >     > Hi guys,
> >     >
> >     > Some days ago, I proposed to start Beam 2.3.0 around January 26th.
> So, we are
> >     > few days from this date.
> >     >
> >     > As a best effort, can you please in Jira flag the Jira with fix
> version 2.3.0
> >     > and blocker for the release. Then, I will know when I can start 
> the
> >     release process.
> >     >
> >     > Thanks !
> >     >
> >     > Regards
> >     > JB
> >     >
> >
> >     --
> >     Jean-Baptiste Onofré
> >     jbono...@apache.org 
> >
> >     http://blog.nanthrax.net
> >     Talend - http://www.talend.com
> >
> >
> 
> --
> Jean-Baptiste Onofré
> jbono...@apache.org 
> http://blog.nanthrax.net
> Talend - http://www.talend.com
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Romain Manni-Bucau]

Hi guys

Out if curiosity, can -parameters (javac) be part of the 2.3 if not already?

Le 27 janv. 2018 18:39, "Jean-Baptiste Onofré"  a écrit :

> Hi Reuven,
>
> I gonna bump 3392 and 3087 to 2.4.0. For the PR, yes Eugene did a first
> round
> review, I will work on it now.
>
> We will pretty close !
>
> Thanks !
> Regards
> JB
>
> On 01/27/2018 05:58 PM, Reuven Lax wrote:
> > Seems that 3392 is not a blocker, and neither is 3087. Looks like Eugene
> is
> > already reviewing the PR form BEAM-793.
> >
> > Reuven
> >
> > On Sat, Jan 27, 2018 at 4:00 AM, Jean-Baptiste Onofré  > > wrote:
> >
> > Hi guys,
> >
> > we still have 7 Jira targeted to 2.3.0.
> >
> > For most of them, Ismaël and I are doing the PRs/fixes and we have
> review in
> > progress.
> >
> > I'm a little bit concerned by BEAM-3392: it's flagged as blocker but
> it's
> > related to a specific branch. Can you please provide an update asap ?
> >
> > However, I didn't have any update for BEAM-3087 (related to the
> Flink runner).
> > Without update soon, I will bump to 2.4.0.
> >
> > I would need a review on PR for BEAM-793 (PR #4500). To avoid to
> break anything
> > for existing user, I set the backoff strategy optional, the user has
> to
> > explicitly set to use it.
> >
> > I'm waiting a little more before cutting the release (especially for
> BEAM-3392
> > and BEAM-3087). However, I would like to cut the release asap.
> >
> > Thanks,
> > Regards
> > JB
> >
> >
> > On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> > > Hi guys,
> > >
> > > Some days ago, I proposed to start Beam 2.3.0 around January 26th.
> So, we are
> > > few days from this date.
> > >
> > > As a best effort, can you please in Jira flag the Jira with fix
> version 2.3.0
> > > and blocker for the release. Then, I will know when I can start the
> > release process.
> > >
> > > Thanks !
> > >
> > > Regards
> > > JB
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org 
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Hi Reuven,

I gonna bump 3392 and 3087 to 2.4.0. For the PR, yes Eugene did a first round
review, I will work on it now.

We will pretty close !

Thanks !
Regards
JB

On 01/27/2018 05:58 PM, Reuven Lax wrote:
> Seems that 3392 is not a blocker, and neither is 3087. Looks like Eugene is
> already reviewing the PR form BEAM-793.
> 
> Reuven
> 
> On Sat, Jan 27, 2018 at 4:00 AM, Jean-Baptiste Onofré  > wrote:
> 
> Hi guys,
> 
> we still have 7 Jira targeted to 2.3.0.
> 
> For most of them, Ismaël and I are doing the PRs/fixes and we have review 
> in
> progress.
> 
> I'm a little bit concerned by BEAM-3392: it's flagged as blocker but it's
> related to a specific branch. Can you please provide an update asap ?
> 
> However, I didn't have any update for BEAM-3087 (related to the Flink 
> runner).
> Without update soon, I will bump to 2.4.0.
> 
> I would need a review on PR for BEAM-793 (PR #4500). To avoid to break 
> anything
> for existing user, I set the backoff strategy optional, the user has to
> explicitly set to use it.
> 
> I'm waiting a little more before cutting the release (especially for 
> BEAM-3392
> and BEAM-3087). However, I would like to cut the release asap.
> 
> Thanks,
> Regards
> JB
> 
> 
> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > Some days ago, I proposed to start Beam 2.3.0 around January 26th. So, 
> we are
> > few days from this date.
> >
> > As a best effort, can you please in Jira flag the Jira with fix version 
> 2.3.0
> > and blocker for the release. Then, I will know when I can start the
> release process.
> >
> > Thanks !
> >
> > Regards
> > JB
> >
> 
> --
> Jean-Baptiste Onofré
> jbono...@apache.org 
> http://blog.nanthrax.net
> Talend - http://www.talend.com
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Reuven Lax]

Seems that 3392 is not a blocker, and neither is 3087. Looks like Eugene is
already reviewing the PR form BEAM-793.

Reuven

On Sat, Jan 27, 2018 at 4:00 AM, Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> we still have 7 Jira targeted to 2.3.0.
>
> For most of them, Ismaël and I are doing the PRs/fixes and we have review
> in
> progress.
>
> I'm a little bit concerned by BEAM-3392: it's flagged as blocker but it's
> related to a specific branch. Can you please provide an update asap ?
>
> However, I didn't have any update for BEAM-3087 (related to the Flink
> runner).
> Without update soon, I will bump to 2.4.0.
>
> I would need a review on PR for BEAM-793 (PR #4500). To avoid to break
> anything
> for existing user, I set the backoff strategy optional, the user has to
> explicitly set to use it.
>
> I'm waiting a little more before cutting the release (especially for
> BEAM-3392
> and BEAM-3087). However, I would like to cut the release asap.
>
> Thanks,
> Regards
> JB
>
>
> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > Some days ago, I proposed to start Beam 2.3.0 around January 26th. So,
> we are
> > few days from this date.
> >
> > As a best effort, can you please in Jira flag the Jira with fix version
> 2.3.0
> > and blocker for the release. Then, I will know when I can start the
> release process.
> >
> > Thanks !
> >
> > Regards
> > JB
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Hi guys,

we still have 7 Jira targeted to 2.3.0.

For most of them, Ismaël and I are doing the PRs/fixes and we have review in
progress.

I'm a little bit concerned by BEAM-3392: it's flagged as blocker but it's
related to a specific branch. Can you please provide an update asap ?

However, I didn't have any update for BEAM-3087 (related to the Flink runner).
Without update soon, I will bump to 2.4.0.

I would need a review on PR for BEAM-793 (PR #4500). To avoid to break anything
for existing user, I set the backoff strategy optional, the user has to
explicitly set to use it.

I'm waiting a little more before cutting the release (especially for BEAM-3392
and BEAM-3087). However, I would like to cut the release asap.

Thanks,
Regards
JB


On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> Hi guys,
> 
> Some days ago, I proposed to start Beam 2.3.0 around January 26th. So, we are
> few days from this date.
> 
> As a best effort, can you please in Jira flag the Jira with fix version 2.3.0
> and blocker for the release. Then, I will know when I can start the release 
> process.
> 
> Thanks !
> 
> Regards
> JB
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Just to be clear on the CassandraIO issues: they are not regression (it was like
this since the addition of the CassandraIO), they are not data loss. I consider
as a bug/improvement as the read is performed on a single worker (the split
returns always 1).

As said, I gonna work today on those issues as a best effort. However, I keep
the release cut "deadline" to tonight/tomorrow early morning my time.

Regards
JB

On 01/26/2018 06:33 AM, Reuven Lax wrote:
> I agree - if CassandraIO issues are not regressions (and are not critical
> data-loss bugs), I don't think the release should block on it.
> 
> Reuven
> 
> On Thu, Jan 25, 2018 at 9:07 PM, Jean-Baptiste Onofré  > wrote:
> 
> I disagree: the CassandraIO issues are not blocker as they are not 
> regression.
> 
> In order to insure the release pace, I will go forward, these issues will 
> be fix
> for the next release cycle.
> 
> For the blog, it's up to you. However, with the next release pace we do, 
> I'm not
> sure it makes sense to do it for each release.
> 
> We still have a full day before the release cut. So, let me do my best on 
> the
> CassandraIO issues, as a best effort. But let's target to cut the release
> tonight/tomorrow early morning as planned.
> 
> Regards
> JB
> 
> On 01/25/2018 09:56 PM, Ismaël Mejía wrote:
> > I saw some recent reports on issues with CassandraIO that are not
> > blockers (not data loss) but IMO deserve to be included because
> > basically the issues imply that users cannot read from Cassandra in
> > parallel, and they were reported by production users. Probably a good
> > idea to finish these before the cut (they don't seem really hard to
> > fix), even if this implies to move the release cut one or two days.
> >
> > I also would like to volunteer to write the release blog post in
> > particular I would like to add a new section to thank the people that
> > contributed in this release as other projects do.
> >
> > On Thu, Jan 25, 2018 at 9:08 PM, Reuven Lax  > wrote:
> >> Thank you for running this JB!
> >>
> >> On Thu, Jan 25, 2018 at 11:50 AM, Jean-Baptiste Onofré 
>  >
> >> wrote:
> >>>
> >>> Hi guys,
> >>>
> >>> Kenn and I are doing the latest triage. I'm creating some PRs that 
> would
> >>> be good
> >>> for 2.3.0 (but not blocker).
> >>>
> >>> As discussed, I plan to start the release process tomorrow evening (my
> >>> time).
> >>>
> >>> Thanks !
> >>> Regards
> >>> JB
> >>>
> >>> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
>  Hi guys,
> 
>  Some days ago, I proposed to start Beam 2.3.0 around January 26th. 
> So,
>  we are
>  few days from this date.
> 
>  As a best effort, can you please in Jira flag the Jira with fix 
> version
>  2.3.0
>  and blocker for the release. Then, I will know when I can start the
>  release process.
> 
>  Thanks !
> 
>  Regards
>  JB
> 
> >>>
> >>> --
> >>> Jean-Baptiste Onofré
> >>> jbono...@apache.org 
> >>> http://blog.nanthrax.net
> >>> Talend - http://www.talend.com
> >>
> >>
> 
> --
> Jean-Baptiste Onofré
> jbono...@apache.org 
> http://blog.nanthrax.net
> Talend - http://www.talend.com
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Reuven Lax]

I agree - if CassandraIO issues are not regressions (and are not critical
data-loss bugs), I don't think the release should block on it.

Reuven

On Thu, Jan 25, 2018 at 9:07 PM, Jean-Baptiste Onofré 
wrote:

> I disagree: the CassandraIO issues are not blocker as they are not
> regression.
>
> In order to insure the release pace, I will go forward, these issues will
> be fix
> for the next release cycle.
>
> For the blog, it's up to you. However, with the next release pace we do,
> I'm not
> sure it makes sense to do it for each release.
>
> We still have a full day before the release cut. So, let me do my best on
> the
> CassandraIO issues, as a best effort. But let's target to cut the release
> tonight/tomorrow early morning as planned.
>
> Regards
> JB
>
> On 01/25/2018 09:56 PM, Ismaël Mejía wrote:
> > I saw some recent reports on issues with CassandraIO that are not
> > blockers (not data loss) but IMO deserve to be included because
> > basically the issues imply that users cannot read from Cassandra in
> > parallel, and they were reported by production users. Probably a good
> > idea to finish these before the cut (they don't seem really hard to
> > fix), even if this implies to move the release cut one or two days.
> >
> > I also would like to volunteer to write the release blog post in
> > particular I would like to add a new section to thank the people that
> > contributed in this release as other projects do.
> >
> > On Thu, Jan 25, 2018 at 9:08 PM, Reuven Lax  wrote:
> >> Thank you for running this JB!
> >>
> >> On Thu, Jan 25, 2018 at 11:50 AM, Jean-Baptiste Onofré  >
> >> wrote:
> >>>
> >>> Hi guys,
> >>>
> >>> Kenn and I are doing the latest triage. I'm creating some PRs that
> would
> >>> be good
> >>> for 2.3.0 (but not blocker).
> >>>
> >>> As discussed, I plan to start the release process tomorrow evening (my
> >>> time).
> >>>
> >>> Thanks !
> >>> Regards
> >>> JB
> >>>
> >>> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
>  Hi guys,
> 
>  Some days ago, I proposed to start Beam 2.3.0 around January 26th. So,
>  we are
>  few days from this date.
> 
>  As a best effort, can you please in Jira flag the Jira with fix
> version
>  2.3.0
>  and blocker for the release. Then, I will know when I can start the
>  release process.
> 
>  Thanks !
> 
>  Regards
>  JB
> 
> >>>
> >>> --
> >>> Jean-Baptiste Onofré
> >>> jbono...@apache.org
> >>> http://blog.nanthrax.net
> >>> Talend - http://www.talend.com
> >>
> >>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

I disagree: the CassandraIO issues are not blocker as they are not regression.

In order to insure the release pace, I will go forward, these issues will be fix
for the next release cycle.

For the blog, it's up to you. However, with the next release pace we do, I'm not
sure it makes sense to do it for each release.

We still have a full day before the release cut. So, let me do my best on the
CassandraIO issues, as a best effort. But let's target to cut the release
tonight/tomorrow early morning as planned.

Regards
JB

On 01/25/2018 09:56 PM, Ismaël Mejía wrote:
> I saw some recent reports on issues with CassandraIO that are not
> blockers (not data loss) but IMO deserve to be included because
> basically the issues imply that users cannot read from Cassandra in
> parallel, and they were reported by production users. Probably a good
> idea to finish these before the cut (they don't seem really hard to
> fix), even if this implies to move the release cut one or two days.
> 
> I also would like to volunteer to write the release blog post in
> particular I would like to add a new section to thank the people that
> contributed in this release as other projects do.
> 
> On Thu, Jan 25, 2018 at 9:08 PM, Reuven Lax  wrote:
>> Thank you for running this JB!
>>
>> On Thu, Jan 25, 2018 at 11:50 AM, Jean-Baptiste Onofré 
>> wrote:
>>>
>>> Hi guys,
>>>
>>> Kenn and I are doing the latest triage. I'm creating some PRs that would
>>> be good
>>> for 2.3.0 (but not blocker).
>>>
>>> As discussed, I plan to start the release process tomorrow evening (my
>>> time).
>>>
>>> Thanks !
>>> Regards
>>> JB
>>>
>>> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
 Hi guys,

 Some days ago, I proposed to start Beam 2.3.0 around January 26th. So,
 we are
 few days from this date.

 As a best effort, can you please in Jira flag the Jira with fix version
 2.3.0
 and blocker for the release. Then, I will know when I can start the
 release process.

 Thanks !

 Regards
 JB

>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>
>>

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Kenneth Knowles]

Agreed. I would say if a previously usable IO became unusable that is (on a
case-by-case basis) a fine cause to block a release. Are the JIRAs filed?

On Thu, Jan 25, 2018 at 12:56 PM, Ismaël Mejía  wrote:

> I saw some recent reports on issues with CassandraIO that are not
> blockers (not data loss) but IMO deserve to be included because
> basically the issues imply that users cannot read from Cassandra in
> parallel, and they were reported by production users. Probably a good
> idea to finish these before the cut (they don't seem really hard to
> fix), even if this implies to move the release cut one or two days.
>
> I also would like to volunteer to write the release blog post in
> particular I would like to add a new section to thank the people that
> contributed in this release as other projects do.
>
> On Thu, Jan 25, 2018 at 9:08 PM, Reuven Lax  wrote:
> > Thank you for running this JB!
> >
> > On Thu, Jan 25, 2018 at 11:50 AM, Jean-Baptiste Onofré 
> > wrote:
> >>
> >> Hi guys,
> >>
> >> Kenn and I are doing the latest triage. I'm creating some PRs that would
> >> be good
> >> for 2.3.0 (but not blocker).
> >>
> >> As discussed, I plan to start the release process tomorrow evening (my
> >> time).
> >>
> >> Thanks !
> >> Regards
> >> JB
> >>
> >> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> >> > Hi guys,
> >> >
> >> > Some days ago, I proposed to start Beam 2.3.0 around January 26th. So,
> >> > we are
> >> > few days from this date.
> >> >
> >> > As a best effort, can you please in Jira flag the Jira with fix
> version
> >> > 2.3.0
> >> > and blocker for the release. Then, I will know when I can start the
> >> > release process.
> >> >
> >> > Thanks !
> >> >
> >> > Regards
> >> > JB
> >> >
> >>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >
> >
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Ismaël Mejía]

I saw some recent reports on issues with CassandraIO that are not
blockers (not data loss) but IMO deserve to be included because
basically the issues imply that users cannot read from Cassandra in
parallel, and they were reported by production users. Probably a good
idea to finish these before the cut (they don't seem really hard to
fix), even if this implies to move the release cut one or two days.

I also would like to volunteer to write the release blog post in
particular I would like to add a new section to thank the people that
contributed in this release as other projects do.

On Thu, Jan 25, 2018 at 9:08 PM, Reuven Lax  wrote:
> Thank you for running this JB!
>
> On Thu, Jan 25, 2018 at 11:50 AM, Jean-Baptiste Onofré 
> wrote:
>>
>> Hi guys,
>>
>> Kenn and I are doing the latest triage. I'm creating some PRs that would
>> be good
>> for 2.3.0 (but not blocker).
>>
>> As discussed, I plan to start the release process tomorrow evening (my
>> time).
>>
>> Thanks !
>> Regards
>> JB
>>
>> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
>> > Hi guys,
>> >
>> > Some days ago, I proposed to start Beam 2.3.0 around January 26th. So,
>> > we are
>> > few days from this date.
>> >
>> > As a best effort, can you please in Jira flag the Jira with fix version
>> > 2.3.0
>> > and blocker for the release. Then, I will know when I can start the
>> > release process.
>> >
>> > Thanks !
>> >
>> > Regards
>> > JB
>> >
>>
>> --
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Reuven Lax]

Thank you for running this JB!

On Thu, Jan 25, 2018 at 11:50 AM, Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> Kenn and I are doing the latest triage. I'm creating some PRs that would
> be good
> for 2.3.0 (but not blocker).
>
> As discussed, I plan to start the release process tomorrow evening (my
> time).
>
> Thanks !
> Regards
> JB
>
> On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> > Hi guys,
> >
> > Some days ago, I proposed to start Beam 2.3.0 around January 26th. So,
> we are
> > few days from this date.
> >
> > As a best effort, can you please in Jira flag the Jira with fix version
> 2.3.0
> > and blocker for the release. Then, I will know when I can start the
> release process.
> >
> > Thanks !
> >
> > Regards
> > JB
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Hi guys,

Kenn and I are doing the latest triage. I'm creating some PRs that would be good
for 2.3.0 (but not blocker).

As discussed, I plan to start the release process tomorrow evening (my time).

Thanks !
Regards
JB

On 01/23/2018 10:39 AM, Jean-Baptiste Onofré wrote:
> Hi guys,
> 
> Some days ago, I proposed to start Beam 2.3.0 around January 26th. So, we are
> few days from this date.
> 
> As a best effort, can you please in Jira flag the Jira with fix version 2.3.0
> and blocker for the release. Then, I will know when I can start the release 
> process.
> 
> Thanks !
> 
> Regards
> JB
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Eugene Kirpichov]

Merged. Affects most files in Beam, so now probably everybody with a PR has
a conflict, apologies for the inconvenience.

On Tue, Jan 23, 2018 at 3:38 PM Eugene Kirpichov 
wrote:

> PR is out https://github.com/apache/beam/pull/4470 - a net reduction of a
> couple thousand LOC due to lambdas!
>
>
> On Tue, Jan 23, 2018 at 12:16 PM Jean-Baptiste Onofré 
> wrote:
>
>> Awesome !
>>
>> Ready to review if you want !
>>
>> Regards
>> JB
>>
>> On 23/01/2018 20:48, Eugene Kirpichov wrote:
>> > Regarding Java 8, I'm about to send a large mechanical PR converting a
>> > lot of code to use lambdas and better type inference.
>> >
>> > On Tue, Jan 23, 2018 at 11:37 AM Jean-Baptiste Onofré > > > wrote:
>> >
>> > By the way, I would like to complete the Java 8 support (the
>> subtasks in
>> > the main Java 8 Jira). So, let me try to move forward on this.
>> >
>> > Regards
>> > JB
>> >
>> > On 23/01/2018 19:51, Reuven Lax wrote:
>> >  > Sounds good. Also many things that are currently flagged as 2.3.0
>> > don't
>> >  > appear to be actual release blockers to me.
>> >  >
>> >  > On Tue, Jan 23, 2018 at 1:39 AM, Jean-Baptiste Onofré
>> > 
>> >  > >> wrote:
>> >  >
>> >  > Hi guys,
>> >  >
>> >  > Some days ago, I proposed to start Beam 2.3.0 around January
>> > 26th.
>> >  > So, we are
>> >  > few days from this date.
>> >  >
>> >  > As a best effort, can you please in Jira flag the Jira with
>> fix
>> >  > version 2.3.0
>> >  > and blocker for the release. Then, I will know when I can
>> > start the
>> >  > release process.
>> >  >
>> >  > Thanks !
>> >  >
>> >  > Regards
>> >  > JB
>> >  > --
>> >  > Jean-Baptiste Onofré
>> >  > jbono...@apache.org 
>> > >
>> >  > http://blog.nanthrax.net
>> >  > Talend - http://www.talend.com
>> >  >
>> >  >
>> >
>>
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Lukasz Cwik]

I fear that this list has been the "priority" list for bug fixes and
dropping the fix version will lose this information. I would be open for a
new label if we really wanted to change this but labels can be forgotten
about as well.

On Tue, Jan 23, 2018 at 3:06 PM, Alan Myrvold  wrote:

> Are there improvements to the release process to make the triaging of open
> issues easier?
>
> I see 30 unresolved issues with fixVersion 2.3.0 in
> https://issues.apache.org/jira/browse/BEAM-3160?jql=
> project%20%3D%20BEAM%20AND%20status%20%3D%20Open%20AND%
> 20fixVersion%20%3D%202.3.0%20ORDER%20BY%20updated%20DESC
>
> The release process, https://beam.apache.org/contribute/release-guide/#
> create-a-new-version-in-jira
> indicates that all these issues will be moved to 2.4.0 if they are not
> resolved.  Would it be better to unset the fixVersion for any issues that
> aren't fixed instead of moving them to the next version?
>
> On Tue, Jan 23, 2018 at 12:16 PM, Jean-Baptiste Onofré 
> wrote:
>
>> Awesome !
>>
>> Ready to review if you want !
>>
>> Regards
>> JB
>>
>> On 23/01/2018 20:48, Eugene Kirpichov wrote:
>>
>>> Regarding Java 8, I'm about to send a large mechanical PR converting a
>>> lot of code to use lambdas and better type inference.
>>>
>>> On Tue, Jan 23, 2018 at 11:37 AM Jean-Baptiste Onofré >> > wrote:
>>>
>>> By the way, I would like to complete the Java 8 support (the
>>> subtasks in
>>> the main Java 8 Jira). So, let me try to move forward on this.
>>>
>>> Regards
>>> JB
>>>
>>> On 23/01/2018 19:51, Reuven Lax wrote:
>>>  > Sounds good. Also many things that are currently flagged as 2.3.0
>>> don't
>>>  > appear to be actual release blockers to me.
>>>  >
>>>  > On Tue, Jan 23, 2018 at 1:39 AM, Jean-Baptiste Onofré
>>> 
>>>  > >> wrote:
>>>  >
>>>  > Hi guys,
>>>  >
>>>  > Some days ago, I proposed to start Beam 2.3.0 around January
>>> 26th.
>>>  > So, we are
>>>  > few days from this date.
>>>  >
>>>  > As a best effort, can you please in Jira flag the Jira with
>>> fix
>>>  > version 2.3.0
>>>  > and blocker for the release. Then, I will know when I can
>>> start the
>>>  > release process.
>>>  >
>>>  > Thanks !
>>>  >
>>>  > Regards
>>>  > JB
>>>  > --
>>>  > Jean-Baptiste Onofré
>>>  > jbono...@apache.org 
>>> >
>>>  > http://blog.nanthrax.net
>>>  > Talend - http://www.talend.com
>>>  >
>>>  >
>>>
>>>
>

Re: [HEADS UP] Preparing Beam 2.3.0

[Alan Myrvold]

Are there improvements to the release process to make the triaging of open
issues easier?

I see 30 unresolved issues with fixVersion 2.3.0 in
https://issues.apache.org/jira/browse/BEAM-3160?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20Open%20AND%20fixVersion%20%3D%202.3.0%20ORDER%20BY%20updated%20DESC

The release process,
https://beam.apache.org/contribute/release-guide/#create-a-new-version-in-jira
indicates that all these issues will be moved to 2.4.0 if they are not
resolved.  Would it be better to unset the fixVersion for any issues that
aren't fixed instead of moving them to the next version?

On Tue, Jan 23, 2018 at 12:16 PM, Jean-Baptiste Onofré 
wrote:

> Awesome !
>
> Ready to review if you want !
>
> Regards
> JB
>
> On 23/01/2018 20:48, Eugene Kirpichov wrote:
>
>> Regarding Java 8, I'm about to send a large mechanical PR converting a
>> lot of code to use lambdas and better type inference.
>>
>> On Tue, Jan 23, 2018 at 11:37 AM Jean-Baptiste Onofré > > wrote:
>>
>> By the way, I would like to complete the Java 8 support (the subtasks
>> in
>> the main Java 8 Jira). So, let me try to move forward on this.
>>
>> Regards
>> JB
>>
>> On 23/01/2018 19:51, Reuven Lax wrote:
>>  > Sounds good. Also many things that are currently flagged as 2.3.0
>> don't
>>  > appear to be actual release blockers to me.
>>  >
>>  > On Tue, Jan 23, 2018 at 1:39 AM, Jean-Baptiste Onofré
>> 
>>  > >> wrote:
>>  >
>>  > Hi guys,
>>  >
>>  > Some days ago, I proposed to start Beam 2.3.0 around January
>> 26th.
>>  > So, we are
>>  > few days from this date.
>>  >
>>  > As a best effort, can you please in Jira flag the Jira with fix
>>  > version 2.3.0
>>  > and blocker for the release. Then, I will know when I can
>> start the
>>  > release process.
>>  >
>>  > Thanks !
>>  >
>>  > Regards
>>  > JB
>>  > --
>>  > Jean-Baptiste Onofré
>>  > jbono...@apache.org 
>> >
>>  > http://blog.nanthrax.net
>>  > Talend - http://www.talend.com
>>  >
>>  >
>>
>>

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Awesome !

Ready to review if you want !

Regards
JB

On 23/01/2018 20:48, Eugene Kirpichov wrote:
Regarding Java 8, I'm about to send a large mechanical PR converting a 
lot of code to use lambdas and better type inference.


On Tue, Jan 23, 2018 at 11:37 AM Jean-Baptiste Onofré > wrote:


By the way, I would like to complete the Java 8 support (the subtasks in
the main Java 8 Jira). So, let me try to move forward on this.

Regards
JB

On 23/01/2018 19:51, Reuven Lax wrote:
 > Sounds good. Also many things that are currently flagged as 2.3.0
don't
 > appear to be actual release blockers to me.
 >
 > On Tue, Jan 23, 2018 at 1:39 AM, Jean-Baptiste Onofré

 > >> wrote:
 >
 >     Hi guys,
 >
 >     Some days ago, I proposed to start Beam 2.3.0 around January
26th.
 >     So, we are
 >     few days from this date.
 >
 >     As a best effort, can you please in Jira flag the Jira with fix
 >     version 2.3.0
 >     and blocker for the release. Then, I will know when I can
start the
 >     release process.
 >
 >     Thanks !
 >
 >     Regards
 >     JB
 >     --
 >     Jean-Baptiste Onofré
 > jbono...@apache.org 
>
 > http://blog.nanthrax.net
 >     Talend - http://www.talend.com
 >
 >

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

By the way, I would like to complete the Java 8 support (the subtasks in 
the main Java 8 Jira). So, let me try to move forward on this.


Regards
JB

On 23/01/2018 19:51, Reuven Lax wrote:
Sounds good. Also many things that are currently flagged as 2.3.0 don't 
appear to be actual release blockers to me.


On Tue, Jan 23, 2018 at 1:39 AM, Jean-Baptiste Onofré > wrote:


Hi guys,

Some days ago, I proposed to start Beam 2.3.0 around January 26th.
So, we are
few days from this date.

As a best effort, can you please in Jira flag the Jira with fix
version 2.3.0
and blocker for the release. Then, I will know when I can start the
release process.

Thanks !

Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org 
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Jean-Baptiste Onofré]

Great !

I'm starting the Jira triage ;)

Thanks !
Regards
JB

On 23/01/2018 19:51, Reuven Lax wrote:
Sounds good. Also many things that are currently flagged as 2.3.0 don't 
appear to be actual release blockers to me.


On Tue, Jan 23, 2018 at 1:39 AM, Jean-Baptiste Onofré > wrote:


Hi guys,

Some days ago, I proposed to start Beam 2.3.0 around January 26th.
So, we are
few days from this date.

As a best effort, can you please in Jira flag the Jira with fix
version 2.3.0
and blocker for the release. Then, I will know when I can start the
release process.

Thanks !

Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org 
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [HEADS UP] Preparing Beam 2.3.0

[Reuven Lax]

Sounds good. Also many things that are currently flagged as 2.3.0 don't
appear to be actual release blockers to me.

On Tue, Jan 23, 2018 at 1:39 AM, Jean-Baptiste Onofré 
wrote:

> Hi guys,
>
> Some days ago, I proposed to start Beam 2.3.0 around January 26th. So, we
> are
> few days from this date.
>
> As a best effort, can you please in Jira flag the Jira with fix version
> 2.3.0
> and blocker for the release. Then, I will know when I can start the
> release process.
>
> Thanks !
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>