Nutmeg

Note: the Nutmeg master branches were created on April 11th. Code on master/main will now be part of Olive. Note your changes there.

If you have a fix for Nutmeg, make a pull request against open-release/nutmeg.master

 

 

 

 

 

 

The 14th Open edX community release will be named Nutmeg. It will be released June 9th, 2022. The open-release/nutmeg.master branches will be created two months earlier, on April 11th. Code on master as of April 11th will be part of Nutmeg. Code merged after that will need special handling to be part of Nutmeg.

Put stuff here that we have to remember when we start packaging up Nutmeg.  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.

Operational

Feature Changes

  • The Dates Tab has been added as a default static tab on all courses, meaning it is stored as part of the course object in Mongo. Previously it was inserted as a dynamic tab at runtime. All new courses will automatically include the Dates Tab. In order to properly have the Dates Tab show up for all your existing courses, a backfill course tabs management command has been created. Run this command on your instance to properly update your default tabs on all of your existing courses. @Dillon Dumesnil (Deactivated)

    • To run the command, run ./manage.py cms backfill_course_tabs or python manage.py cms backfill_course_tabs from your shell.

  • An internal performance improvement called “learning sequences” has been opt-in for a few releases, but is now always-on for Nutmeg. If you have any courses that have not been re-published on Koa or later, run the simulate_publish cms django command on your courses before upgrading, to populate the learning sequence data. @Michael Terry (Deactivated)

Added Features:

CLOSEST_CLIENT_IP_FROM_HEADERS

  • New config value that all deployments should set: CLOSEST_CLIENT_IP_FROM_HEADERS in edx-platform @Tim McCormack

    • This is a security-impacting setting that tells your deployment how to determine the IP address of the client. See openedx.core.djangoapps.util.ip for documentation on how (and why) to configure this (as well as the related NUM_PROXIES setting for django-rest-framework).

    • Breaking change: Failing to set this can result in rate-limiting legitimate traffic or failing to block brute-force attacks, depending on your proxy setup.

Deprecations and Removals

Based on estimated dates 2021-10-15 to 2022-04-11.

Deprecations

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh