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
