Hi Reuven, that was on of the question. I proposed to stay with Maven for 2.5.0 and switch to Gradle to 2.6.0 (in order for us to stabilize gradle build). But, it may worth to try 2.5.0 with Gradle.
Regards JB On 04/09/2018 02:27 PM, Reuven Lax wrote: > To the folks working on Gradle last week - are we at the point where we can > try > running this release purely using Gradle, or should we wait until 2.6.0? > > Reuven > > On Mon, Apr 9, 2018 at 8:01 AM Jean-Baptiste Onofré <[email protected] > <mailto:[email protected]>> wrote: > > Up ? > > Regards > JB > > On 04/06/2018 10:48 AM, Jean-Baptiste Onofré wrote: > > Hi guys, > > > > Apache Beam 2.4.0 has been released on March 20th. > > > > According to our cycle of release (roughly 6 weeks), we should think > about > 2.5.0. > > > > I'm volunteer to tackle this release. > > > > I'm proposing the following items: > > > > 1. We start the Jira triage now, up to Tuesday > > 2. I would like to cut the release on Tuesday night (Europe time) > > 2bis. I think it's wiser to still use Maven for this release. Do you > think we > > will be ready to try a release with Gradle ? > > > > After this release, I would like a discussion about: > > 1. Gradle release (if we release 2.5.0 with Maven) > > 2. Isolate release cycle per Beam part. I think it would be interesting > to > have > > different release cycle: SDKs, DSLs, Runners, IOs. That's another > discussion, I > > will start a thread about that. > > > > Thoughts ? > > > > Regards > > JB > > > > -- > Jean-Baptiste Onofré > [email protected] <mailto:[email protected]> > http://blog.nanthrax.net > Talend - http://www.talend.com > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
