#15253 closed (fixed)
1.1.3, 1.2.4, and 1.3 release notes lack mention of Dec. 2010 security fixes
| Reported by: | Gary Wilson | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | blocker | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
http://www.djangoproject.com/weblog/2010/dec/22/security/
In fact, there are no 1.1.3 release notes in trunk (didn't check if these were committed to 1.1.x branch).
Change History (9)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
| Keywords: | blocker added |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
1.2.4 notes don't need any change, because it was the 1.2.5 releease :-)
I committed a note to the 1.2.5 release notes last night in r15478 (responding to #15245). #15259 indicates that there is a problem with the example, but once that is fixed, the same text should be cross ported into the 1.3 and 1.1.4 release notes.
And yes, it is needed in the 1.3 notes, because anyone upgrading from 1.2 to 1.3 will hit the problem.
comment:5 by , 14 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
... and now I've just re-read the ticket title, and you're referring to the *December* security release, not yesterday's release.
Note:
See TracTickets
for help on using tickets.
Also not exactly sure if we need to include in the 1.3 release notes or not since technically the changes will be mentioned in the 1.2.4 notes and 1.3 notes are changes from version 2.