Hi guys, new update on the 2.5.0 release preparation.
I tested the artifacts published by gradle (using gradlew publishToLocalMaven) in "my" beam-samples (which still use the mvn).
Unfortuntaly beam-samples project doesn't build as some artifacts seem to miss in the local repository. I'm also checking the generated maven coordinates generated (metadata, etc), and I'm not sure they are complete.
On the other hand, I have build failure using gradle on python SDK (I think it's an environment issue due to the update to Ubuntu 18.04, I'm checking the python version, lint, ...) and go SDK (investigating).
So, I need more time to completely review artifacts and build. I keep you posted. Regards JB On 06/04/2018 10:48, 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
