-
Notifications
You must be signed in to change notification settings - Fork 443
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
Redwood sandbox preparation #1054
Comments
@ghassanmas Hi, can you take care of tutor-forum branch/PR? |
@DawoudSheraz |
Tutor Indigo PR: overhangio/tutor-indigo#79
|
Thanks. Are builds and init working as expected? |
Yes |
Tutor MFE:
|
@DawoudSheraz I'm not able to see https://edlyio.atlassian.net/wiki/spaces/openedx/pages/3013148726/Building+Open+edX+major+releases. I already sent an access request from my account. You can copy-paste the info here if you prefer. I've checked the already existing PRs so I think I can start, anyways I'll check your document once is ready |
@jfavellar90 I have updated the issue's description. It's more or less similar to what you already did in the PRs. Thanks |
Hi @DawoudSheraz, I'm working on the codjail plugin. I tested against the latest nightly. One thing to keep in mind Is that the openedx image must include this commit if running (openedx/edx-platform@351e360) on open-relelease/redwood.master or (openedx/edx-platform@8ff52ce) if running on master. Tutor contrib codejail: eduNEXT/tutor-contrib-codejail#54
|
PR for tutor-webui
|
PR for tutor credentials.
Thanks @Danyal-Faheem, for your collaboration and thorough testing of this plugin. Much appreciated! |
Apart from Android & Cairn(disabled in favor of aspects), the rest of the plugins are active and enabled. Closing this issue. |
This issue is for tracking the items to prepare https://github.com/overhangio/openedx-release-demo for Redwood cutoff.
Redwood branches are expected to be available on May 9th. Once the branches are out, the community will be eagerly looking forward to sandbox provided by Edly to test out redwood cutoff. But before the sandbox can be built, tutor and its plugins need to have
redwood
branches with appropriate changes. The necessary information is already present on https://edlyio.atlassian.net/wiki/spaces/openedx/pages/3013148726/Building+Open+edX+major+releases. A note: once the branches are created, any changes to nightly would need to be manually added to the redwood branch. Therefore, a rebase on nightly whenever nightly changes would be required to ensure the redwood branch is always up-to-dateThis issue is just a todo list to ensure that tutor and its plugins have redwood branches created from nightly before the cutoff date (even though there will be potential failures on CI against it) and have a PR against master. For sanity checks, make sure to run image build and init task on local
tutor <local/dev> do init --limit=pluginnname
. Additionally, the sandbox repo https://github.com/overhangio/openedx-release-demo would also need updates to build on redwood.Tutor & Plugins Todo List
Available on launch
Available within a week
Delay expected
Sandbox Repo Todo List
Context
Every six months, Tutor maintainers sync up with the Build/Test/Release working group to create the next version, both of Open edX and Tutor.
In the scenario below, we are upgrading Open edX from fictional “Delta” to “Epsilon”. Tutor will upgrade from v4 to v5 (“d”=4, “e”=5).
(these instructions are pulled and adapted from this old discussion topic)
Create release branches
In Tutor core and all plugins, we must create “epsilon” branches off of the nightly branches. For each repo, this looks like the following:
Upgrade Tutor core and plugins
The release branches should be updated regularly to take into account the latest changes from the nightly branch. During the release process, it is frequent that changes are pushed to the master and nightly branches, and the latest “espilon” branch must have those changes as well. Be prepared to push --force the “espsilon” branches frequently.
The text was updated successfully, but these errors were encountered: