To release Samba 4.0 'as is'

Richard Sharpe realrichardsharpe at
Tue Nov 22 10:43:37 MST 2011

On Tue, Nov 22, 2011 at 9:33 AM, Jeremy Allison <jra at> wrote:
> On Tue, Nov 22, 2011 at 05:13:16PM +1100, Andrew Bartlett wrote:

Andrew Bartlett's proposal trimmed because you can infer it from
Jeremy's response.

>> What do others think?
> -1. We can't do this. It isn't an integrated product yet,
> it's just a grab bag of non-integrated features.
> Without proper design and code to implement the source3
> fileserver, winbind and nmbd integration we simply don't
> have a finished product. The integrated fileserver is a
> MUST HAVE for a 4.0 release.
> Rightly or wrongly Samba4 is seen as the replacement
> for Samba3. If you ship what you have now you put the
> Team members who support OEM fileservers in an incredibly
> difficult position w.r.t. marketing and communications
> with our customers, not to mention the Linux distros.
> Don't just ship whatever you have out the door, you need
> to produce a plan to finish the missing features, and
> create bug reports to track them.
> If you want to split the codebase and Team efforts completely,
> releasing an unfinished Samba4 is an excellent way to do it.

I concur with Jeremy's view. I get lots of people who are involved
with using Samba as a CIFS server asking the difference between Samba
3 and Samba 4, and I think you will find it very hard to position
Samba 4 if it does not have the sort of functionality Jeremy talks
about and you risk turning many people off of Samba altogether.

Richard Sharpe

More information about the samba-technical mailing list