django.contrib.auth.admin.UserAdmin.response_add changed in 1.2.4

[jonas.obrist@…]

Changeset ​http://code.djangoproject.com/changeset/14628 introduced a change to UserAdmin.response_add which snuck into the 1.2.4 bugfix release of Django changing an existing API, which is not documented in the release notes of the security fix 1.2.4.

[Ramiro Morales]

First, a bit of background: r14629 fixed #14679 (I forgot to link the ticket in the commit message, sorry) that reported an unintended change in behavior introduced in r13503, that fixed #14014, that reported an unintended change in behavior introduced before the 1.2 release (r12218).

I see you point because, from an user POV, this is a behavior that changed during in 1.2.X branch life cycle, but OTOH it's buggy behavior that got corrected (hopefully for good after two commits) so a) all the buttons in the user add form do what their labels say, and b) they redirect to sensible pages after they are pressed just like they did in 1.1.

And yes, the 1.2.4 release has been triggered by a security fix, but our policy has always been that maintenance releases also fix other issues (I count aprox. 280 fixes of all kinds between 1.2.3 and 1.2.4).

Not sure I agree with you this is a change of an existing API, and I can see a release note could be of help.

[jonas.obrist@…]

Thank you very much for the clarification.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Aymeric Augustin]

Since we no longer support 1.2 I think we can abandon this ticket.