Re: Beam Dependency Ownership

Thanks all for taking the ownership of Beam dependencies! This is an import step to keep our dependencies healthy and up-to-date. We will close this thread now. The next step would be integrating the ownership information into the Beam codebase and implementing a tool to create and manage the JIRA

Re: Beam Dependency Ownership

If you haven't already, please take a look at the Beam SDK Dependency Ownership and sign up with any dependencies that you are familiar with. In case anyone miss, there is a second tab for

Re: Beam Dependency Ownership

Thanks for this Yifan, I've added my name to all Hadoop related dependencies, solr, along with es. On Thu, Jun 28, 2018 at 3:28 PM, Etienne Chauchot wrote: > I've added myself and @Tim Robertson on elasticsearchIO related deps. > > Etienne > > Le mercredi 27 juin 2018 à 14:05 -0700, Chamikara

Re: Beam Dependency Ownership

I've added myself and @Tim Robertson on elasticsearchIO related deps. Etienne Le mercredi 27 juin 2018 à 14:05 -0700, Chamikara Jayalath a écrit : > It's mentioned under "Dependency declarations may identify owners that are > responsible for upgrading respective > dependencies". Feel free to

Re: Beam Dependency Ownership

It's mentioned under "Dependency declarations may identify owners that are responsible for upgrading respective dependencies". Feel free to update if you think more details should be added to it. I think it'll be easier if we transfer data in spreadsheet to comments close to dependency

Re: Beam Dependency Ownership

Thanks Scott, I will supplement the missing packages to the spreadsheet. And, we expect this being kept up to date along with the Beam project growth. Shall we mention this in the Dependency Guide page , @Chamikara Jayalath ? On Wed, Jun 27, 2018

Re: Beam Dependency Ownership

Thanks Yifan. I added myself to some of the dependencies I'm involved with upgrading. In case anyone miss, there's a second tab for Python SDK :). On Wed, Jun 27, 2018 at 11:17 AM Scott Wegner wrote: > Thanks for kicking off this process Yifan-- I'll add my name to some > dependencies I'm

Beam Dependency Ownership

Hi all, We now have the automated detections for Beam dependency updates and sending a weekly report to dev mailing list. In order to address the updates in time, we want to find owners for all dependencies of Beam, and finally, Jira bugs will be automatically created and assigned to the owners