Update WHATSNEW towards an alpha5 release.

Andrew Bartlett

1 files changed, 17 insertions, 33 deletions

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 8f17e981feb..562a331b320 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -1,4 +1,4 @@
-What's new in Samba 4 alpha4
+What's new in Samba 4 alpha5
 ============================
 
 Samba 4 is the ambitious next version of the Samba suite that is being
@@ -6,13 +6,13 @@ developed in parallel to the stable 3.0 series. The main emphasis in
 this branch is support for the Active Directory logon protocols used
 by Windows 2000 and above.
 
-Samba4 alpha4 follows on from the alpha release series we have been
+Samba4 alpha5 follows on from the alpha release series we have been
 publishing since September 2007
 
 WARNINGS
 ========
 
-Samba4 alpha4 is not a final Samba release.  That is more a reference
+Samba4 alpha5 is not a final Samba release.  That is more a reference
 to Samba4's lack of the features we expect you will need than a
 statement of code quality, but clearly it hasn't seen a broad
 deployment yet.  If you were to upgrade Samba3 (or indeed Windows) to
@@ -68,15 +68,18 @@ CHANGES SINCE Alpha4
 In the time since Samba4 Alpha4 was released in June 2008, Samba has
 continued to evolve, but you may particularly notice these areas:
 
-(TODO: update list when closer to a release)
+  LDAP backend support restored (issues preventing the use of the LDAP
+  backend in alpha4 have been addressed)
 
-  Python Bindings: Bindings for Python are now used for all internal
-  scripting, and the system python installation is used to run all
-  Samba python scripts (in place of smbpython found in the previous
-  alpha).
+  SMB2 Support:  The SMB2 server, while still disabled, has improved,
+  and now supports SMB2 signing. 
 
-  As such Python is no longer optional, and configure will generate an
-  error if it cannot locate an appropriate Python installation.
+  OpenChange support:  Updates have been made since alpha4 to better
+  support OpenChange's use of Samba4's libraries. 
+
+  Faster ldb loading:  A fix to avoid calling 'init_module' (which was
+  not defined by Samba modules, but was by the C library) will fix
+  some of the slowness in authentication. 
 
   SWAT Remains Disabled: Due to a lack of developer time and without a
   long-term web developer to maintain it, the SWAT web UI remains been
@@ -85,26 +88,6 @@ continued to evolve, but you may particularly notice these areas:
   GNU Make: To try and simplfy our build system, we rely on GNU Make
   to avoid autogenerating a massive single makefile. 
 
-  Registry: Samba4's registry library has continued to improve.
-
-  ID mapping: Samba4 uses the internal ID mapping in winbind for all
-  but a few core users.  Samba users should not appear in /etc/passwd,
-  as Samba will generate new user and group IDs regradless. 
-
-  NTP: Samba4 can act as a signing server for the ntp.org NTP deamon,
-  allowing NTPd to reply using Microsoft's non-standard signing
-  scheme.  A patch to make NTPd talk to Samba for this purpose has
-  been submitted to the ntp.org project.
-
-  CLDAP: Users should experience less arbitary delays and more success with
-  group policy, domain joins and logons due to an improved
-  implementation of CLDAP and the 'netlogon' mailslot datagrams.
-
-  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.
@@ -130,13 +113,14 @@ KNOWN ISSUES
 
 - Clock Synchronisation is critical.  Many 'wrong password' errors are
   actually due to Kerberos objecting to a clock skew between client
-  and server.  (The NTP work is partly to assist with this problem).
+  and server.  (The NTP work in the previous alpha is partly to assist
+  with this problem).
 
-- Samba4 alpha4 is currently only portable to recent Linux
+- Samba4 alpha5 is currently only portable to recent Linux
   distributions.  Work to return support for other Unix varients is
   expected during the next alpha cycle
 
-- Samba4 alpha4 is incompatible with GnuTLS 2.0, found in Fedora 9 and
+- Samba4 alpha5 is incompatible with GnuTLS 2.0, found in Fedora 9 and
   recent Ubuntu releases.  GnuTLS use may be disabled using the
   --disable-gnutls argument to ./configure. (otherwise 'make test' and
   LDAPS operations will hang).