DOCSP-21352: Remove EOL'd ..versionadded:: (#800)

* DOCSP-21352: Remove EOL'd ..versionadded::

* DOCSP-21352: Fix markup error

* DOCSP-21352: Incorporate review comments

Co-authored-by: Sarah Olson <[email protected]>

Author: sarah-olson-mongodb

draft/tutorial/expire-least-recently-used-data.txt

@@ -4,8 +4,6 @@ Expire Least Recently Used Data from a Collection
 
 .. default-domain:: mongodb
 
-.. versionadded:: 2.2
-
 Least recently used, or LRU, data retention patterns are used in simple
 data caches or support for stateless systems. By extending TTL
 collections with application support provides additional features.

source/administration/monitoring.txt

@@ -311,7 +311,7 @@ affect logging:
 Log Redaction
 ~~~~~~~~~~~~~
 
-.. versionadded:: 3.4 Available in MongoDB Enterprise only
+*Available in MongoDB Enterprise only*
 
 A :binary:`~bin.mongod` running with :setting:`security.redactClientLogData`
 redacts :doc:`messages </reference/log-messages>` associated with any given

source/administration/production-notes.txt

@@ -207,8 +207,6 @@ more information.
 Read Concern
 ~~~~~~~~~~~~
 
-.. versionadded:: 3.2
-
 .. include:: /includes/fact-read-own-writes.rst
 
 Write Concern

source/core/aggregation-pipeline-optimization.txt

@@ -183,8 +183,6 @@ The optimizer can add the same :pipeline:`$match` stage before the
 ``$project``/``$unset`` + ``$skip`` Sequence Optimization
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 3.2
-
 When you have a sequence with :pipeline:`$project` or :pipeline:`$unset` followed by 
 :pipeline:`$skip`, the :pipeline:`$skip` 
 moves before :pipeline:`$project`. For example, if
@@ -353,8 +351,6 @@ stage
 ``$lookup`` + ``$unwind`` Coalescence
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 3.2
-
 When a :pipeline:`$unwind` immediately follows another
 :pipeline:`$lookup`, and the :pipeline:`$unwind` operates on the ``as``
 field of the :pipeline:`$lookup`, the optimizer can coalesce the

source/core/bulk-write-operations.txt

@@ -18,8 +18,6 @@ bulk. Bulk write operations affect a *single* collection. MongoDB
 allows applications to determine the acceptable level of
 acknowledgement required for bulk write operations.
 
-.. versionadded:: 3.2
-
 The :method:`db.collection.bulkWrite()` method provides the ability to 
 perform bulk insert, update, and remove operations.
 MongoDB also supports bulk insert

source/core/databases-and-collections.txt

@@ -88,8 +88,6 @@ To modify these collection options, see :dbcommand:`collMod`.
 Document Validation
 ~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 3.2
-
 By default, a collection does not require its documents to have the
 same schema; i.e. the documents in a single collection do not need to
 have the same set of fields and the data type for a field can differ
@@ -113,13 +111,6 @@ type, update the documents to the new structure.
 Unique Identifiers
 ~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 3.6
-
-.. note::
-
-   The ``featureCompatibilityVersion`` must be set to ``"3.6"`` or greater. For
-   more information, see :ref:`view-fcv`.
-
 Collections are assigned an immutable :abbr:`UUID (Universally unique
 identifier)`. The
 collection UUID remains the same across all members of a replica set

source/core/index-case-insensitive.txt

@@ -12,8 +12,6 @@ Case Insensitive Indexes
    :depth: 2
    :class: singlecol
 
-.. versionadded:: 3.4
-
 Case insensitive indexes support queries that perform string
 comparisons without regard for case.
 

source/core/index-partial.txt

@@ -13,8 +13,6 @@ Partial Indexes
    :depth: 1
    :class: singlecol
 
-.. versionadded:: 3.2
-
 Partial indexes only index the documents in a collection that meet a
 specified filter expression. By indexing a subset of the documents in a
 collection, partial indexes have lower storage requirements and reduced

source/core/index-unique.txt

@@ -228,8 +228,6 @@ the unique constraint on the value of the field ``x``:
 Unique Partial Indexes
 ~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 3.2
