DOCSP-22135 FCV page update: add v6.0 and remove EOL versions (#1094)

* DOCSP-22135 add v6.0 and remove EOL versions

* DOCSP-22135 relocating warning & fixing ref

* DOCSP-22135 removing eol versions from list

* DOCSP-22135 removed include

* DOCSP-22135 removed include

* DOCSP-22135 add include file back

Co-authored-by: Jocelyn Mendez <[email protected]>

Author: jocelyn-mendez1

source/includes/featureCompatibility-caveat.rst

@@ -0,0 +1,8 @@
+Enabling these backwards-incompatible features can complicate the 
+downgrade process since you must remove any persisted backwards-incompatible 
+features before you downgrade.
+
+It is recommended that after upgrading, you allow your deployment to run 
+without enabling these features for a burn-in period to ensure the 
+likelihood of downgrade is minimal. When you are confident that the 
+likelihood of downgrade is minimal, enable these features.

source/includes/featureCompatibility-caveat.txt

@@ -5,6 +5,13 @@
    * - Deployments
      - ``featureCompatibilityVersion``
 
+   * - For new 6.0 deployments
+     - ``"6.0"``
+
+   * - For 6.0 deployments :ref:`upgraded from 5.0 <6.0-upgrade>`
+     
+     - ``"5.0"`` until you :dbcommand:`setFeatureCompatibilityVersion` to ``"6.0"``. 
+
    * - For new 5.0 deployments
      - ``"5.0"``
 
@@ -25,26 +32,3 @@
    * - For 4.2 deployments :ref:`upgraded from 4.0 <4.2-upgrade>`
 
      - ``"4.0"`` until you :dbcommand:`setFeatureCompatibilityVersion` to ``"4.2"``.
-
-   * - For new 4.0 deployments
-     - ``"4.0"``
-
-   * - For 4.0 deployments :ref:`upgraded from 3.6 <4.0-upgrade>`
-
-     - ``"3.6"`` until you :dbcommand:`setFeatureCompatibilityVersion` to ``"4.0"``.
-
-   * - For new 3.6 deployments
-     - ``"3.6"``
-
-   * - For 3.6 deployments :ref:`upgraded from 3.4 <3.6-upgrade>`
-   
-     - ``"3.4"`` until you :dbcommand:`setFeatureCompatibilityVersion`
-       to ``"3.6"``.
-
-   * - For new 3.4 deployments
-     - ``"3.4"``
-
-   * - For 3.4 deployments :ref:`upgraded from 3.2 <3.4-upgrade>`
-   
-     - ``"3.2"`` until you :dbcommand:`setFeatureCompatibilityVersion`
-       to ``"3.4"``.

source/includes/list-table-featureCompatibilityVersion-defaults.rst

@@ -20,6 +20,17 @@ Definition
    :dbcommand:`setFeatureCompatibilityVersion` against the ``admin``
    database.
 
+.. warning::
+
+   Enabling backwards-incompatible features can complicate the
+   downgrade process since you must remove any persisted
+   backwards-incompatible features before you downgrade.
+
+   It is recommended that after upgrading, you allow your deployment to
+   run without enabling backwards-incompatible features for a burn-in period 
+   to ensure the likelihood of downgrade is minimal. When you are confident 
+   that the likelihood of downgrade is minimal, enable these features.
+
 Syntax
 ------
 
@@ -41,97 +52,39 @@ The values for the ``version`` are:
    * - Version
      - Description
 
-   * - ``"5.0"``
+   * - ``"6.0"``
+
+     - *Available on MongoDB 6.0 Deployments* 
 
+       Enables the :ref:`6.0 features that persist data incompatible 
+       with MongoDB 5.0 <6.0-downgrade-considerations>`.
+
+   * - ``"5.0"``
 
      - *Available on MongoDB 5.0 Deployments*
 
        Enables the :ref:`5.0 features that persist data incompatible
        with MongoDB 4.4 <5.0-compatibility-enabled>`.
 
-       .. include:: /includes/featureCompatibility-caveat.rst
-
    * - ``"4.4"``
 
-
      - *Available on MongoDB 4.4 and 5.0 Deployments*
 
        Enables the :ref:`4.4 features that persist data incompatible
        with MongoDB 4.2 <4.4-compatibility-enabled>`.
 
-       .. include:: /includes/featureCompatibility-caveat.rst
-
-
    * - ``"4.2"``
 
-
      - *Available on MongoDB 4.2 and 4.4 Deployments*
 
        Enables the :ref:`4.2 features that persist data incompatible
        with MongoDB 4.0 <4.2-compatibility-enabled>`.
 
-       .. include:: /includes/featureCompatibility-caveat.rst
-
        - If set on MongoDB 4.4 deployments,
            Disables the :ref:`4.4 features that persist data
            incompatible with MongoDB 4.2
            <4.4-compatibility-enabled>`.
 
-   * - ``"4.0"``
-
-     - *Available on MongoDB 4.0 and 4.2 Deployments*
-
-       - If set on MongoDB 4.0 deployments,
-           Enables the :ref:`4.0 features that persist data incompatible
-           with MongoDB 3.6 <4.0-compatibility-enabled>`.
-
-           .. include:: /includes/featureCompatibility-caveat.rst
-
-       - If set on MongoDB 4.2 deployments,
-           Disables the :ref:`4.2 features that persist data
-           incompatible with MongoDB 4.0
-           <4.2-compatibility-enabled>`.
-
-   * - ``"3.6"``
-
-     - *Available on MongoDB 3.6 and 4.0 Deployments*
-
-       - If set on MongoDB 3.6 deployments,
-           Enables the :ref:`3.6 features that persist data
-           incompatible with MongoDB 3.4
-           <3.6-compatibility-enabled>`.
-
-           .. include:: /includes/featureCompatibility-caveat.rst
-
-       - If set on MongoDB 4.0 deployments,
-           Disables the :ref:`4.0 features that persist data
-           incompatible with MongoDB 3.6
-           <4.0-compatibility-enabled>`.
-
-
-   * - ``"3.4"``
-
-     - *Available on MongoDB 3.4 and MongoDB 3.6 Deployments*
-
-       - If set on MongoDB 3.4 deployments,
-           Enables the :ref:`3.4 features that persist data
-           incompatible with MongoDB 3.2
-           <3.4-compatibility-enabled>`.
-
-           .. include:: /includes/3.4-featureCompatibility-caveat.rst
-
-       - If set on MongoDB 3.6 deployments,
-           Disables the :ref:`3.6 features that persist data
-           incompatible with MongoDB 3.4
-           <3.6-compatibility-enabled>`.
-
-   * - ``"3.2"``
-
-     - *Available on MongoDB 3.4 Deployments*
-
-       Disables the :ref:`3.4 features that persist data
-       incompatible with MongoDB 3.2 <3.4-compatibility-enabled>`.
-
 The optional ``writeConcern`` specifies the write concern
 :ref:`wc-wtimeout` value in milliseconds:
 
@@ -257,6 +210,53 @@ depending on the current state of the :binary:`~bin.mongod`:
 
 .. _set-fcv:
 
+Set Feature Compatibility Version on MongoDB 6.0 Deployments
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Enable 6.0 Backwards Incompatible Features
+``````````````````````````````````````````
+
+To enable the :ref:`6.0 features that persist data incompatible with
+MongoDB 5.0 <6.0-downgrade-considerations>`, set the feature compatibility
+to ``"6.0"`` on the MongoDB 6.0 deployment:
+
+.. note::
+
+   Run the :dbcommand:`setFeatureCompatibilityVersion` command against
+   the ``admin`` database.
+
+   .. include:: /includes/list-run-command-targets.rst
+
+.. code-block:: javascript
+
+   db.adminCommand( { setFeatureCompatibilityVersion: "6.0" } )
+
+Disable 6.0 Backwards Incompatible Features
+```````````````````````````````````````````
+
+To disable the :ref:`6.0 features that persist data incompatible with
+MongoDB 5.0 <6.0-downgrade-considerations>`, set the feature compatibility
+to ``"5.0"`` on the MongoDB 6.0 deployment:
+
+.. note::
+
+   Run the :dbcommand:`setFeatureCompatibilityVersion` command against
+   the ``admin`` database.
+
+   .. include:: /includes/list-run-command-targets.rst
+
+   - ``"5.0"`` featureCompatibilityVersion is supported on MongoDB
+     5.0 and MongoDB 6.0 deployments only.
+
+.. code-block:: javascript
+
+   db.adminCommand( { setFeatureCompatibilityVersion: "5.0" } )
+
+If run as part of the downgrade process from MongoDB 6.0 to MongoDB 
+5.0, you must also remove all persisted features that are
+:ref:`incompatible <6.0-downgrade-considerations>` with 5.0. See the
+appropriate downgrade procedures.
+
 Set Feature Compatibility Version on MongoDB 5.0 Deployments
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -372,126 +372,6 @@ to ``"4.2"`` on the MongoDB 4.2 deployment:
 
    db.adminCommand( { setFeatureCompatibilityVersion: "4.2" } )
 
-Disable 4.2 Backwards Incompatible Features
-```````````````````````````````````````````
-
-To disable the :ref:`4.2 features that persist data incompatible with
-MongoDB 4.0 <4.2-compatibility-enabled>`, set the feature compatibility
-to ``"4.0"`` on the MongoDB 4.2 deployment:
-
-.. note::
-
-   Run the :dbcommand:`setFeatureCompatibilityVersion` command against
-   the ``admin`` database.
-
-   .. include:: /includes/list-run-command-targets.rst
-
-   - ``"4.0"`` featureCompatibilityVersion is supported on MongoDB
-     4.0 and MongoDB 4.2 deployments only.
-
-.. code-block:: javascript
-
-   db.adminCommand( { setFeatureCompatibilityVersion: "4.0" } )
-
-If run as part of the downgrade process from MongoDB 4.2 to MongoDB
-4.0, you must also remove all persisted features that are
-:ref:`incompatible <4.2-compatibility-enabled>` with 4.0. See the
-appropriate downgrade procedures.
-
-Set Feature Compatibility Version on MongoDB 4.0 Deployments
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Enable 4.0 Backwards Incompatible Features
-``````````````````````````````````````````
-
-To enable the :ref:`4.0 features that persist data incompatible with
-MongoDB 3.6 <4.0-compatibility-enabled>`, set the feature compatibility
-to ``"4.0"`` on the MongoDB 4.0 deployment:
-
-.. note::
-
-   Run the :dbcommand:`setFeatureCompatibilityVersion` command against
-   the ``admin`` database.
-
-   .. include:: /includes/list-run-command-targets.rst
-
-.. code-block:: javascript
-
-   db.adminCommand( { setFeatureCompatibilityVersion: "4.0" } )
-
-Disable 4.0 Backwards Incompatible Features
-```````````````````````````````````````````
-
-To disable the :ref:`4.0 features that persist data incompatible with
-MongoDB 3.6 <4.0-compatibility-enabled>`, set the feature compatibility
-to ``"3.6"`` on the MongoDB 4.0 deployment:
-
-.. note::
-
-   Run the :dbcommand:`setFeatureCompatibilityVersion` command against
-   the ``admin`` database.
-
-   .. include:: /includes/list-run-command-targets.rst
-
-   - ``"3.6"`` featureCompatibilityVersion is supported on MongoDB
-     3.6 and MongoDB 4.0 Deployments Only.
-
-.. code-block:: javascript
-
-   db.adminCommand( { setFeatureCompatibilityVersion: "3.6" } )
-
-If run as part of the downgrade process from MongoDB 4.0 to MongoDB
-3.6, you must also remove all persisted features that are
-:ref:`incompatible <4.0-compatibility-enabled>` with 3.6. See the
-appropriate downgrade procedures.
-
-Set Feature Compatibility Version on MongoDB 3.6 Deployments
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Enable 3.6 Backwards Incompatible Features
-``````````````````````````````````````````
-
-To enable the :ref:`3.6 features that persist data incompatible with
-MongoDB 3.4 <3.6-compatibility-enabled>`, set the feature compatibility
-to ``"3.6"`` on the MongoDB 3.6 deployment:
-
-.. note::
-
-   Run the :dbcommand:`setFeatureCompatibilityVersion` command against
-   the ``admin`` database.
-
-   .. include:: /includes/list-run-command-targets.rst
-
-.. code-block:: javascript
-
-   db.adminCommand( { setFeatureCompatibilityVersion: "3.6" } )
-
-Disable 3.6 Backwards Incompatible Features
-```````````````````````````````````````````
-
-To disable the :ref:`3.6 features that persist data incompatible with
-MongoDB 3.4 <3.6-compatibility-enabled>`, set the feature compatibility
-to ``"3.4"`` on the MongoDB 3.6 deployment:
-
-.. note::
-
-   Run the :dbcommand:`setFeatureCompatibilityVersion` command against
-   the ``admin`` database.
-
-   .. include:: /includes/list-run-command-targets.rst
-
-   - ``"3.4"`` featureCompatibilityVersion is supported on MongoDB
-     3.6 and MongoDB 3.4 Deployments Only.
-
-.. code-block:: javascript
-
-   db.adminCommand( { setFeatureCompatibilityVersion: "3.4" } )
-
-If run as part of the downgrade process from MongoDB 3.6 to MongoDB
-3.4, you must also remove all persisted features that are
-:ref:`incompatible <3.6-compatibility-enabled>` with 3.4. See the
-appropriate downgrade procedures.
-
 Set Write Concern Timeout
 ~~~~~~~~~~~~~~~~~~~~~~~~~