I also agree that the release should be done using Gradle otherwise we won't have the opportunity to migrate off of Maven for several more weeks till 2.6.0 is released. Several people have pointed out that supporting multiple build systems is a hassle which is what inspired putting more effort into the migration effort.
On Mon, Apr 30, 2018 at 5:05 PM Scott Wegner <[email protected]> wrote: > Welcome back JB! > > I just sent a separate update about Gradle [1]-- the build migration is > complete and the release documentation has been updated. > > I recommend we produce the 2.5.0 release using Gradle. Having a successful > release should be the final validation before declaring the Gradle > migration complete. So the sooner we can have a Gradle release, the sooner > we can get back to a single build system :) > > If it would be helpful, I suggest that somebody who's been working on the > Gradle migration to manage the 2.5.0 release. That way if we encounter any > issues from the build system, they should have sufficient expertise to fix > it. > > [1] > https://lists.apache.org/thread.html/e543b3850bfc4950d57bc18624e1d4131324c6cf691fd10034947cad@%3Cdev.beam.apache.org%3E > > > On Mon, Apr 30, 2018 at 11:38 AM Romain Manni-Bucau <[email protected]> > wrote: > >> >> >> Le 30 avr. 2018 19:39, "Jean-Baptiste Onofré" <[email protected]> a écrit : >> >> Hi guys, >> >> now that I'm back from vacations, I bring back 2.5.0 release on the table >> ;) >> >> This is also related to the current status of build (Maven/Gradle). >> >> FYI, I gonna start the Jira triage tomorrow and I launched couple of >> build on my >> machine (both Maven and Gradle) to get an update on the current status. >> >> Please, let me know if you have an opinion about Gradle vs Maven for the >> release. >> >> >> Produced artifacts are still too different to use gradle IMHO. Jira were >> created but not yet fixed last time i tried gradle so clearly maven IMHO. >> >> >> Thanks ! >> 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] >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> >> >> -- > > > Got feedback? http://go/swegner-feedback >
