summaryrefslogtreecommitdiff
path: root/source4/BUGS
diff options
context:
space:
mode:
authorJelmer Vernooij <jelmer@samba.org>2008-09-30 17:11:39 +0200
committerJelmer Vernooij <jelmer@samba.org>2008-09-30 17:11:39 +0200
commit40a6a28170881e567d130c10bec700441423d1e8 (patch)
tree4425f04dd63307cae38d39b75bf3a566a2df9029 /source4/BUGS
parente0af9601e1535b847e3c82e334d6a9de2ff3580d (diff)
downloadsamba-40a6a28170881e567d130c10bec700441423d1e8.tar.gz
Move Samba4-specific files into source4/
Diffstat (limited to 'source4/BUGS')
-rw-r--r--source4/BUGS24
1 files changed, 24 insertions, 0 deletions
diff --git a/source4/BUGS b/source4/BUGS
new file mode 100644
index 00000000000..1a9790ddd9f
--- /dev/null
+++ b/source4/BUGS
@@ -0,0 +1,24 @@
+Samba4 alpha4 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
+Samba4, you would find many things work, but that other key features
+you may have relied on simply are not there yet.
+
+For example, while Samba 3.0 is an excellent member of a Active
+Directory domain, Samba4 is happier as a domain controller, and it is
+in this role where it has seen deployment into production.
+
+Samba4 is subjected to an awesome battery of tests on an
+automated basis, we have found Samba4 to be very stable in it's
+behaviour. We have to recommend against upgrading production servers
+from Samba 3 to Samba 4 at this stage, because there may be the features on
+which you may rely that are not present, or the mapping of
+your configuration and user database may not be complete.
+
+If you are upgrading, or looking to develop, test or deploy Samba4, you should
+backup all configuration and data.
+
+We welcome your testing, please file bug reports at
+https://bugzilla.samba.org/, product: Samba4. Please include as much
+information as possible, such as GIT revision number and backtraces.