Actions
Task #1760
closed
Figure out our plan for when Django14 gets re-retired
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
Issue #1755 occurred because Django14 was removed from EPEL6. This caused such problems for users that the package is being temporarily brought back to EPEL6, but it's not a very good situation for 2 reasons.
1) The Django14 is known to be insecure and is not receiving updates from upstream Django or from the package maintainer in EPEL.
2) Django14 eventually will likely be re-retired at some point at which point if we take don't take proactive action we'll have #1755 again on our hands.
See the epel-devel thread[0] on this issue where the future of Django14 is being discussed.
Actions
.