Quince will be released on December 11th, 2023. It will be the 17th Open edX community release.
Put stuff here that we have to remember when we start packaging up Quince. 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.
Quince will be based on branches cut two months earlier on Oct 9th, 2023. Changes made after that date will be part of the next release (Redwood) unless you also backport them to Quince.
Please add any new changes to Next Release: Redwood
Information Radiators 💡
Risk Management 🚨
Which MFEs will be included?
Are the experimental MFEs in Palm going to be officially added in Quince as either optional or mandatory MFEs?
There will be a required effort that could go from a couple of hours to 1-2 days.
October 9 is a holiday in the US
OEP-58: Heads up
Aspects test cases?
Work Plan 📅
Week | From | To | Task | Assignee |
|---|---|---|---|---|
38 | September 18 | September 24 | Confirming working group roles:
| |
39 | September 25 | October 1 | Backlog refinement guidelines | |
40 | October 2 | October 8 | Testing plan announcement
| |
41 | October 9 | October 15 | Branches cut | |
Testing start | ||||
50 | December 11 | December 17 | quince.1 release | |
Quince release retrospective |
Operational ⚙️
[Tim McCormack] Deployers must ensure that for all of their IDAs, any
JWT_PUBLIC_SIGNING_JWK_SETDjango setting does not contain whitespace inside of the Base64 strings of the encoded keys.This is related to edx-drf-extensions now using PyJWT instead of pyjwkest, which is overly permissive of spaces inside Base64. 2U discovered that several of their IDA configurations had a
JWT_PUBLIC_SIGNING_JWK_SETsetting that inadvertently contained whitespace inside the large Base64 strings. Before upgrading to Quince, ensure that there are no linebreaks or other whitespace inside Base64 strings in the JWT key settings. Otherwise, IDAs will produce 'Incorrect padding' errors.For example broken/working configs see the edx-drf-extensions changelog for version 8.8.0; issue 346 has more detailed technical information.
[Awais Qureshi] Django-storages upgraded to latest version and it has some breaking changes.
The constructor
kwargbucketis no longer accepted. Instead, usebucket_name.define
default_aclvalue explicitly in constructor kwarg e.gdefault_acl: public-read. in previous versionsdjango-storagesprovides default value aspublic-readbut now it is none. So it's important to mention it explicitly as per your use case.
[Awais Qureshi] For Django 4.2
CSRF_TRUSTED_ORIGINSmust include scheme. Update all urls there with schemes. e.g.edx.orgchanges tohttps://*.edx.org.
Deprecations and Removals ✖️
Based on estimated dates 2023-04-11 to 2023-10-01.
[Farhan] We have deprecated and migrated the openedx/xblock-utils library into openedx/XBlock. See https://github.com/openedx/XBlock/issues/675 .
Most functionality has been removed from the long-deprecated Old Mongo Modulestore. This was the old system for storing and accessing course content, used by courses with
Org/Course/Runstyle identifiers, e.g.MITx/6.002x/2012_Fall. All end-user access to this course content was removed with the Nutmeg release, so any course actively being run in the Nutmeg release or later should be unaffected.To preserve compatibility with old installations, some limited Old Mongo functionality remains:
Files that were uploaded to these old courses (e.g. images, PDFs) will remain accessible. This is partly to preserve older certificates which relied on downloading assets from their originating course.
The metadata stored at the root CourseBlock is still accessible in a read-only way. This includes things like the course title, start and end dates, and various settings.
For more details, please seehttps://github.com/openedx/public-engineering/issues/62
Other deprecations: