Versions Compared

Old Version 31

changes.mady.by.user Kyle McCormick

Saved on

compared with

New Version 32

changes.mady.by.user Kyle McCormick

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Move note about "helping with the release" to the playbooks page

...

  • Respond to GitHub Requests within one business day.

    • Requests should automatically ping the @openedx/tcril-oncall GitHub group.

    • Assign yourself to the issue.

    • If you can’t resolve the request within a day, that is fine. Just give an “Ack” and a general timeline estimate.

    • Please note that users must also be added to the CLA check database. The specifics are in the document linked above.

  • By the end of the sprint, ensure each GitHub Request is either:

    • closed, or

    • explicitly reviewed & handed off to the next on-call engineer at the beginning of the following sprint.

  • Be available to the Open edX Release Manager in order to help with GitHub administrivia during the release cutting and tagging processes. You may be asked to grant/revoke permissions, merge PRs, and occasionally jump into release-related meetings; however, you shouldn’t need to take on any release-related responsibilities beyond that.

  • Respond to other pings to the @openedx/tcril-oncall group if they happen.

  • Keep an eye on the #ask-tcril Slack channel. If tCRIL-oriented questions come up that nobody is responding to, bring them up in daily standup so we don’t forget about them.

...