I believe the future of Django in EPEL is a topic that is being discussed
on the EPSCO meetings last week and this week (18:00 UTC on Wednesdays in
#fedora-meeting, iirc).
I'm hoping that even if a newer, 1.8 based Django package is added to
EPEL6, that the existing one named Django14 can be kept
This removal has been problematic for a lot of software including the listed
EPEL dependencies and anything those depend on. I propose the following be done:
- Temporarily un-retire Django14 in EPEL6, and allow a planned sunset after
some period of time. It would not receive updates during this
