Backporting policy for 1.2.X
Luke Plant
After some discussions on django-core, we recently changed our
backporting policy for the bug fix branch. However, we didn't say
anything about the previous branch (i.e. 1.2.X currently). Are we going
to leave that the same - security fixes only? With a smaller backporting
burden, I wouldn't be opposed to having the same policy for both branches.
In particular, and I'm guessing this might be a separate issue, I'm
wondering if we should backport the fix for #13648 [1] to 1.2.X. The
case for backporting is that it is actually a regression that would have
been a release blocker if it had been caught before 1.2 was released. At
the very least it should have been marked as a regression while 1.3 was
being developed, and therefore backported.
Regards,
Luke
[1] Ticket: http://code.djangoproject.com/ticket/13648
Changeset: http://code.djangoproject.com/changeset/16209
--
"Outside of a dog, a book is a man's best friend... inside of a
dog, it's too dark to read."
Luke Plant || http://lukeplant.me.uk/