Remove "Experimental" tag from execution profiles documentation

aboudreault · mambocab · commit e9b9082e1d9f · 2018-01-03T16:08:34.000-05:00
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
@@ -19,6 +19,7 @@ Other
 * Possible deadlock on cassandra.concurrent.execute_concurrent (PYTHON-768)
 * Add some known deprecated warnings for 4.x (PYTHON-877)
 * Remove copyright dates from copyright notices (PYTHON-863)
+* Remove "Experimental" tag from execution profiles documentation (PYTHON-840)
 
 3.12.0
 ======
diff --git a/docs/execution_profiles.rst b/docs/execution_profiles.rst
@@ -1,13 +1,13 @@
-Execution Profiles (experimental)
-=================================
+Execution Profiles
+==================
 
-Execution profiles are an experimental API aimed at making it easier to execute requests in different ways within
+Execution profiles aim at making it easier to execute requests in different ways within
 a single connected ``Session``. Execution profiles are being introduced to deal with the exploding number of
 configuration options, especially as the database platform evolves more complex workloads.
 
-The Execution Profile API is being introduced now, in an experimental capacity, in order to take advantage of it in
-existing projects, and to gauge interest and feedback in the community. For now, the legacy configuration remains
-intact, but legacy and Execution Profile APIs cannot be used simultaneously on the same client ``Cluster``.
+The legacy configuration remains intact, but legacy and Execution Profile APIs
+cannot be used simultaneously on the same client ``Cluster``. Legacy configuration
+will be removed in the next major release (4.0).
 
 This document explains how Execution Profiles relate to existing settings, and shows how to use the new profiles for
 request execution.
