DOCSP-33175 Remove 1.6 prerelease content (#162)

* DOCSP-33175 Removes 1.6 content for prerelease

* Removes exclude documentation

* Removes start mention

* Restores patch limitation

* Removes 1.6 from release notes toc

* Fixes per Ajay

* Fixes per Ajay

* Fixes per Ajay

* Fixes per jtcovan

Author: kennethdyer

source/reference/api/start.txt

@@ -143,15 +143,6 @@ Request Body Parameters
 
        .. versionadded:: 1.1
 
-   * - ``excludeNamespaces``
-     - array
-     - Optional
-     - Filters the databases or collections to exclude from sync.
-
-       .. include:: /includes/api/facts/namespace-explanation.rst
-
-       .. versionadded:: 1.6
-
    * - ``reversible``
      - boolean
      - Optional

source/reference/collection-level-filtering.txt

@@ -18,34 +18,20 @@ Filtered Sync
 .. include:: /includes/api/facts/filtering-intro.rst
 
 Starting in 1.1, ``mongosync`` supports inclusion filters to specify which
-databases and collections to include in sync.  Starting in 1.6, ``mongosync``
-also supports exclusion filters and regular expressions.
+databases and collections to include in sync.  
 
 - With inclusion filters, ``mongosync`` syncs matching
   databases and collections.
-- With exclusion filters, ``mongosync`` syncs all databases
-  and collections, except for those that match the filters.
-- With both inclusion and exclusion filters, ``mongosync`` only syncs
-  databases and collections that match the inclusion filters then excludes
-  any that also match the exclusion filters.
 - With no filters, ``mongosync`` syncs all databases and collections.
 
 .. _c2c-filter-syntax:
 
 Filter Syntax
 -------------
 
-The :ref:`c2c-api-start` API endpoint accepts two fields that configure 
-filtered sync: ``includeNamespaces`` and ``excludeNamespaces``.
-Each field takes an array of filters that specify the databases and collections 
-to include or exclude from sync.
-
-.. note::
-
-   If the :ref:`c2c-api-start` call uses both ``includeNamespaces`` and 
-   ``excludeNamespaces`` parameters, ``mongosync`` first matches databases
-   and collections from the inclusion filters, then excludes those that
-   also match an exclusion filter.
+The :ref:`c2c-api-start` API endpoint accepts one field to configure filtered
+sync: ``includeNamespaces``.  This field takes an array of filters to specify
+the databases and collections to include in the sync.
 
 Filters have the following syntax:
 
@@ -58,38 +44,10 @@ Filters have the following syntax:
           "collections": [
              "<collection-name>"
           ]
-          "databaseRegex": {
-             "pattern": "<regex-pattern>",
-             "options": "<options>"
-          },
-          "collectionRegex": {
-             "pattern": "<regex-pattern>",
-             "options": "<options>"
-          }
-       }
-    ],
-    "excludeNamespaces": [
-       {
-          "database": "<database-name>",
-          "collections": [
-             "<collection-name>"
-          ]
-          "databaseRegex": {
-             "pattern": "<regex-pattern>",
-             "options": "<options>"
-          },
-          "collectionRegex": {
-             "pattern": "<regex-pattern>",
-             "options": "<options>"
-          }
        }
     ]
 
-Filters must include either the ``database`` field or the ``databaseRegex`` field.
-
-If you need the filter to match specific collections, you can use either 
-the ``collections`` array to specify collections individually or define 
-a regular expression using the ``collectionRegex`` field.
+Filters must include the ``database`` field. 
 
 .. _c2c-configure-filter:
 
@@ -116,43 +74,33 @@ Configure a Filter
 
    .. step:: Create a Filter.
 
-      The :ref:`c2c-api-start` API accepts two parameters that configure
+      The :ref:`c2c-api-start` API accepts a parameter to configure a series of
       optional filters: 
 
       - The ``includeNamespaces`` parameter takes an array of filters, which
         are used to determines which databases and collections ``mongosync`` 
         should include in the sync.
-      - The ``excludeNamespaces`` parameter takes an array of filters, which
-        are used to determine which databases and collections ``mongosync``
-        should exclude from the sync.
 
       If you don't specify a filter, ``mongosync`` performs a full cluster
       sync.
 
-      Create inclusion and/or exclusion filters to identify the databases and
+      Create inclusion filters to identify the databases and
       collections you want to sync.
 
       For example, this inclusion filter would configure ``mongosync`` to only
-      sync collections whose names begin with ``accounts_`` from the ``sales`` 
-      database, except for the ``accounts_old`` collection:
+      sync ``accounts_us`` and ``accounts_eu`` collections in the ``sales`` 
+      database.
 
       .. code-block:: json
 
          "includeNamespaces": [
             {
                "database": "sales",
-               "collectionRegex": {
-                  "pattern": "^accounts_.+$",
-                  "options": "ms"
-               }
-         ],
-         "excludeNamespaces": [
-             {
-                 "database": "sales",
-                 "collections": [
-                     "accounts_old"
-                 ]
-             }
+               "collections": [
+                   "accounts_us",
+                   "accounts_eu",
+               ]
+            }
          ]
 
       For more information on filters, see :ref:`c2c-filter-syntax`. 
@@ -350,8 +298,3 @@ Adding and Renaming Collections While Syncing
 
 .. include:: /includes/example-filter-collection-with-renaming.rst
 
-.. toctree::
-   :hidden:
-
-   /reference/collection-level-filtering/filter-regex
-

source/reference/collection-level-filtering/filter-regex.txt

@@ -29,19 +29,10 @@ General Limitations
   .. include:: /includes/fact-minimum-versions.rst
 
 - ``mongosync`` does not support MongoDB rapid releases such as 6.1 or
-  6.2. Only major MongoDB releases such as 6.0 or 7.0. are supported.
+  6.2. The minimum supported server version is MongoDB 6.0.5.
   For more information on MongoDB versioning, see
   :ref:`release-version-numbers`.
-- The source and destination clusters must have the same major and minor
-  release version, but can have different patch releases.
-
-  For example,
-  - ``mongosync`` supports sync from a MongoDB 6.0.8 source cluster to a
-    destination cluster using MongoDB 6.0.9, since these are patch releases 
-    of the same major release.
-  - ``mongosync`` does not support sync from a MongoDB 6.0.9 source cluster to 
-    a destination cluster using MongoDB 7.0.0, since they have different major
-    versions.
+- The source and destination clusters must have the same release version.
 - The minimum supported :dbcommand:`Feature Compatibility Version
   <setFeatureCompatibilityVersion>` is 6.0.
 - The source and destination clusters must have the same Feature

source/reference/limitations.txt

@@ -60,10 +60,9 @@ Same Server Version
 ~~~~~~~~~~~~~~~~~~~
 
 {+c2c-product-name+} only supports syncing between the same version of
-MongoDB Server. The major and minor :ref:`server version numbers
-<release-version-numbers>` must be the same on both clusters.
-Starting in ``mongosync`` 1.6.0, the source and destination cluster
-can use different patch releases of the same major and minor version.
+MongoDB Server. All three :ref:`server version numbers
+<release-version-numbers>`, including the patch number, must be the
+same on both servers.
 
 Support Lifecycle 
 ~~~~~~~~~~~~~~~~~

source/reference/versioning.txt

@@ -8,7 +8,6 @@ Release Notes
 .. toctree::
    :titlesonly: 
 
-   /release-notes/1.6
    /release-notes/1.5
    /release-notes/1.4
    /release-notes/1.3