-
 Partial indexes only index the documents in a collection that meet a
 specified filter expression. If you specify both the
 ``partialFilterExpression`` and a :ref:`unique constraint

source/core/read-isolation-consistency-recency.txt

@@ -61,8 +61,6 @@ Monotonic Writes
 Real Time Order
 ---------------
 
-.. versionadded:: 3.4
-
 For read and write operations on the primary, issuing read operations
 with :readconcern:`"linearizable"` read concern and write operations
 with :writeconcern:`"majority"` write concern enables multiple threads
@@ -79,8 +77,6 @@ schedule for these reads and writes is considered linearizable.
 Causal Consistency
 ------------------
 
-.. versionadded:: 3.6
-
 If an operation logically depends on a preceding operation, there is a
 causal relationship between the operations. For example, a write
 operation that deletes all documents based on a specified condition and

source/core/read-preference-staleness.txt

@@ -6,8 +6,6 @@ Read Preference ``maxStalenessSeconds``
 
 .. default-domain:: mongodb
 
-.. versionadded:: 3.4
-
 Replica set members can lag behind the :term:`primary` due to network
 congestion, low disk throughput, long-running operations, etc. The read
 preference ``maxStalenessSeconds`` option lets you specify a maximum

source/core/retryable-writes.txt

@@ -360,8 +360,6 @@ retrying upserts which failed due to duplicate key errors.
 Diagnostics
 ~~~~~~~~~~~
 
-.. versionadded:: 3.6.3
-
 The :dbcommand:`serverStatus` command, and its :binary:`~bin.mongosh`
 shell helper :method:`db.serverStatus()` includes statistics on
 retryable writes in the :serverstatus:`transactions` section.

source/core/schema-validation.txt

@@ -12,8 +12,6 @@ Schema Validation
    :depth: 1
    :class: singlecol
 
-.. versionadded:: 3.2
-
 MongoDB provides the capability to perform schema validation during
 updates and insertions.
 
@@ -44,11 +42,8 @@ MongoDB also provides the following related options:
 JSON Schema
 -----------
 
-.. versionadded:: 3.6
-
-Starting in version 3.6, MongoDB supports JSON Schema validation. To
-specify JSON Schema validation, use the :query:`$jsonSchema` operator
-in your ``validator`` expression.
+MongoDB supports JSON Schema validation. To specify JSON Schema validation, 
+use the :query:`$jsonSchema` operator in your ``validator`` expression.
 
 .. note::
 

source/core/security-encryption-at-rest.txt

@@ -22,8 +22,6 @@ privacy standards, including HIPAA, PCI-DSS, and FERPA.
 Encrypted Storage Engine
 ------------------------
 
-.. versionadded:: 3.2
-
 .. include:: /includes/fact-enterprise-only-admonition.rst
 
 .. important:: Available for the WiredTiger Storage Engine only.

source/core/security-ldap-external.txt

@@ -13,15 +13,13 @@ LDAP Authorization
    :depth: 1
    :class: singlecol
 
-.. versionadded:: 3.4
-
-   `MongoDB Enterprise
-   <http://www.mongodb.com/products/mongodb-enterprise-advanced?tck=docs_server>`_ supports
-   querying an LDAP server for the LDAP groups to which the authenticated user
-   belongs. MongoDB maps the distinguished names (DN) of each returned group
-   to :ref:`roles <roles>` on the ``admin`` database. MongoDB authorizes the
-   user based on the mapped roles and their associated privileges. See
-   :ref:`LDAP Authorization <security-ldap-external>` for more information.
+`MongoDB Enterprise
+<http://www.mongodb.com/products/mongodb-enterprise-advanced?tck=docs_server>`_ supports
+querying an LDAP server for the LDAP groups to which the authenticated user
+belongs. MongoDB maps the distinguished names (DN) of each returned group
+to :ref:`roles <roles>` on the ``admin`` database. MongoDB authorizes the
+user based on the mapped roles and their associated privileges. See
+:ref:`LDAP Authorization <security-ldap-external>` for more information.
 
 The LDAP Authorization process is summarized below:
 

source/core/security-ldap.txt

@@ -167,8 +167,6 @@ authorization on each :term:`shard` for shard-local users.
 LDAP Authentication via the Operating System LDAP libraries
 -----------------------------------------------------------
 
-.. versionadded:: 3.4
-
 The LDAP authentication via OS libraries process is summarized below:
 
 #. A client authenticates to MongoDB, providing a user's credentials.

source/core/shell-types.txt

@@ -216,8 +216,6 @@ constructor to explicitly specify 32-bit integers.
 NumberDecimal
 ~~~~~~~~~~~~~
 
-.. versionadded:: 3.4
-
 The :binary:`~bin.mongo` shell treats all numbers as 64-bit floating-point
 ``double`` values by default. The :binary:`~bin.mongo` shell provides the
 ``NumberDecimal()`` constructor to explicitly specify 128-bit

source/includes/extracts-agg-operators.yaml

@@ -580,15 +580,11 @@ content: |
 
         - Combines multiple documents into a single document.
 
-          .. versionadded:: 3.6
-
       * - :expression:`$objectToArray`
 
         - Converts a document to an array of documents representing
           key-value pairs.
 
-          .. versionadded:: 3.6
-
       * - :expression:`$setField`
 
         - Adds, updates, or removes a specified field in a document. You

source/includes/extracts-arrayFilters.yaml

@@ -51,8 +51,6 @@ content: |
 ref: arrayFilters-blurb
 content: |
 
-   .. versionadded:: 3.6
-
    Starting in MongoDB 3.6, when updating an array field, you can
    specify ``arrayFilters`` that determine which array elements to
    update.

source/includes/extracts-collation.yaml

