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
>
Dear all,
You are kindly invited to the meeting:
EPSCO meeting on 2016-11-09 from 18:00:00 to 19:00:00 GMT
At fedora-meet...@irc.freenode.net
The meeting will be about:
Extra Packages for Enterprise Linux Steering COmmittee (EPSCO) has a weekly
meeting to go over concerns and problems in
On 8 November 2016 at 10: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
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
Afternoon,
I'm currently working through the final stages of a new release for
Patchwork [1]. One of the things that's been discussed extensively in
the past is the versions of Django we support. Most sysadmins refuse to
use packages outside of those provided by their distro (i.e. no pip).