Hi, I did some tests on the maven artifacts produced by the gradle build: I published maven artifacts to local maven repo using : ./gradlew publishToMavenLocal -PisRelease --no-parallel -x test then used beam samples project (maven based) and did a mvn dependency:tree => transitive dependencies of all beam related artifacts are well resolved
Le jeudi 31 mai 2018 à 14:43 +0200, Jean-Baptiste Onofré a écrit : > Agree, I gonna start the release process tonight (my time). > > > Regards > > JB > > Le 31 mai 2018, à 14:29, Kenneth Knowles <[email protected]> a écrit: > > Yea - the branch should be cut before trying to finish the burndown. > > Kenn > > On Thu, May 31, 2018 at 2:09 AM Robert Bradshaw <[email protected]> wrote: > > > I think it makes sense to cut the release and get the ball rolling, and > > > iff the ParquetIO/S3 issue turns out to be > > > simple, we cherry-pick, otherwise we add a note. > > > On Thu, May 31, 2018 at 1:56 AM Jean-Baptiste Onofré <[email protected]> > > > wrote: > > > > Hi, > > > > > > > > > > > > > > > > Regarding RabbitMqIO, Eugene provided new feedback last night that I > > > > > > > > would like to implement. However, it's not a release blocker, so I will > > > > > > > > move forward with 2.5.0 release without RabbitMqIO (I will include in > > > > > > > > 2.6.0). > > > > > > > > > > > > > > > > Regarding ParquetIO, I tested HDFS successfully as well (I had an issue > > > > > > > > on my namenode). S3 is important, but I think we can just add a note in > > > > > > > > the RELEASE NOTE and move forward with 2.5.0. Thoughts ? > > > > > > > > > > > > > > > > So, please, let me know if I can start the release process today (I > > > > > > > > would like to move forward asap). > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Regards > > > > > > > > JB > > > > > > > >
