How to move storage OEMs to Samba 4.0 ?

Jeremy Allison jra at
Wed Jun 6 10:13:16 MDT 2012

On Wed, Jun 06, 2012 at 10:19:37AM +0200, Kai Blin wrote:
> You're clearly missing
> 3) Keep our existing policy of not adding new features to "stable"
> release branches. We can pledge to support 3.6 for a longer run than
> just until 4.2 is released, for people who really need the stability. We
> can also have patches for popular new features, if people have the spare
> time to create those. But this clearly points out where the testing of
> these patches needs to happen: in-house where people chose to apply the
> patches.
> Which is what I'd prefer. We don't even seem to have the development
> resources to get the next 3.6 bugfix release out in a timely manner. I
> think having to not only bug fixes but also new features will make
> further 3.6 releases take even longer and divert development effort from
> the 4.x series.

What you're missing is that these back-ports of new features ARE BEING
DONE ANYWAY by Team members on behalf of OEMs. That's what many Team
members are actually employed for.

Opening up the 3.6.x tree a little just allows these changes to have
a single consistent home.


More information about the samba-technical mailing list