Page Comparison

...

- Trigger the job which pulls the translation and creates PRs (i.e. PR for fronted-app-learning: https://github.com/openedx/frontend-app-learning/pull/973 , PR for edx-platform: https://github.com/openedx/edx-platform/pull/31039 )
- If the PRs are not merged at the time (this is expected hence the above note), leave a note about them so that we can backport the commit at a later time.

Why we need to this: The point of doing this is that we ensure the shortest lag possible between the last time a translator review/translate string and the branch cut date. i.e. If the syncing happens on a weekly basis and we do the branch cut just a day before the scheduled weekly sync , then we would in theory lose 6 days of translation work.

2b. Freeze edx-sandbox for the release

Starting with Quince, we need to freeze the Python dependency pins for the edx-platform codejail sandbox environment (also known as “edx-sandbox”). This allows operators to smoothly upgrade their instructor-authored code from release to release. The file needs to exist both in the release and on master, so this step needs to be done before the release cut.

To do this:

• copy ./requirements/edx-sandbox/base.txt to a new file named ./requirements/edx-sandbox/releases/<RELEASE.txt>

• git-add the new file and open a pull request against edx-platform master

• tag someone for review and merge it before cutting the release.

That’s it! Here’s an example: https://github.com/openedx/edx-platform/commit/8eb9ee7b5c758351fe197a203f82c1141e127f61 .

2c. Testing before creating release branches

If you want to try a dry-run of the release before making any release branches, make a branch under your personal name. Don't use the full release name in the branch name, or people will think it's a release.  Follow the instructions for "Create the release branches", but use "yourname/test-z.1" instead of "open-release/zebrawood.master", for example:

$ tag_release --doit --skip-repo "*-internal" --branch yourname/test-z.1

...

2d. Create the release branches

The repo-tools repo has a script, tag_release.py, to branch and tag the proper repos.  The repos are indicated by an "openedx-release" entry in their openedx.yaml file.  Releases before Ficus would mark dependent repos (those installed by other repos, such as XBlock being installed by edx-platform).  We no longer branch or tag dependent repos.

...