If you have a fix for Olive, make a pull request against open-release/olive.master
The 15th Open edX community release will be named Olive. It will be released December 9th, 2022. The open-release/olive.master branches will be created two months earlier, on October 10th. Code on master/main as of October 10th will be part of Olive. Code merged after that will need special handling to be part of Olive.
Put stuff here that we have to remember when we start packaging up Olive. Especially important is information that system installers or operators will need to know. Please include your name when you add an item, so that we can get back to you with questions.
The Learning MFE is no longer optional, and must be run it as part of your installation now. It has been the default for a couple releases with an opt-out, but that opt-out has been removed (see Deprecations & Removals below for more).
[@TJ Tracy (Deactivated) & @Kelly Buchanan ] The Learner records MFE is now available as an optional frontend for Credentials
Currently, the implementation of public records is not fully tested, and the old UI is used for public links to records on edx.org. Known Bugs:
By default, all grades will now be persisted in the database. This will be a change from the previous default behavior, where grades were not persisted. This should be a performance improvement for installations that did not previously have this flag on.
The platform had a bad response time due to the file I/O when it's running in docker the more themes you added to your platform the slower the reponse. Now by using LRU cache when searching themes, the performance was improved.
Deprecations and Removals
Based on estimated dates 2022-04-11 to 2022-10-10.
A few pieces of the legacy/deprecated learner experience have been removed entirely in favor of the MFE experience. Specifically, the outline, dates, and courseware tabs. Instead, you must run the Learning MFE and its tabs will be used. Along with the legacy code, a few old waffle flags have been removed: course_experience.latest_update, course_experience.show_upgrade_msg_on_course_home, course_experience.upgrade_deadline_message, course_home.course_home_use_legacy_frontend, courseware.microfrontend_course_team_preview, and courseware.use_legacy_frontend@Michael Terry (Deactivated)
As a consequence of this change, we read the enterprise_catalog_api_url from site configuration so ensure that this setting is set for any site that loads enterprise catalog data. This setting is just a passthrough for settings.ENTERPRISE_CATALOG_API_URL which should be loaded into your django settings, however you load that.