Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Sprint 114 FE On-call duty #16934

Open
5 tasks
chris-kuryak opened this issue Dec 31, 2024 · 0 comments
Open
5 tasks

Sprint 114 FE On-call duty #16934

chris-kuryak opened this issue Dec 31, 2024 · 0 comments
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team

Comments

@chris-kuryak
Copy link
Collaborator

Responsibilities and Acceptance Criteria for this sprint

One engineer per sprint is assigned on-call duty. It is that engineer's responsibility to know the "pulse" of FE issues/health during the sprint. This includes the following responsibilities:

  • Front-end checks (after deployment)
  • Primary point-of-contact for any FE problems that occur during the sprint (including status of those issues)
  • Resolve all security (high-priority) Dependabots
  • Try to tackle other Dependabot issues while still accomplishing your sprint commitments
  • Small content updates (if they exist)
@chris-kuryak chris-kuryak added engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team labels Dec 31, 2024
@chris-kuryak chris-kuryak changed the title Copy of Sprint 111 FE On-call duty Sprint 114 FE On-call duty Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chris-kuryak