Hi Yann,

The policy we use for backporting is described there: https://docs.djangoproject.com/en/1.7/internals/release-process/#supported-versions

> The rule of thumb is that fixes will be backported to the last major release for bugs that would have prevented a release in the first place (release blockers).

The issue in question (https://code.djangoproject.com/ticket/13776) doesn't meet those criteria (it's not a regression so it wouldn't be categorized as a release blocker).


This leaves you with the following options:

* Wait until 1.8 is released with this fix (and use a workaround or a private fork until then) * Find a good argument as to why this particular fix should be backported ("all the tests pass" is a good start but it's not enough).


I hope that makes sense.
Thanks,

Baptiste

On 12/01/2014 03:49 PM, Yann Fouillat wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I have an issue which is corrected in master but not in the 1.7.x
branch and I would like to know what I should do ?

The commit fixing my issue is
https://github.com/django/django/commit/45e049937d2564d11035827ca9a9221b86215e45#diff-70af885c2725fe87eb3b99a393268d10.

I tried to backport it in stable/1.7.x and all the tests pass.

Regards,
- -- Yann FOUILLAT
Ingénieur Développeur
Makina Corpus
Tél : 02 51 79 80 82
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUfH/mAAoJEO1YhKM5jgEdTV4IAJSE+IftGMPRxZEaXCYQguGV
NxdOZIDizqXOFWc4zwwS44eZoXcZyTjUKw/zs/DSHQ/CHd0yYTkOD1mkdoEtPVvE
V3xjh3bMPodB95qwxSpLn11//far02J9pob3XNj0G7pdMN7wqmICNNvE6Cpa/Prj
6vp5HN0NYwYhLiFowC8iMpt4b2KWiXba1YPNf1UmuGI5tNa5jTuc4oJx+r1pMxID
fAE4UdX4oWyqMzHBIJ/LWa5SqtrGY9/gcHlGI2zIDNSxIEubva0UAfKp2AKPnKwL
vjyKMbdofmxDNw0v4AgvBS/nslF0vvFwz93BswxjTJa8SQbF0rVHxMzK/DdyDrs=
=Wjs+
-----END PGP SIGNATURE-----


--
You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/547C857C.8030301%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to