The Django 2.2 upgrade work is nearing completion. edX engineers are working on deploying updated code to edx.org production this week. This means we could start Juniper master branches very soon.
The known Juniper issues are in Jira here: [CRI-171] Open edX release: Juniper.
You can help get Juniper done, and done well, by doing some of these things:
- Reproduce issues, and write up exactly how you did it. This will save other people time.
- Fix problems. Even if you just have clues, and not a complete solution, it’s helpful to provide the information.
- Write new issues. If you find something wrong with Juniper, write a ticket.
- Collate information between Discourse and Jira. We have information in both places. If we can make Jira authoritative, it will reduce confusion. Discourse is good for when discussion is needed, but crisp descriptions of the problem should end up in Jira.
Thanks in advance for your help. It’s great to see the community pull together to produce the community release!
BTW, I wrote an FAQ about the Open edX releases, let me know if there are things to add.