@@ -1,6 +1,5 @@
 ref: collation-versionadded
 content: |
-   .. versionadded:: 3.4
 
    .. include:: /includes/extracts/collation-description.rst
 ---
@@ -215,8 +214,6 @@ content: |
    .. include:: /includes/extracts/collation-unspecified.rst
 
    .. include:: /includes/extracts/collation-single-per-operation.rst
-
-   .. versionadded:: 3.4
 ---
 ref: collation-operations-table
 content: |-

source/includes/extracts-date-format-specifiers.yaml

@@ -19,9 +19,6 @@ content: |
       * - ``%G``
 
         - Year in ISO 8601 format
-
-          .. versionadded:: 3.4
-
         - ``0000``-``9999``
 
       * - ``%H``
@@ -58,9 +55,6 @@ content: |
       * - ``%u``
 
         - Day of week number in ISO 8601 format (1-Monday, 7-Sunday)
-
-          .. versionadded:: 3.4
-
         - ``1``-``7``
 
       * - ``%U``
@@ -71,9 +65,6 @@ content: |
       * - ``%V``
 
         - Week of Year in ISO 8601 format
-
-          .. versionadded:: 3.4
-
         - ``01``-``53``
 
       * - ``%Y``
@@ -83,19 +74,13 @@ content: |
       * - ``%z``
 
         - The timezone offset from UTC.
-
-          .. versionadded:: 3.6
-
         - ``+/-[hh][mm]``
 
       * - ``%Z``
 
         - The minutes offset from UTC as a number. For example, if the
           timezone offset (``+/-[hhmm]``) was ``+0445``, the minutes
           offset is ``+285``.
-
-          .. versionadded:: 3.6
-
         - ``+/-mmm``
 
       * - ``%%``

source/includes/fact-auth-restrictions-array-contents.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 3.6
-
 The ``authenticationRestrictions`` document can contain *only* the
 following fields. The server throws an error if the 
 ``authenticationRestrictions`` document contains an unrecognized field:
@@ -40,4 +38,4 @@ following fields. The server throws an error if the
    unable to authenticate the user.
 
 For more information on authentication in MongoDB, see
-:doc:`Authentication </core/authentication/>`.
+:doc:`Authentication </core/authentication/>`.

source/includes/fact-auth-restrictions-role-desc.rst

@@ -2,5 +2,3 @@ The authentication restrictions the server enforces on the role.
 Specifies a list of IP addresses and
 :abbr:`CIDR (Classless Inter-Domain Routing)` ranges users granted this
 role are allowed to connect to and/or which they can connect from.
-
-.. versionadded:: 3.6

source/includes/fact-client-appname.rst

@@ -1,5 +1,3 @@
-.. versionadded:: 3.4
-
 The identifier of the client application which ran the operation. Use
 the :urioption:`appName` connection string option to set a custom value
 for the ``appName`` field.

source/includes/fact-runCommand-results.rst

@@ -36,8 +36,6 @@
        sessions <causal-consistency>`, MongoDB drivers use this time
        to automatically set the :ref:`afterClusterTime`.
 
-       .. versionadded:: 3.6
-
    * - ``$clusterTime``
 
      - A document that returns the signed cluster time. Cluster time is a
@@ -51,5 +49,3 @@
        - ``signature``: a document that contains the hash of the cluster time and the id
          of the key used to sign the cluster time.
 
-       .. versionadded:: 3.6
-

source/includes/table-sessions-commands.rst

@@ -21,34 +21,22 @@
 
      - Expire sessions before the sessions' timeout period.
 
-       .. versionadded:: 3.6
-
    * - :dbcommand:`killAllSessions`
 
      - Kill all sessions.
 
-       .. versionadded:: 3.6
-
    * - :dbcommand:`killAllSessionsByPattern`
 
      - Kill all sessions that match the specified pattern
 
-       .. versionadded:: 3.6
-
    * - :dbcommand:`killSessions`
 
      - Kill specified sessions.
 
-       .. versionadded:: 3.6
-
    * - :dbcommand:`refreshSessions`
 
      - Refresh idle sessions.
 
-       .. versionadded:: 3.6
-
    * - :dbcommand:`startSession`
 
      - Starts a new session.
-
-       .. versionadded:: 3.6

source/indexes.txt

@@ -211,8 +211,6 @@ with other MongoDB indexes.
 Partial Indexes
 ~~~~~~~~~~~~~~~
 
-.. versionadded:: 3.2
-
 :doc:`Partial indexes </core/index-partial>` only index the documents in
 a collection that meet a specified filter expression. By indexing a
 subset of the documents in a collection, partial indexes have lower

source/reference/aggregation-variables.txt

@@ -93,8 +93,6 @@ MongoDB offers the following system variables:
 
        For an example of its usage, see :ref:`remove-example`.
 
-       .. versionadded:: 3.6
-
    * - .. variable:: DESCEND
 
      - One of the allowed results of a :pipeline:`$redact` expression.