WHATSNEW: Start release notes for Samba 4.0.0rc2.

To be continued...

Karolin
(cherry picked from commit e30937e2826b43ebb3a77b621a6de8bf272b02d0)

1 files changed, 142 insertions, 71 deletions

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index b594e0e8e88..c62676edb1c 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -1,33 +1,24 @@
-What's new in Samba 4.0.0 rc1
-=============================
+Release Announcements
+=====================
+
+This is the second release candidate of Samba 4.0.  This is *not*
+intended for production environments and is designed for testing
+purposes only.  Please report any defects via the Samba bug reporting
+system at https://bugzilla.samba.org/.
 
 Samba 4.0 will be the next version of the Samba suite and incorporates
-all the technology found in both the Samba4 alpha series and the
+all the technology found in both the Samba4 series and the
 stable 3.x series. The primary additional features over Samba 3.6 are
 support for the Active Directory logon protocols used by Windows 2000
 and above.
 
-
-WARNINGS
-========
-
-Samba 4.0.0 rc1 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.
-
 This release contains the best of all of Samba's
 technology parts, both a file server (that you can reasonably expect
 to upgrade existing Samba 3.x releases to) and the AD domain
 controller work previously known as 'samba4'.
 
-Samba 4.0 is subjected to an awesome battery of tests on an automated
-basis, we have found Samba 4.0 to be very stable in it's behaviour.
-However, as with all our pre-releases we still recommend against
-upgrading production servers from Samba 3.x release to Samba 4.0 beta
-at this stage.
-
 If you are upgrading, or looking to develop, test or deploy Samba 4.0
-beta releases, you should backup all configuration and data.
+releases candidates, you should backup all configuration and data.
 
 
 UPGRADING
@@ -36,7 +27,7 @@ UPGRADING
 Users upgrading from Samba 3.x domain controllers and wanting to use
 Samba 4.0 as an AD DC should use the 'samba-tool domain
 classicupgrade' command.  See the wiki for more details:
-https://wiki.samba.org/index.php/Samba4/samba3upgrade/HOWTO 
+https://wiki.samba.org/index.php/Samba4/samba3upgrade/HOWTO.
 
 Users upgrading from Samba 4.0 alpha and beta releases since alpha15
 should run 'samba-tool dbcheck --cross-ncs --fix' before re-starting
@@ -53,6 +44,7 @@ If you used the BIND9_FLATFILE or BIND9_DLZ features,
 you'll have to add '-dns' to the 'server services' option,
 as the internal dns server (SAMBA_INTERNAL) is the default now.
 
+
 NEW FEATURES
 ============
 
@@ -66,17 +58,17 @@ Samba3-like logon services provided over CIFS.  We correctly generate
 the infamous Kerberos PAC, and include it with the Kerberos tickets we
 issue.
 
-Samba 4.0 beta ships with two distinct file servers.  We now use the
+Samba 4.0.0rc2 ships with two distinct file servers.  We now use the
 file server from the Samba 3.x series 'smbd' for all file serving by
 default.
 
 Samba 4.0 also ships with the 'NTVFS' file server.  This file server
-is what was used in all previous alpha releases of Samba 4.0, and is
+is what was used in all previous releases of Samba 4.0, and is
 tuned to match the requirements of an AD domain controller.  We
 continue to support this, not only to provide continuity to
 installations that have deployed it as part of an AD DC, but also as a
 running example of the NT-FSA architecture we expect to move smbd to in
-the longer term.  
+the longer term.
 
 For pure file server work, the binaries users would expect from that
 series (nmbd, winbindd, smbpasswd) continue to be available.  When
@@ -102,53 +94,132 @@ Finally, a new scripting interface has been added to Samba 4, allowing
 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 beta8
-===================
-
-For a list of changes since beta8, please see the git log.
-
-$ git clone git://git.samba.org/samba.git
-$ cd samba.git
-$ git log samba-4.0.0beta8..samba-4.0.0rc1
-
-Some major user-visible changes include:
-
-- The smbd file server now offers SMB3 as the maximum protocol
-  by default. Samba can negotiate version 3 of the SMB protocol
-  and supports the required features, including all required
-  features of SMB 2.1 and SMB 2.0. Note that this does not imply
-  that Samba implements all features of SMB3 since many of them
-  are optional capabilities. Examples of features that Samba does
-  not implement yet are leases (SMB 2.1) and multi-channel (SMB 3).
-
-  Samba now offers an initial support for SMB2 durable file handles.
-  These are enabled by default and can be turned off on a per share
-  basis by setting "durable handles = no" on the share configuration.
-  Note that in order to prevent conflicts with other applications
-  accessing the same files, durable handles are only granted on
-  shares that are configured for CIFS/SMB2-only access, i.e. more
-  explicitly shares that are configured for minimal interoperability
-  with these settings:
-
-    kernel oplocks = no
-    kernel share modes = no
-    posix locking = no
-
-  The option "kernel share modes" has been introduced to be able
-  to turn the translation of SMB share modes into kernel flocks
-  off.
-
-- The 'provision' script was merged into 'samba-tool'
-  as 'samba-tool domain provision' the arguments are still
-  the same.
 
