WHATSNEW: Update for Bug 13676 changes in Samba 4.10

Although it's unlikely that users will be using the 'smb' Python
bindings, it's probably worth noting in the release notes that these
bindings will be deprecated in future releases.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=13676

Signed-off-by: Tim Beale <timbeale@catalyst.net.nz>
Reviewed-by: Jeremy Allison <jra@samba.org>

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 267cc5402a9d75df4eefb0c51de297c7d63cb613..493d9c2b35f1303be9a99bc4a4cb38f58d270e49 100644 (file)
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -153,7 +153,13 @@ log entries has been removed to make the parsing of the JSON log messages
 easier. JSON log entries now start with 2 spaces followed by an opening brace
 i.e. "  {"
 
+SMBv2 samba-tool support
+------------------------
 
+On previous releases, some samba-tool commands would not work against a remote
+DC that had SMBv1 disabled. SMBv2 support has now been added for samba-tool.
+The affected commands are 'samba-tool domain backup|rename' and the
+'samba-tool gpo' set of commands. Refer also bug #13676.
 
 
 REMOVED FEATURES
@@ -176,6 +182,14 @@ samba_backup
 The samba_backup script has been removed. This has now been replaced by the
 'samba-tool domain backup offline' command.
 
+SMB client Python bindings
+--------------------------
+
+The SMB client python bindings are now deprecated and will be removed in future
+Samba releases. This will only affects users that may have used the Samba
+Python bindings to write their own utilities, i.e. users with a custom Python
+script that includes the line 'from samba import smb'.
+
 smb.conf changes
 ================