The next Open edX release will be called Juniper. We want it to include the work currently ongoing to port our Python code to Python 3, since Python 2 reaches end-of-life in early 2020. Another major upgrade will be happening right after the Python 3 work: the move from Django 1.11 to Django 2.2, since Django 1.x goes out of support by April 2020.
The Python 3 work will likely not be stable for another month, which is why we haven’t started the Juniper work yet. The Django upgrade is more important, since Django does have an active stream of security fixes. Python 3 is needed before Django can be upgraded.
Our latest thought for Juniper is to wait until the Python 3 work is stabilized, then mark a Juniper alpha release. Our estimate now is that this would happen in early December. Then, once the Django 2.2 upgrade is done, we would have the official start of Juniper with a Juniper release candidate. That would likely happen in the March timeframe.
This means that Juniper happens significantly later than our ideal six-month schedule would dictate. But we wanted to get the much-needed upgrades in your hands as soon as they are ready.
Any thoughts or concerns about this plan?