Dear list, currently, there's version 1.2 of the web development framework django included in epel6. A week ago, django 1.4 was released. Afaik, the django developers support only two minor releases at a time, so it's questionable if django-1.2 will get any (security-)updates from now on.
My question is: Is there a operation precedure to do an upgrade to e.g. django-1.3 (and accepting possible breakage of old software)? Is this even required? If nobody complains about this update, I'd prepare an update to version 1.3 probably next weekend. There are some minor backwards incompatible changes [1], in general, versions 1.2 and 1.3 are compatible. There's also a bugzilla-entry regarding this[2]. Thanks! Matthias [1] https://docs.djangoproject.com/en/1.3/releases/1.3/#backwards-incompatible-changes-in-1-3 [2] https://bugzilla.redhat.com/show_bug.cgi?id=802153 -- Matthias Runge <[email protected]> <[email protected]> _______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
