To release Samba 4.0 'as is'

[Kai Blin]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-12-01 08:41, Andrew Bartlett wrote:


> It seems unfortunate that we do not have the confidence in our 
> current smbd code or the desire to support it that we would need
> to break it, but if that is the price we need to pay for an AD 
> release, I'm still happy.

Incidentally, that's not what I think I said. My suggestion to break
smbd et al for the AD server release was to accommodate for the fact
that we're not planning to make this a file server release, and
breaking smbd is the clearest way to signal this to people. I would
think that smbd is in as good a shape in master as the AD parts are,
seeing how they get identical testing. It's just that so far the
release process for the file server was not "take whatever happens to
pass autobuild right now", so I was trying to allow for that.

> (While I had hoped to help them with the release, users like 
> Univention taking the bleeding edge of smbd/Samba4 integration may 
> be better served by master anyway, as that code matures).

IIRC Univention uses a 3.x server for file and print serving. I don't
see why they couldn't keep using that set-up until we release 4.0 File
Server.

Cheers,
Kai

- -- 
Kai Blin
Worldforge developer http://www.worldforge.org/
Wine developer http://wiki.winehq.org/KaiBlin
Samba team member http://www.samba.org/samba/team/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7XS3kACgkQEKXX/bF2FpRuswCgpFLjyd2QTwdXvxkI7nmdiZnm
FHoAmwTk7gxi7eS9pU0mISaBjWxOsvkG
=txU8
-----END PGP SIGNATURE-----