--- title: #493: CalVer and LTS | daily.dev description: A roundup of Python community news covering three self-hosted web UI projects for Traefik, nginx, and Caddy reverse proxies; Wagtail 8.0's release with custom... canonical: https://daily.dev/posts/493-calver-and-lts-zsmdgihad twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: #493: CalVer and LTS | daily.dev og:description: A roundup of Python community news covering three self-hosted web UI projects for Traefik, nginx, and Caddy reverse proxies; Wagtail 8.0's release with custom... og:url: https://daily.dev/posts/493-calver-and-lts-zsmdgihad og:image: https://api.daily.dev/og/posts/ZsmDGiHaD.png og:image:alt: #493: CalVer and LTS og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # #493: CalVer and LTS **[Planet Python](https://daily.dev/sources/planetpython)** · 9 min read · 1 upvotes · 0 comments ## Summary A roundup of Python community news covering three self-hosted web UI projects for Traefik, nginx, and Caddy reverse proxies; Wagtail 8.0's release with custom base page models, a new read/write REST API, and security fixes; CPython officially adding RISC-V as a tier 3 supported platform under PEP 11; and Django's plan starting with Django 2028 to move to annual calendar-versioned releases where every version gets three years of support, eliminating the old LTS/non-LTS distinction. Extra links cover Python docs adding time-complexity notes, a free book, a uv Python-pruning script, and Ollama cloud models. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Will Django switch to calendar versioning and yearly releases? Yes, starting with Django 2028, Django moves to one feature release per January, adopts calendar-based version numbers, and supports every release for three years. This eliminates the old standard versus LTS distinction, since every release becomes a long-supported option. Each release gets one year of mainstream bug fixes followed by two years of security and data-loss fixes, and existing Django 5.2 LTS and 6.2 LTS commitments remain unchanged before 2028. _Teams planning Django upgrade cycles can track this shift toward annual CalVer releases on daily.dev._ ### Is RISC-V officially supported by CPython now? Yes, CPython added RISC-V as a PEP 11 tier 3 platform, specifically targeting 64-bit Linux (riscv64-unknown-linux-gnu). This makes the port a maintained compatibility target so future CPython changes are less likely to silently break it, though there are still no python.org installers and no binary wheel parity for native extensions. Tier 3 also means failures don't block a Python release, since a core developer contact and buildbot are required but not full guarantees. _Developers targeting RISC-V hardware can follow tier progress and testing calls like this on daily.dev._ ### What changed in Wagtail 8.0? Wagtail 8.0 adds support for custom base page models so projects no longer must subclass Wagtail's Page as shipped, introduces a new v3 REST API supporting both read and write CMS operations for the first time, and adds a global registry for permission policies with full PageViewSet customization. It also stops auto-converting AVIF and WebP images to PNG by default, fixes five security issues, and formalizes Django 6.1 support with uv-based CI. _CMS developers upgrading Wagtail can check breaking behavior changes like the image conversion default on daily.dev._ ## Similar posts on daily.dev - [PyCoder’s Weekly](https://daily.dev/posts/pycoder-s-weekly-oekitkw2s) · Planet Python · 0 upvotes · 0 comments - [Issue 350: Django moves to an annual release cycle](https://daily.dev/posts/issue-350-django-moves-to-an-annual-release-cycle-ulipqy5ir) · Django News · 0 upvotes · 0 comments - [PyCoder’s Weekly](https://daily.dev/posts/pycoder-s-weekly-6ho8fly1b) · Planet Python · 0 upvotes · 0 comments --- Tags: [#python](https://daily.dev/tags/python), [#django](https://daily.dev/tags/django), [#cpython](https://daily.dev/tags/cpython) [View this post on daily.dev](https://daily.dev/posts/493-calver-and-lts-zsmdgihad) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"#493: CalVer and LTS","url":"https://daily.dev/posts/493-calver-and-lts-zsmdgihad","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/493-calver-and-lts-zsmdgihad"},"datePublished":"2026-08-26T01:52:11.124Z","dateModified":"2026-09-14T08:46:43.480Z","description":"A roundup of Python community news covering three self-hosted web UI projects for Traefik, nginx, and Caddy reverse proxies; Wagtail 8.0's release with custom...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a4219fd1da3667f9dd1f1717cd44ebdc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a4219fd1da3667f9dd1f1717cd44ebdc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Planet Python","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Planet Python","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/eac3cc584cb043b5a242d13752bd3d0c","url":"https://daily.dev/sources/planetpython"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/493-calver-and-lts-zsmdgihad","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"python,django,cpython","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Planet Python","item":"https://daily.dev/sources/planetpython"},{"@type":"ListItem","position":3,"name":"#493: CalVer and LTS"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/493-calver-and-lts-zsmdgihad#faq","mainEntity":[{"@type":"Question","name":"Will Django switch to calendar versioning and yearly releases?","acceptedAnswer":{"@type":"Answer","text":"Yes, starting with Django 2028, Django moves to one feature release per January, adopts calendar-based version numbers, and supports every release for three years. This eliminates the old standard versus LTS distinction, since every release becomes a long-supported option. Each release gets one year of mainstream bug fixes followed by two years of security and data-loss fixes, and existing Django 5.2 LTS and 6.2 LTS commitments remain unchanged before 2028. Teams planning Django upgrade cycles can track this shift toward annual CalVer releases on daily.dev."}},{"@type":"Question","name":"Is RISC-V officially supported by CPython now?","acceptedAnswer":{"@type":"Answer","text":"Yes, CPython added RISC-V as a PEP 11 tier 3 platform, specifically targeting 64-bit Linux (riscv64-unknown-linux-gnu). This makes the port a maintained compatibility target so future CPython changes are less likely to silently break it, though there are still no python.org installers and no binary wheel parity for native extensions. Tier 3 also means failures don't block a Python release, since a core developer contact and buildbot are required but not full guarantees. Developers targeting RISC-V hardware can follow tier progress and testing calls like this on daily.dev."}},{"@type":"Question","name":"What changed in Wagtail 8.0?","acceptedAnswer":{"@type":"Answer","text":"Wagtail 8.0 adds support for custom base page models so projects no longer must subclass Wagtail's Page as shipped, introduces a new v3 REST API supporting both read and write CMS operations for the first time, and adds a global registry for permission policies with full PageViewSet customization. It also stops auto-converting AVIF and WebP images to PNG by default, fixes five security issues, and formalizes Django 6.1 support with uv-based CI. CMS developers upgrading Wagtail can check breaking behavior changes like the image conversion default on daily.dev."}}]} ```