Opened 13 years ago
Closed 13 years ago
#17926 closed Bug (fixed)
XMLField removed in 1.4 but still documented
| Reported by: | Alex Burgel | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.4-beta-1 |
| Severity: | Normal | 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
XMLField removed in 1.4 but still documented
the 1.4 docs still say XMLField is deprecated, and the release notes do not mention that it has been removed.
Change History (4)
comment:1 by , 13 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 by , 13 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
This hasn't resolved the issue of it not being mentioned in the Django 1.4 release notes.
comment:4 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
See comment:1, removal of deprecated objects are not in release notes.
Note:
See TracTickets
for help on using tickets.
This should be removed, thanks for spotting it.
However, when some deprecated object is deleted in any version, the release notes of the version do not repeat that it has been deleted. You should read the previous version release notes to find the deprecation notice.
https://docs.djangoproject.com/en/1.3/releases/1.3/#removal-of-xmlfield