How to move storage OEMs to Samba 4.0 ?

[Stefan (metze) Metzmacher]

Hi Jeremy,

>> * We could offer a loose collection of backported feature patches
>>   not harnessed into a release, so every interested OEM can pick
>>   from that collection.
> 
> I don't like that idea. The "loose collection of backported feature patches"
> is what everyone has on their own right now. It negates the
> advantage of being a "release".

I'd suggest a v3-6-backports branch (maybe in an extra repo, rebased on
v3-6-stable)

>> I would really like to discuss this further since I also want to
>> reach the best possible way to help OEMs with current releases
>> while encouraging them to move to 4.0.
> 
> So again, as everyone seemed to ignore it. I really like Ira's
> suggestion.
> 
> Anyone can submit a "new feature" patch for 3.6.next, under
> the following conditions.
> 
> 3 engineers must review and buy-off on the changes, not
> two. At least 2 of the engineers must be from different
> organizations (i.e. No all-Sernet, all-Google, or all-IBM
> patches).
> 
> Does that help ? I think it strikes the right balance
> of opening up the tree a little bit, without having
> a new "3.6.next is open for everything" policy.

And how many are needed to veto it?

metze

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20120613/31c14971/attachment.pgp>