derrickaw opened a new pull request, #41428:
URL: https://github.com/apache/beam/pull/41428

   Problem: Currently, dependencies are upgraded once every release cycle at 
the beginning and give 5ish weeks to soak before next release cut. Since 
vulnerabilities are being attacked more and faster, this seems excessive to 
wait 6 weeks to get in another update.
   Goal: 
   1. Propose going to two updates per cycle for now, which will allow 3ish 
weeks to soak. Maybe in the future we should consider going to 3 per cycle or 
every 2 weeks.
   2. So allow the update to happen in weeks 1 and 3.
   3. Also, move the check up higher in the workflow so compute is not wasted 4 
out of the 6 weeks.
   
   <!--
   
   Thank you for your contribution! Follow this checklist to help us 
incorporate your contribution quickly and easily:
   
    - [ ] If this contribution is large, please file an Apache [Individual 
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
    - [ ] Replace these instructions with a description of your change and why 
you have made it.
    - [ ] Mention the appropriate issue in your description (for example: 
`addresses #123` or `fixes #456`).
    - [ ] Update `CHANGES.md` with noteworthy changes.
   
   See [CONTRIBUTING.md]() for more details.
   
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to