Page Comparison

Teak Maintenance Goals

• Focus on Django upgrade for the next 2 releases.

Next time: Andrés González would like to bring into the agenda the topic of how many releases back are we keeping under maintenance. We, as site operator and Open edX service provider, have the policy to use in production the previous release to the latest. The reason behind that is that even when a new major version is released, there are still bugs that are discovered by real use. https://github.com/openedx/frontend-app-authoring/issues/1199 is an example of a bug found in Redwood while it is the current release. In addition, the fix to this bug implied un-archiving an archived repo. IMO, repos of the versions under maintenance shouldn’t be archived. I would like to propose to keep the latest two (2) versions under maintenance. I know this can be a challenge to the maintenance group, considering the scarce resources they have. But I think this is something to bring back to the maintenance agenda.

• This feels like it’s a thing that BTR should decide since they would be signing up for more work.

• Extending the maintenance window implies that we extend how long we support security updates for a release.

  • Since a lot of providers still use older versions, it’s probably not a good idea to not do security fixes.

Devstack Deprecation related questions

• https://github.com/openedx/open-edx-proposals/issues/595#issuecomment-2394527019