The Build/Test/Release working group is currently brainstorming to produce a medium- to long-term vision. What do we want to achieve in the next six months in terms of Open edX releases? Dream big! I’ll start with my own Christmas list :spiral_notepad: :gift: An Open edX platform running on a mode…

I would love to see: Continuous integration testing for whatever installation method we are supporting. An active and engaged BTR working group. An explicit process for tracking what has changed in the code.

I would love to see: Easy integration of MFE in whatever installation method we are supporting

[image] sambapete: Easy integration of MFE in whatever installation method we are supporting Yes! @Felipe has started writing up some ideas: Deploying MFEs in the community . Please provide feedback or help. Let’s get this done.

Regarding some of the items on Regis’s wishlist: We’re currently finishing the process of switching essentially all of the services over to Python 3.8, this should be done before the Python 3.5 EOL on September 13th. With the Python 3.8 upgrade almost done, we’ve started working on Django 3.0 comp…

That sounds exciting! Thanks for sharing these details @jmbowman . :slight_smile:

Thanks for these great news @jmbowman . I can’t help but think that it would be amazing to have such a page where all Open edX developers publish what they are working on. That would tick item :gift_heart: on my wishlist.

:wave:t4: Note that the internal target date for edX teams to complete the Ubuntu and MySQL upgrades is mid-November. So those may not make it into Koa - if the plan is Nov 9th for the Koa master branch cut . (Not being a Grinch - but the elder sibling telling you what’s real. :wink:)

[image] nimisha: :wave:t4: Note that the internal target date for edX teams to complete the Ubuntu and MySQL upgrades is mid-November. So those may not make it into Koa - if the plan is Nov 9th for the Koa master branch cut . In that case we would have to postpone Koa, as Lilac would come out …

I am confident that edX and the community will pull together to make disciplined six-month releases of secure software a reality.

We’re currently finishing the process of switching essentially all of the services over to Python 3.8, this should be done before the Python 3.5 EOL on September 13th. @jmbowman do you have an update on this?

What would you like to see under this year's Open edX Christmas tree?🎄

Working Groups Build-Test-Release

nedbat (Ned Batchelder) August 5, 2020, 10:29am 5

Yes! @Felipe has started writing up some ideas: Deploying MFEs in the community. Please provide feedback or help. Let’s get this done.

Topic		Replies	Views
Latest thoughts about when Juniper will happen Releases juniper	12	2562	October 24, 2019
Is it mandatory to have the python version 3.8 for this Open edX project? Site Operations Help	1	445	July 5, 2022
Juniper is here! Releases juniper	4	2221	June 15, 2020
Koa is now ready!‌ Releases	1	1445	December 10, 2020
How to keep old releases installable? Site Operators	32	3386	August 28, 2020

What would you like to see under this year's Open edX Christmas tree?🎄

Related topics