LTS Release Schedule for CRX

[rxm7706]

I tried looking for information on when CRX would support wagtail 7.0 and django 5.2 LTS, but could not find an estimated date. So I thought I'd rather ask the more pertinent question around LTS.

With Wagtail Adopting an LTS, that aligns behind Django. It has really helped with planning and scheduling. Would coderedcms be adopting a similar strategy.

Reference : https://wagtail.org/blog/wagtail-70/

Django schedules their LTS releases for April and now we will have our LTS releases scheduled for May. This will make it much easier for anyone who loves our LTS releases to upgrade to our newest LTS version and the newest LTS version of Django at the same time. We hope this schedule adjustment will make upgrade planning a lot easier and more manageable for everyone who relies on us.

Thank you and regards.

[auvipy]

I might try to come with a PR to start adding support for wagtail 7.x if the maintainers agree

[vsalvino]

We don't have a schedule of future releases. Generally we try to adapt new versions of wagtail as soon as possible, whenever we get a moment of time! This sometimes takes a few weeks, or a few months, depending on how big the upgrade is, or how heavy our workload is.

We do have a list of supported versions here: https://docs.coderedcorp.com/wagtail-crx/releases/index.html

Keep in mind, all of our dependencies also need to first support new versions of Django and Wagtail (sometimes they need updated, sometimes they don't). Such as: wagtail-seo, wagtail-cache, django-bootstrap5, etc.

Pull requests are welcome if you want to help :)

[rxm7706]

Related PRs and Issues

• Formalize support for Django 5.2 wagtail/wagtail#13015
• Add support for Django 5.2 zostera/django-bootstrap5#753
• Wagtail 7.0 Maintenance wagtail-cache#86
• Support for wagtail 7.0 LTS wagtail-flexible-forms#9
• Add support for wagtail 7.0 wagtail-seo#77
• Support for wagtail 7.0+ wagtail-seo#78