Fix WHATSNEW.

In particular, I can't find the DCOM code, so presumably it's still in
a branch.

Andrew Bartlett
(This used to be commit 00ad3f8a6dfb742113c1eeedb4c9a81b0a64947e)

1 files changed, 5 insertions, 6 deletions

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 7ec83acb16..9b72a77c45 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -10,8 +10,8 @@ Samba 4 is currently not yet in a state where it is usable in
 production environments. Note the WARNINGS below, and the STATUS file,
 which aims to document what should and should not work.
 
-Samba4 alpha4 follows on from our third alpha release since September
-last year. 
+Samba4 alpha4 follows on from the alpha release series we have been
+publishing since September last year.
 
 WARNINGS
 ========
@@ -99,13 +99,12 @@ continued to evolve, but you may particularly notice these areas:
   group policy, domain joins and logons due to an improved
   implementation of CLDAP and the 'netlogon' mailslot datagrams.
 
-  DCOM: In preperation for merging the Samba4-based 'python-wmi'
-  implementation of a WMI client, Samba's previously abandoned DCOM
-  client has been revived. 
-
   SMB2: The Samba4 SMB2 server and testsuite have been greatly
   improved, but the SMB2 server remains off by default.
 
+  Secure DNS update: Configuration for GSS-TSIG updates of DNS records
+  is now generated by the provision script.
+
 These are just some of the highlights of the work done in the past few
 months.  More details can be found in our GIT history.