| 1 | Samba4 alpha4 is not a final Samba release. That is more a reference
|
|---|
| 2 | to Samba4's lack of the features we expect you will need than a
|
|---|
| 3 | statement of code quality, but clearly it hasn't seen a broad
|
|---|
| 4 | deployment yet. If you were to upgrade Samba3 (or indeed Windows) to
|
|---|
| 5 | Samba4, you would find many things work, but that other key features
|
|---|
| 6 | you may have relied on simply are not there yet.
|
|---|
| 7 |
|
|---|
| 8 | For example, while Samba 3.0 is an excellent member of a Active
|
|---|
| 9 | Directory domain, Samba4 is happier as a domain controller, and it is
|
|---|
| 10 | in this role where it has seen deployment into production.
|
|---|
| 11 |
|
|---|
| 12 | Samba4 is subjected to an awesome battery of tests on an
|
|---|
| 13 | automated basis, we have found Samba4 to be very stable in it's
|
|---|
| 14 | behaviour. We have to recommend against upgrading production servers
|
|---|
| 15 | from Samba 3 to Samba 4 at this stage, because there may be the features on
|
|---|
| 16 | which you may rely that are not present, or the mapping of
|
|---|
| 17 | your configuration and user database may not be complete.
|
|---|
| 18 |
|
|---|
| 19 | If you are upgrading, or looking to develop, test or deploy Samba4, you should
|
|---|
| 20 | backup all configuration and data.
|
|---|
| 21 |
|
|---|
| 22 | We welcome your testing, please file bug reports at
|
|---|
| 23 | https://bugzilla.samba.org/, product: Samba4. Please include as much
|
|---|
| 24 | information as possible, such as GIT revision SHA and backtraces.
|
|---|
