On 08/11/16 16:31, Brian Bouterse wrote: > 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 for legacy > usage. The Django14 package having that unconventional name would allow > a new package to use the more conventional python-django name which is > convenient. I believe I can shed a light here: - Django14 followed the old Django naming scheme in Fedora. Django was renamed to python-django there. - Django-1.4 was the old long term supported version and works with pythons up to python 2.6 - Django14 should be retired IMO - Django-1.8 (current long term supported version) requires python 2.7. That means, we can not have a recent Django in EPEL6 with system python. - The main reason not updating to Django-1.8 in EPEL7 is reviewboard. (I don't know the state of askbot currently, Fedora has ask.fedoraproject.org). - Maintaining a django version, which was retired upstream becomes more and more a pain, esp. if it's not part of your job to keep it alive. Matthias _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
