#16907 closed Cleanup/optimization (fixed)
Deprecate databrowse
| Reported by: | Preston Holmes | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.databrowse | Version: | dev |
| Severity: | Release blocker | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Several times it has come up that databrowse is a good candidate for removal from Django.
https://code.djangoproject.com/wiki/SummerOfCode2011#Integratedatabrowseintotheadmin
http://groups.google.com/group/django-developers/browse_thread/thread/3ff58cc663822456
are just two
Attachments (1)
Change History (11)
comment:2 by , 14 years ago
| milestone: | → 1.4 |
|---|---|
| Patch needs improvement: | set |
| Triage Stage: | Unreviewed → Accepted |
Minor tweaks to docs still required, but after those, feel free to promote to Ready for Checkin yourself.
comment:3 by , 14 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
tweaks made - self marking RFC per suggestion from SmileyChris - committer may choose to further refine release note if desired.
comment:5 by , 14 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
Hm, this needs a note in the deprecation docs.
by , 14 years ago
| Attachment: | deprecation-timeline.diff added |
|---|
comment:7 by , 14 years ago
| Patch needs improvement: | unset |
|---|
Sorry about the miss on the note, I thought I had grepped docs for deprecate - but at the time I think I was looking for style and usage and just landed on release notes
comment:8 by , 14 years ago
| Severity: | Normal → Release blocker |
|---|
marking this as a release blocker to prevent any chance that the deprecation gets released without the correction to the timeline
Here is a pull that implements the initiation of deprecation:
https://github.com/django/django/pull/53