7.5-10 minutes

A github action to automate backporting process

Ghassan Maslamani

• For every new release or new tag, we typically have few PRs/commits to be back ported, this process can be time consuming, however there exists a few GitHub actions that do that: ref: https://github.com/marketplace?type=&verification=&query=cherry-pick

  • Assuming we agree a GitHub action makes sense to automate the process then we also need to make decision about

    • What is the next steps? (action)

    • Can any of the above already be used? or should we build our own from scratch, given some of them an appointed

    • Should the action open a PR or commit directly to the release branch? or should it be flexible to support two scenarios.

    • Is this something Axim need to be in loop about?

  • This was discussed in latest 24-04-2023 DevEnv meeting and it was suggested that it better match BTR scope

5 minutes

Should we make olive.4 release

Ghassan Maslamani

Reason to make it

• Google Analytics feature back port suggested by Brian Mesick backport PR https://github.com/openedx/edx-platform/pull/32106

• Security update for Django suggested by Ned Batchelder (Deactivated)

• Missed backport from olive.3 https://github.com/openedx/wg-build-test-release/issues/253

5 minutes

Release notes PR started

Peter Pinch

just started, at https://github.com/openedx/docs.openedx.org/pull/321

• I’m not a core committer on docs.edx.org. Should I nominate myself?