Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#19660 closed Cleanup/optimization (worksforme)

Django 1.4 release notes links to a page with no 1.4 documentation

Reported by: schillingt@… Owned by: nobody
Component: Documentation Version: 1.4
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

Hi all,

I was viewing the 1.4 release notes, in particular the improved password hashing section (https://docs.djangoproject.com/en/dev/releases/1.4/#improved-password-hashing) and clicked on the link to How Django Stores Passwords. This brought me to https://docs.djangoproject.com/en/dev/topics/auth/passwords/#auth-password-storage. However, I could not change this page's documentation to 1.4. It appears that it's only valid for 1.5 and up. Is this documentation also valid for 1.4? If not, I would think that the link should be removed from the 1.4 release notes.

Let me know if you have any questions for me.

Thanks,
Tim

Change History (3)

comment:1 Changed 2 years ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to worksforme
  • Status changed from new to closed

Password management didn't change significantly between Django 1.4 and 1.5; however, the docs that were re-organized, and the version switcher doesn't deal with that.

This section is also valid for 1.4. If you read the 1.4 release notes in the 1.4 version of the docs, you'll land on pretty much the same text, with an additional paragraph explaining this is new in 1.4.

comment:2 Changed 2 years ago by schillingt@…

However, the password hashing list on https://docs.djangoproject.com/en/1.5/topics/auth/passwords/ does not seem to match what's actually being used by Django 1.4. I'd say that difference is enough to have a separate page.

comment:3 Changed 2 years ago by anonymous

Nope I'm wrong. I apologize.

Note: See TracTickets for help on using tickets.
Back to Top