> > Also I'm blocked on verifying the python/ruby code due to the pip/gem > packages not yet having been pushed. Is there an ETA for those?
The issue here is that none of the “currently active” Avro committers have access to the repositories for those. We’ve asked to have our accounts added to the Avro “groups” on those repositories, but that hasn’t happened yet. We need for some of the Avro old timers that do have access to either do the push or grant us access so we can do the push. We’re working on it, just trying to get ahold of them. Dan > > Patrick > > On Thu, May 16, 2019 at 7:43 AM Ismaël Mejía <[email protected]> wrote: > >> This is a fork of the discussion started in the release vote thread [1]. >> >> Just to keep the discussion going and follow up on issues and projects >> that deserve attention. >> So far open issues are: >> >> BEAM-7328 Update Avro to version 1.9.0 in Java SDK >> HIVE-21737 Upgrade Avro to version 1.9.0 >> FLINK-12532 Upgrade Avro to version 1.9.0 >> PARQUET-1576 Upgrade to Avro 1.9.0 >> SPARK-27733 Upgrade to Avro 1.9.x >> >> Don't hesitate to create new issues if required and bring info in this >> thread that could be useful for others working on this. >> >> [1] >> https://lists.apache.org/thread.html/ab598c36fd823a3fc563f7c621f957f0c2ef09513d4e8428391ddb69@%3Cdev.avro.apache.org%3E >> -- Daniel Kulp [email protected] <mailto:[email protected]> - http://dankulp.com/blog <http://dankulp.com/blog> Talend Community Coder - http://talend.com <http://coders.talend.com/>