-- The 'updateprovision' script was renamed to 'samba_upgradeprovision'.
+######################################################################
+Changes
+#######
+
+smb.conf changes
+----------------
+
+   Parameter Name			Description	Default
+   --------------			-----------	-------
+
+   allow dns updates			New		disabled
+   announce as				Removed
+   announce version			Removed
+   cldap port				New		0
+   client max protocol			New
+   client min protocol			New
+   client signing			Changed default	default
+   dcerpc endpoint servers		New
+   dgram port				New		0
+   display charset			Removed
+   dns forwarder			New
+   dns update command			New
+   homedir map				Changed default	auto.home
+   kernel share modes			New		Yes
+   kpasswd port				New		0
+   krb5 port				New		0
+   max protocol				Removed
+   min protocol				Removed
+   nbt client socket address		New		0.0.0.0
+   nbt port				New		0
+   nsupdate command			New
+   ntp signd socket directory		New
+   ntvfs handler			New
+   paranoid server security		Removed
+   pid directory			New
+   printer admin			Removed
+   rndc command 			New
+   rpc big endian			New		No
+   samba kcc command			New
+   send spnego principal		Removed
+   server max protocol			New		SMB3
+   server min protocol			New		LANMAN1
+   server role				New		auto
+   server services			New
+   server signing			Changed default	default
+   share backend			New
+   share modes				Removed
+   smb2 max read			Changed default 1048576
+   smb2 max write			Changed default 1048576
+   smb2 max trans			Changed default 1048576
+   socket address			Removed
+   spn update command			New
+   time offset				Removed
+   tls cafile				New
+   tls certfile				New
+   tls crlfile				New
+   tls dh params file			New
+   tls enabled				New		No
+   tls keyfile				New
+   unicode				New		Yes
+   web port				New		0
+   winbindd privileged socket directory	New
+   winbind sealed pipes			New		No
+   winbindd socket directory		New
+
+
+CHANGES SINCE 4.0.0rc1
+======================
+
+o   Michael Adam <obnox@samba.org>
+    * BUG 9173: Make the SMB2 compound request create/delete_on_close/
+      close work as Windows.
+
+
+o   Jeremy Allison <jra@samba.org>
+    * BUG 9161: Re-add the vfs_Chdir() cache.
+    * BUG 9189: SMB2 Create doesn't return correct MAX ACCESS access mask in
+      blob.
+    * BUG 9213: Bad ASN.1 NegTokenInit packet can cause invalid free.
+
+
+o   Christian Ambach <ambi@samba.org>
+    * BUG 9162: Fix the build of the GPFS VFS module.
+    * BUG 9197: Only do 'printing_subsystem_update' when printing is enabled.
+
+
+o   Alexander Bokovoy <ab@samba.org>
+    * BUG 9157: Cleanup idmap_ldap build dependencies.
+
+
+o   Ira Cooper <ira@samba.org>
+    * BUG 9162: Fix build on Illumos/Solaris using '--with-acl'.
+    * BUG 9173: Compound requests should continue processing.
+
+
+o   Björn Jacke <bj@sernet.de>
+    * BUG 9162: Fix the build of the ACL VFS modules.
+    * BUG 9172: Fix reporting of gfs2 quotas.
+
+
+o   Volker Lendecke <vl@samba.org>
+    * BUG 9217: CreateFile with FILE_DIRECTORY_FILE can create directories
+      on read-only shares.
+
+
+o   Stefan Metzmacher <metze@samba.org>
+    * BUG 9173: Make the SMB2 compound request create/delete_on_close/
+      close work as Windows.
+    * BUG 9184: Fix receiving of UDP packets from 0 bytes.
+    * BUG 9191: Release the share mode lock before calling exit_server().
+    * BUG 9193: Fix usage of invalid memory in smb2_signing_check_pdu().
+    * BUG 9194: Disallow '--prefix=/usr' and '--prefix=/usr/local' without
+      '--enable-fhs'.
+    * BUG 9198: Fix RHEL-CTDB packaging.
+
+
+o   Matthieu Patou <mat@matws.net>
+    * BUG 9199: Fix usage of "panic action".
+
+
+o   Andreas Schneider <asn@samba.org>
+    * BUG 8632: Fix builtin forms order to match Windows again.
+    * BUG 9159: Fix generating idmap manpages.
+    * BUG 9218: Don't segfault if user specified ports out for range.
 
-- We changed the default dns implementation to the internal dns server
-  (SAMBA_INTERNAL). BIND9_FLATFILE and BIND9_DLZ are still available,
-  but you'll have to add '-dns' to the 'server services' option
-  to disable the internal dns server.
-  The default for 'allow dns updates' has changed to 'secure only'.
 
 KNOWN ISSUES
 ============
@@ -179,17 +250,17 @@ 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 beta.
+  containing _.  A workaround will be in a future release.
 
 - samba_upgradeprovision should not be run when upgrading to this release
   from a recent release.  No important database format changes have
-  been made since alpha16.  
+  been made since alpha16.
 
 - Installation on systems without a system iconv (and developer
   headers at compile time) is known to cause errors when dealing with
   non-ASCII characters.
 
-- Domain member support in the 'samba' binary is in it's infancy, and
+- Domain member support in the 'samba' binary is in its infancy, and
   is not comparable to the support found in winbindd.  As such, do not
   use the 'samba' binary (provided for the AD server) on a member
   server.
@@ -205,7 +276,7 @@ KNOWN ISSUES
 
 - The DRS replication code may fail.  Please contact the team if you
   experience issues with DRS replication, as we have fixed many issues
-  here in response to feedback from our production users. 
+  here in response to feedback from our production users.
 
 
 RUNNING Samba 4.0 as an AD DC