3.3.1 release notes for bug NCBC-3192 in 3.3.0

Author: jeffrymorris

modules/project-docs/pages/sdk-release-notes.adoc

@@ -15,14 +15,37 @@ For release notes, download links, and installation methods for 2.7 and earlier
 
 The full installation instructions that were previously on this page can now be found xref:sdk-full-installation.adoc[here].
 
+== Version 3.3.1 (29 April 2022)
+
+Version 3.3.1 is the second release of the 3.3 series. It contains a single ticket (NCBC-3192) and is a re-release of 3.3.0 with (NCBC-3192).
+
+https://packages.couchbase.com/clients/net/3.3/Couchbase-Net-Client-3.3.1.zip[Download] |
+https://docs.couchbase.com/sdk-api/couchbase-net-client-3.3.1[API Reference] |
+https://www.nuget.org/packages/CouchbaseNetClient/3.3.1[Nuget]
+
+=== Special Note
+
+* During a rebalance upgrade from 6.x (or any earlier version) to 7x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.  
+The solution is to either upgrade to 3.2.9 or greater, or to quiesce application processing so there are no writes until you have upgraded all nodes.  
+If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
+
+=== Fixed Issues
+
+* https://issues.couchbase.com/browse/NCBC-2543[NCBC-3192]: Erroneous InvalidArgumentException with default TLS settings
+
 == Version 3.3.0 (27 April 2022)
 
-Version 3.3.0 is the first release of the 3.3 series.
+Version 3.3.0 is the first release of the 3.3 series (delisted from NuGet 4/28/2022).
 
 https://packages.couchbase.com/clients/net/3.3/Couchbase-Net-Client-3.3.0.zip[Download] |
 https://docs.couchbase.com/sdk-api/couchbase-net-client-3.3.0[API Reference] |
 https://www.nuget.org/packages/CouchbaseNetClient/3.3.0[Nuget]
 
+=== Special Note
+
+* During a rebalance upgrade from 6.x (or any earlier version) to 7x, in mixed mode (where you are communicating with Couchbase Server whilst some but not all nodes are upgraded), there is a known issue where data may be written to the wrong location.  
+The solution is to either upgrade to 3.2.9 or greater, or to quiesce application processing so there are no writes until you have upgraded all nodes.  
+If you encounter a similar situation during migration and need help with mitigation, please contact our support team.
 
 === Fixed Issues