WHATSNEW: prepare for 4.0 beta8

WHATSNEW.txt

@@ -1,4 +1,4 @@
-What's new in Samba 4.0 beta7
+What's new in Samba 4.0 beta8
 =============================
 
 Samba 4.0 will be the next version of the Samba suite and incorporates
@@ -11,7 +11,7 @@ and above.
 WARNINGS
 ========
 
-Samba 4.0 beta7 is not a final Samba release, however we are now making
+Samba 4.0 beta8 is not a final Samba release, however we are now making
 good progress towards a Samba 4.0 release.  However, this is expected to be the
 last beta release before we start on our release candidate series.
 
@@ -77,7 +77,7 @@ the longer term.
 For pure file server work, the binaries users would expect from that
 series (nmbd, winbindd, smbpasswd) continue to be available.  When
 running an AD DC, you only need to run 'samba' (not
-nmbd/smbd/winbind), as the required services are co-ordinated by this
+nmbd/smbd/winbind), as the required services are co-coordinated by this
 master binary.
 
 As DNS is an integral part of Active Directory, we also provide a DNS
@@ -98,56 +98,51 @@ Python programs to interface to Samba's internals, and many tools and
 internal workings of the DC code is now implemented in python.
 
 
-CHANGES SINCE beta6
+CHANGES SINCE beta7
 =====================
 
-For a list of changes since beta6, please see the git log.
+For a list of changes since beta7, please see the git log.
 
 $ git clone git://git.samba.org/samba.git
 $ cd samba.git
-$ git log samba-4.0.0beta6..samba-4.0.0beta7
+$ git log samba-4.0.0beta7..samba-4.0.0beta8
 
 Some major user-visible changes include:
 
-- ACLs are now set during provision at the POSIX layer for the sysvol
-  share.  This allows group policies to be modified by Domain
-  Administrators (Policy Administrators) that are not the actual
-  Administrator user.
+- A fix for a segfault/abort on startup of the 'samba' binary in the
+  credentials_secrets code. 
 
-- A number of verified fixes for expanding memory use across the AD
-  domain controller, including in the Bind9 DLZ module.
+- A fix for samba-tool classicupgrade of pdb_ldap-based domains
 
-- A fix for bug #9097 (the winbind in the AD DC would lock up under
-  parallel requests).
+- A fix for samba-tool domain exportkeyab only exporting DES keys
 
-- wbinfo --ping-dc now returns helpful information on what failed and
-  against which DC it failed
+- Printing is now enabled on the AD DC
 
-- SMB3 encryption support
+- Fix bug #9124 - Samba fails to set "inherited" bit on inherited ACE's.
 
-- New 'samba-tool ntacl' commands:
-  - samba-tool ntacl sysvolreset
-  - samba-tool ntacl sysvolcheck
+- We now avoid printing secret attributes (such as unicodePwd and
+  suppliementalCredentials) in ldb trace logs
 
-Less visible, but important changes under the hood include:
+- s3-printing: fix bug 9123 lprng job tracking errors
 
-- Continued work to support SMB2 and SMB3
-
-- Continued work to use async IO to improve file server performance.
-
-- Patches to ensure that talloc_tos() and talloc_stackframe() are
-  always used correctly.
-
-- We can now test the implementation of NT -> POSIX ACL mapping in a
-  unit test with VFS bindings exposing both to python.  We also store
-  the posix ACL in a tdb during make test, allowing testing of this
-  feature on all platforms, regardless of local FS settings.
-
-- Python bindings for the source3 async libsmb library (for use in testing)
+- A fix for building with MIT Kerberos
 
 KNOWN ISSUES
 ============
 
+- 'samba-tool domain classicupgrade' will fail when setting ACLs on
+  the GPO folders with NT_STATUS_INVALID_ONWER in the default
+  configuration.  This happens if, as is typical a 'domain admins'
+  group (-512) is mapped in the passdb backend being upgraded.  This
+  is because the group mapping to a GID only prevents Samba from
+  allocating a uid for that group.  The uid is needed so the 'domain
+  admins' group can own the GPO file objects.
+
+  To work around this issue, remove the 'domain admins' group before
+  upgrade, as it will be re-created automatically.  You will
+  of course need to fill in the group membership again.  A future release
+  will make this automatic, or find some other workaround.
+
 - This release makes the s3fs file server the default, as this is the
   file server combination we will use for the Samba 4.0 release.
 
@@ -161,7 +156,7 @@ KNOWN ISSUES
   this partition is not yet reliable.
 
 - Replication may fail on FreeBSD due to getaddrinfo() rejecting names
-  containing _.  A workaround will be in a future next beta.
+  containing _.  A workaround will be in a future beta.
 
 - upgradeprovision should not be run when upgrading to this release
   from a recent release.  No important database format changes have