To release Samba 4.0 'as is'

Michael Croes mycroes at
Tue Nov 22 12:23:25 MST 2011

I totally agree on points made by people against a Samba 4 release soon. It
will probably result in similar situations as have occured with Gnome 3 and
KDE 4.

However, as someone using Samba 4 in production (authentication for proxy-,
file- and mailservers, domain controller, mail routing) I would like
something distributions can build on. Personally I don't care about fs
support in Samba 4, every serious organization can devote a seperate
computer/server to it.

For me I'd rather see monthly or bi-monthly packages in an Ubuntu PPA than
an early Samba 4 release. Or maybe just some good guidance on how to
package Samba 4 so people have something to start with.

I currently have to deal with occassional Samba restarts and half-working
DNS, which sucks in production. it's good enough for me to use with around
100 users, but calling this a stable release would be crazy.

Op 22 nov. 2011 07:13 schreef "Andrew Bartlett" <abartlet at> het

> I would like to propose that we proceed to making a pre-release of Samba
> 4.0 in the next month (ie, before Christmas), and that we propose to
> release Samba 4.0 'as is' regarding major features.
> To be clear, I propose that the DNS server work continue, and we seek a
> resolution of the best approach here over the time between now and a
> release, but we do not block a release on this point.  (I am confident
> however that those involved will have a good solution, and even the
> current flat file is clearly good enough for our many users).
> I also propose that we do not make the major architectural changes
> between now and the release to change file server or winbind
> implementations for the AD DC.  Instead, we continue to build on the
> massive efforts already made here over the next few months, but we will
> not change the default behaviour for a 4.0 release.
> This will give the vendors (Univention and Resara) and our numerous
> users who are building on top of Samba 4.0 alpha releases a stable
> release to move to, based on the current architecture, before we make
> the change to a common file server for Samba 4.1.
> This will mean we continue to ship smbd, nmbd, winbindd, samba etc as
> found in the current alpha releases.
> With this plan, and with the quality brought about by our continuous
> integration approach, I think we can make a Samba 4.0 release in a
> reasonable time-frame, perhaps with a final release in about three
> months time.
> I do wish to be clear that I'm certainly not abandoning the idea of a
> single file server, and I know many others on the team have also
> invested great amounts of their own time in this effort.  It is
> important not only for NAS vendors who wish to add AD to the NAS (an
> idea I raise with every NAS vendor I get the chance to speak to), but
> also our users who still regularly ask for a combined release with the
> AD server, file server and print server all present in the same runtime
> installation.
> What do others think?
> Andrew Bartlett
> --
> Andrew Bartlett                      
> Authentication Developer, Samba Team 

More information about the samba-technical mailing list