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é <[email protected]> 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é > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
