-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependa-duty #9920
Comments
At least half of the existing dependabot PRs have been closed! Hooray! I created a new label " I'm hoping we can continue merging more dependabot PRs in the next few sprints to keep them at the manageable number. I don't mind taking on this task for the next sprint if other devs have other priorities. :) |
@mmmavis Thanks for this! We'll keep this open until we're caught up, you all can decide who will carry this forward in the next sprint. |
Hey @danielfmiranda can you give us an update as of where we are with dependabot issues? The above comment from Mavis is a perfect example :)
|
Hi @cdanfon! No problem, for my update:
Thanks! |
We're skipping this duty during s/c 6th March |
For next round, we should focus on security critical updates: https://github.com/MozillaFoundation/foundation.mozilla.org/security/dependabot |
Sprint July 24, 2023 - August 4, 2023:
|
Pausing this for 8/7 sprint |
Sprint October 16th, 2023 -October 27th, 2023: |
Sprint November 27th, 2023 - December 8th, 2023: |
Sprint December 11th, 2023 - December 22nd, 2023: |
Sprint January 22nd, 2024 - February 2nd, 2024: |
➤ Ramon Ramos commented: Sprint June 11, 2024 - June 25, 2024:
|
➤ diego commented: Sprint Agust 6, 2024 - Agust 20, 2024
|
[Timebox to 4 hours]
GOAL: Spend the timeboxed amount of time per sprint addressing Dependencies
Process for Github Dependabot Duty
Please use the process outlined in this document, Github: Dependabot Duty when you are assigned to this task.
Reach out to the team in Slack if you need access to the referenced document.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: