DOCSP-7955 remove versionchanged and versionadded tags for v3.0 ONLY repo-wide

Author: andf-mongodb

source/core/read-preference-mechanics.txt

@@ -69,14 +69,11 @@ Read Preference and Shards
 For sharded clusters that have replica set shards, :binary:`~bin.mongos`
 applies the read preference when reading from the shards. Server
 selection is governed by the :doc:`read preference
-</core/read-preference>` and :setting:`replication.localPingThresholdMs` settings.
+</core/read-preference>` and :setting:`replication.localPingThresholdMs`
+settings. The read preference is re-evaluated for each operation.
 
 .. include:: /includes/fact-3.4-added-maxStalenessSeconds.rst
 
-.. versionchanged:: 3.0
-
-   The read preference is re-evaluated for each operation.
-
 .. include:: /includes/extracts/server-selection-read-preference-sharded-clusters.rst
 
 .. [#default-threshold]  The default threshold value is 15 milliseconds.

source/core/security-users.txt

@@ -137,6 +137,8 @@ you enable access control, connect to the localhost interface and create
 the first user in the ``admin`` database. The first user must have
 privileges to create other users, such as a user with the
 :authrole:`userAdmin` or :authrole:`userAdminAnyDatabase` role.
+Connections using the localhost exception *only* have access to create
+the first user on the ``admin`` database.
 
 .. versionchanged:: 3.4
 
@@ -146,14 +148,6 @@ privileges to create other users, such as a user with the
    in LDAP. See :ref:`LDAP Authorization <security-ldap-external>` for more
    information.
 
-.. versionchanged:: 3.0
-
-   The localhost exception changed so that these connections *only*
-   have access to create the first user on the ``admin``
-   database. In previous versions, connections that gained access
-   using the localhost exception had unrestricted access to the
-   MongoDB instance.
-
 The localhost exception applies only when there are no users created in the
 MongoDB instance.
 

source/faq/concurrency.txt

@@ -10,8 +10,6 @@ FAQ: Concurrency
    :depth: 1
    :class: twocols
 
-.. versionchanged:: 3.0
-
 MongoDB allows multiple clients to read and write the same data.
 In order to ensure consistency, it uses locking and other
 :term:`concurrency control` measures to prevent multiple clients
@@ -72,12 +70,6 @@ lock modes are represented as follows:
 How granular are locks in MongoDB?
 ----------------------------------
 
-.. versionchanged:: 3.0
-
-
-Beginning with version 3.0, MongoDB ships with the :ref:`WiredTiger
-<storage-wiredtiger>` storage engine.
-
 .. include:: /includes/fact-wiredtiger-locks.rst
 
 How do I see the status of locks on my :binary:`~bin.mongod` instances?

source/includes/extracts-access-copydb.yaml

@@ -31,8 +31,6 @@ content: |
 ref: access-copydb-source-not-admin
 content: |
 
-   .. versionchanged:: 3.0
-
    If the source database is a non-``admin`` database, you must have
    privileges that specify :authaction:`find`,
    :authaction:`listCollections`, and :authaction:`listIndexes` actions
@@ -47,8 +45,6 @@ content: |
 ref: access-copydb-source-admin
 content: |
 
-   .. versionchanged:: 3.0
-
    If the source database is the ``admin`` database, you must have
    privileges that specify :authaction:`find`,
    :authaction:`listCollections`, and :authaction:`listIndexes` actions

source/includes/extracts-built-in-roles.yaml

@@ -144,8 +144,15 @@ content: |
 ref: built-in-roles-root
 content: |
   Provides access to the operations and all the resources of the
-  :authrole:`readWriteAnyDatabase`,
-  :authrole:`dbAdminAnyDatabase`, :authrole:`userAdminAnyDatabase`,
-  :authrole:`clusterAdmin`, :authrole:`restore`, and
-  :authrole:`backup` *combined*.
+  following roles *combined*:
+
+  - :authrole:`readWriteAnyDatabase`
+  - :authrole:`dbAdminAnyDatabase`
+  - :authrole:`userAdminAnyDatabase`
+  - :authrole:`clusterAdmin`
+  - :authrole:`restore`
+  - :authrole:`backup`
+  
+  Also provides the :authaction:`validate`
+  privilege action on ``system.`` collections.
 ...

source/includes/extracts-cloneCollection.yaml

@@ -5,11 +5,9 @@ content: |
    {{cloneCollection}} cannot be used if the `from` server has
    :doc:`authorization </core/authorization>` enabled.
 
-   .. versionchanged:: 3.0
-
-      If the given :term:`namespace` already exists in the destination
-      :binary:`~bin.mongod` instance, {{cloneCollection}} will return an
-      error.
+   If the given :term:`namespace` already exists in the destination
+   :binary:`~bin.mongod` instance, {{cloneCollection}} will return an
+   error.
 ---
 ref: cloneCollection-behavior-dbcommand
 content: |
@@ -27,8 +25,6 @@ content: |
 
    Namespace
    ~~~~~~~~~
-   
-   .. versionchanged:: 3.0
 
    If the given :term:`namespace` already exists in the destination
    :binary:`~bin.mongod` instance, {{cloneCollection}} will return an
@@ -57,12 +53,9 @@ content: |
    database name in the ``from`` server as the destination database.  If the
    collection does not exist in the source database, {{cloneCollection}} fails.
 
-
-   .. versionchanged:: 3.0
-
-      If the given :term:`collection` already exists in the destination
-      :binary:`~bin.mongod` instance, {{cloneCollection}} returns an
-      error.
+   If the given :term:`collection` already exists in the destination
+   :binary:`~bin.mongod` instance, {{cloneCollection}} returns an
+   error.
 
    Authorization
    ~~~~~~~~~~~~~

source/includes/extracts-fact-3.0-tools-drop-dbpath-support.yaml

@@ -13,12 +13,6 @@ content: |
     - the inserted document if ``upsert: true`` and no document matches the query;
 
     - otherwise, ``null``.
-
-  .. versionchanged:: 3.0
-
-     In previous versions, if for the update, ``sort`` is specified,
-     and ``upsert: true``, and the ``new`` option is not set or ``new:
-     false``, {{op}} instead of ``null``.
 ---
 ref: fact-findandmodify-command-return
 inherit:

source/includes/extracts-fact-findandmodify-return.yaml

@@ -75,9 +75,7 @@ MongoDB's comparison of :term:`BSON` objects uses the following order:
 Dates and Timestamps
 --------------------
 
-.. versionchanged:: 3.0.0
-   Date objects sort before Timestamp objects. Previously Date and
-   Timestamp objects sorted together.
+Date objects sort before Timestamp objects.
 
 Non-existent Fields
 -------------------

source/includes/extracts-parent-fact-3.0-tools-drop-dbpath-support.yaml

@@ -682,18 +682,7 @@ The following role provides full privileges on all resources:
    .. versionchanged:: 3.4
 
       The :authrole:`root` role includes privileges from the
-      :authrole:`backup` role.
-
-   .. versionchanged:: 3.0.7
-
-      The :authrole:`root` has the :authaction:`validate` privilege
-      action on ``system.`` collections. Previously, :authrole:`root`
-      does **not** include any access to collections that begin with the
-      ``system.`` prefix other than ``system.indexes`` and
-      ``system.namespaces``.
-
-      The :authrole:`root` role includes privileges from the
-      :authrole:`restore` role.
+      :authrole:`backup` and :authrole:`restore` roles.
 
 Internal Role
 -------------

source/includes/fact-3.0-mongoexport-drop-csv-option.rst

@@ -390,8 +390,6 @@ Output
 
 .. data:: collStats.indexDetails
 
-   .. versionadded:: 3.0.0
-
    A document that reports data from the :ref:`WiredTiger <storage-wiredTiger>`
    storage engine for each index in the collection. Other storage engines will
    return an empty document.
@@ -464,8 +462,6 @@ Output
 
 .. data:: collStats.wiredTiger
 
-   .. versionadded:: 3.0.0
-
    :data:`~collStats.wiredTiger` only appears when using the
    WiredTiger storage engine.
 

source/includes/fact-majority-write-concern-change.rst

@@ -130,8 +130,6 @@ Definition
 
         - Optional. Available for the WiredTiger storage engine only.
 
-          .. versionadded:: 3.0
-          
           Allows users to specify configuration to the storage engine on a
           per-collection basis when creating a collection. The value of the
           ``storageEngine`` option should take the following form:
@@ -451,8 +449,6 @@ The same operation on a collection that uses simple binary collation
 Specify Storage Engine Options
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 3.0
-
 You can specify collection-specific storage engine configuration
 options when you create a collection with
 :method:`db.createCollection()`. Consider the following operation:

source/includes/fact-remove-dropDups-option.rst

@@ -88,9 +88,6 @@ Definition
 
    Each document in the ``indexes`` array can take the following fields:
 
-   .. include:: /includes/fact-remove-dropDups-option.rst
-
-
    .. list-table::
       :header-rows: 1
       :widths: 20 20 80
@@ -281,11 +278,8 @@ Definition
           support replica sets with members that use different storage
           engines.
 
-          .. versionadded:: 3.0
-          
-          
-          
-   
+
+
       * - ``weights``
 
         - document

source/includes/fact-mongodb30-upsert-id.rst renamed to source/includes/fact-upsert-id.rst

@@ -684,13 +684,9 @@ Output Fields
    is ``true`` if the operation has started or ``false`` if the
    operation is idle, such as an idle connection or an internal thread
    that is currently idle. An operation can be active even if the
-   operation has yielded to another operation.
-
-   .. versionchanged:: 3.0
-
-      For some inactive background threads, such as an inactive
-      ``signalProcessingThread``, MongoDB suppresses various empty
-      fields.
+   operation has yielded to another operation. For some inactive
+   background threads, such as an inactive ``signalProcessingThread``,
+   MongoDB suppresses various empty fields.
 
 .. data:: currentOp.secs_running
 
@@ -902,8 +898,6 @@ Output Fields
 
 .. data:: currentOp.locks
 
-   .. versionchanged:: 3.0
-
    The :data:`~currentOp.locks` document reports the type and mode of
    locks the operation currently holds. The possible lock types are as
    follows:

source/includes/fact-wiredtiger-compatibility-with-old-shells.rst

@@ -15,8 +15,6 @@ Definition
 
 .. dbcommand:: explain
 
-   .. versionadded:: 3.0
-
    The :dbcommand:`explain` command provides information on the
    execution of the following commands: :dbcommand:`aggregate`,
    :dbcommand:`count`, :dbcommand:`distinct`, :dbcommand:`find`,

source/includes/members-used-to-allow-multiple-votes.rst

@@ -64,8 +64,6 @@ Definition
           latest write propagates to a majority of the voting replica set
           members.
 
-          .. include:: /includes/fact-majority-write-concern-change.rst
-          
           If using ``w``, you should also use ``wtimeout``. Specifying
           a value for ``w`` without also providing a ``wtimeout`` may cause
           :dbcommand:`getLastError` to block indefinitely.

source/reference/bson-type-comparison-order.txt

@@ -317,8 +317,6 @@ of a replica set:
 
 .. data:: isMaster.electionId
 
-   .. versionadded:: 3.0
-
    A unique identifier for each election. Included only in the output
    of :dbcommand:`isMaster` for the :term:`primary`. Used by clients
    to determine when elections occur.

source/reference/built-in-roles.txt

@@ -10,8 +10,6 @@ listCollections
    :depth: 1
    :class: singlecol
 
-.. versionadded:: 3.0.0
-
 Definition
 ----------
 

source/reference/command/collStats.txt

@@ -10,8 +10,6 @@ listIndexes
    :depth: 1
    :class: singlecol
 
-.. versionadded:: 3.0.0
-
 Definition
 ----------
 

source/reference/command/create.txt

@@ -45,8 +45,6 @@ Definition
 Behavior
 --------
 
-.. versionchanged:: 3.0.0
-
 The :setting:`systemLog.logRotate` setting or :option:`--logRotate <mongod --logRotate>` option
 specify :dbcommand:`logRotate`'s behavior.