Hi,
the subject says it all, I'm intending to retire Django-1.1 in EPEL5. The last update has been released about two years ago, there are at least two known security issues.
Current Django is Django-1.5, and Django 1.4 is the oldest version getting security fixes from upstream.
On 03/22/2013 08:11 AM, Christopher Meng wrote:
In fact, no rhel5 people will install django via epel.
How do you know? What does that mean to my earlier mail? What will they install else?
All my friends under RHEL5 and derivatives install django from other ways..... 1.1 is too old.
On 03/22/2013 09:36 AM, Christopher Meng wrote:
All my friends under RHEL5 and derivatives install django from other ways..... 1.1 is too old.
well, interesting argument. Do you know, when RHEL5 was released (2007)? IMHO, if somebody still runs RHEL5, then because there is a requirement to do so.
Since RHEL versions are long running, I can not guarantee, there's nobody out there still running Django-1.1
Which version of Django do your friends?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/22/2013 03:05 AM, Matthias Runge wrote:
Hi,
the subject says it all, I'm intending to retire Django-1.1 in EPEL5. The last update has been released about two years ago, there are at least two known security issues.
Current Django is Django-1.5, and Django 1.4 is the oldest version getting security fixes from upstream.
I'm in favor of retiring packages with known security issues. We're providing the Django14 package for people who can use that version, and I assume that a Django15 package is coming soon as well, Matthias?
epel-devel@lists.fedoraproject.org
-
Christopher Meng -
Matthias Runge -
Stephen Gallagher