#15245 closed (fixed)
Django 1.2.5 release notes do not reflect changes listed in weblog post regarding security release
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | 1.2 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The security changes discussed on the Django weblog at:
http://www.djangoproject.com/weblog/2011/feb/08/security/
are not reflected in the Django 1.2.5 release notes in the tarball or website at:
http://docs.djangoproject.com/en/1.2/releases/1.2.5/.
Additionally these release notes mention further backwards incompatible changes which are not mentioned on the weblog posting.
Change History (3)
comment:1 by , 14 years ago
| Component: | Uncategorized → Documentation |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
Note:
See TracTickets
for help on using tickets.
There's not much we can do post-facto about the weblog entry; however, the release notes should be updated to include details about the issues with the security release.