From 7e7e447b40d934aedd2f4b1fdc2d9aaef164ade0 Mon Sep 17 00:00:00 2001
From: Matt Robenolt <matt@ydekproductions.com>
Date: Sat, 1 Aug 2015 11:59:43 -0700
Subject: [PATCH] [1.8.x] Removed obsolete note about sentry/raven not handling
 WSGI properly.

2.0.7 was released in 2012.

Backport of 514fee82a18e2b8fed0b6e31a95bd7a1a94980ab from master
---
 docs/howto/deployment/wsgi/index.txt | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/howto/deployment/wsgi/index.txt b/docs/howto/deployment/wsgi/index.txt
index 128e296ad6..a6c7d4b229 100644
--- a/docs/howto/deployment/wsgi/index.txt
+++ b/docs/howto/deployment/wsgi/index.txt
@@ -85,7 +85,6 @@ to combine a Django application with a WSGI application of another framework.
 .. note::
 
     Some third-party WSGI middleware do not call ``close`` on the response
-    object after handling a request — most notably Sentry's error reporting
-    middleware up to version 2.0.7. In those cases the
+    object after handling a request. In those cases the
     :data:`~django.core.signals.request_finished` signal isn't sent. This can
     result in idle connections to database and memcache servers.