From ce412d00c625bb90ac4091731b3d32084321c9fb Mon Sep 17 00:00:00 2001 From: Jake Howard Date: Sat, 11 Apr 2020 15:18:01 +0100 Subject: [PATCH] Fix django cycle image Remove the cachebust so it's always correct --- content/posts/django-22.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/django-22.md b/content/posts/django-22.md index 8c3be7a..d402a90 100644 --- a/content/posts/django-22.md +++ b/content/posts/django-22.md @@ -8,7 +8,7 @@ April marks the release of Django 2.2, the latest LTS version of the popular Pyt Django historically works off the LTS pattern of software releasing, providing 2 channels. LTS versions are maintained far longer than regular versions, and receive regular bug fixes and security patches in line with the main release channel. -![Django update cycle](https://static.djangoproject.com/img/release-roadmap.e844db08610e.png) +![Django update cycle](https://static.djangoproject.com/img/release-roadmap.png) The bump from 1.11 to 2.2 also bought with it the updates from 2.0 and 2.1. Features used by some users for 18 months finally come to those who need the stability of an LTS release. I've not delved too far into the 2.x releases so far, as most of what I do strongly benefits from using an LTS-based version.