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 tickets of Beam deps in order to track the upgrade process.
Thank you. Regards. Yifan On Mon, Jul 9, 2018 at 10:24 AM Yifan Zou <yifan...@google.com> wrote: > If you haven't already, please take a look at the Beam SDK Dependency > Ownership > <https://docs.google.com/spreadsheets/d/12NN3vPqFTBQtXBc0fg4sFIb9c_mgst0IDePB_0Ui8kE/edit?ts=5b32bec1#gid=0>and > sign up with any dependencies that you are familiar with. In case anyone > miss, there is a second tab for the Python SDK. > > Thanks. > > Yifan > > On Thu, Jun 28, 2018 at 6:37 AM Tim Robertson <timrobertson...@gmail.com> > wrote: > >> 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 <echauc...@apache.org> >> wrote: >> >>> 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 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 >>> declarations instead of maintaining the spreadsheet (after we collect the >>> data). Otherwise we'll have to put an extra effort to make sure that the >>> spreadsheet, BeamModulePlugin, and Python setup.py are in sync. We can >>> decide on the exact format of the comment to make sure that automated tool >>> can easily parse the comment. >>> >>> - Cham >>> >>> On Wed, Jun 27, 2018 at 1:45 PM Yifan Zou <yifan...@google.com> wrote: >>> >>> 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 >>> <https://beam.apache.org/contribute/dependencies/>, @Chamikara Jayalath >>> <chamik...@google.com>? >>> >>> On Wed, Jun 27, 2018 at 11:17 AM Scott Wegner <sc...@apache.org> wrote: >>> >>> Thanks for kicking off this process Yifan-- I'll add my name to some >>> dependencies I'm familiar with. >>> >>> Do you expect this to be a one-time process, or will we maintain the >>> owners over time? If we will maintain this list, it would be easier to keep >>> it up-to-date if it was closer to the code. i.e. perhaps each dependency >>> registration in the Gradle BeamModulePlugin [1] should include a list of >>> owners. >>> >>> [1] >>> https://github.com/apache/beam/blob/master/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L325 >>> >>> On Wed, Jun 27, 2018 at 8:52 AM Yifan Zou <yifan...@google.com> wrote: >>> >>> 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 >>> if actions need to be taken. We also welcome non-owners to upgrade >>> dependency packages, but only owners will receive the Jira tickets. >>> >>> Please review the spreadsheet Beam SDK Dependency Ownership >>> <https://docs.google.com/spreadsheets/d/12NN3vPqFTBQtXBc0fg4sFIb9c_mgst0IDePB_0Ui8kE/edit?ts=5b32bec1#gid=0> >>> and >>> sign off if you are familiar with any Beam dependencies and willing to >>> take in charge of them. It is definitely fine that a single package have >>> multiple owners. The more owners we have, the more helps we will get to >>> keep Beam dependencies in a healthy state. >>> >>> Thank you :) >>> >>> Regards. >>> Yifan >>> >>> >>> https://docs.google.com/spreadsheets/d/12NN3vPqFTBQtXBc0fg4sFIb9c_mgst0IDePB_0Ui8kE/edit?ts=5b32bec1#gid=0 >>> >>> >>
