Thanks everyone for making comments and suggestions. I modified the proposal that added dependency release time as the major criteria for outdated package determination. The revised doc is here: https://docs.google.com/document/d/1rqr_8a9NYZCgeiXpTIwWLCL7X8amPAVfRXsO72BpBwA. Any comments are welcome.
-Yifan On Thu, May 24, 2018 at 5:25 PM Chamikara Jayalath <[email protected]> wrote: > Thanks Yifan. Added some comments. I think having regularly generated > human reports on outdated decencies of Beam SDKs will be extremely helpful > in keeping Beam in a healthy state. > > - Cham > > On Thu, May 24, 2018 at 7:08 AM Yifan Zou <[email protected]> wrote: > >> Hello, >> >> I have a proposal to automate Beam dependency check. Since some Beam >> dependent packages are out-of-date, we want to identify them and check for >> dependency updates regularly in the future. Generally, we have couple >> options to do it: >> 1. Implementing a Jenkins job that check dependency versions and >> create reports. >> 2. Using the Github App Dependabot >> <https://github.com/marketplace/dependabot> to automate dependency >> updates. >> 3. Combination of those two solutions. >> >> I am looking forward to hearing feedback from you :) >> >> >> https://docs.google.com/document/d/1rqr_8a9NYZCgeiXpTIwWLCL7X8amPAVfRXsO72BpBwA/ >> >> Thanks. >> >> Best. >> Yifan Zou >> >
