[Gluster-Maintainers] 3.8 Plan changes - proposal

[Vijay Bellur]

On 01/07/2016 12:28 PM, Shyam wrote:
> On 01/07/2016 06:25 AM, Raghavendra Talur wrote:
>>
>>
>> On Thu, Jan 7, 2016 at 8:14 AM, Vijay Bellur <vbellur at redhat.com
>> <mailto:vbellur at redhat.com>> wrote:
>>
>>     Hi All,
>>
>>     I am considering the following changes for 3.8:
>>
>>     1. Include 4.0 features such as NSR, dht2, glusterd2.0 & eventing as
>>     experimental features in 3.8. 4.0 features are shaping up reasonably
>>     well and it would be nice to have them packaged in 3.8 so that we
>>     can get more meaningful feedback early on. As 4.0 features mature,
>>     we can push them out through subsequent 3.8.x releases to derive
>>     iterative feedback.
>>
>>
>> Would it be possible to provide these features without impacting the
>> stability of 3.8 for users not interested in new features? I am aware
>> that these will be provided as opt-ins but surely there would be code
>> changes involved in libglusterfs, posix xlator and rpc mechanisms.
>
> Good call out, yes there would be changes (small or otherwise) in common
> code. I think we need to think about this with care, and probably get in
> infra changes required by the new features sooner, so that they do not
> cause any stability concerns. IOW, cut off infra changes for
> experimental features earlier than the other feature submissions.
>

In addition, any code landing in libglusterfs and other common areas 
should be (more) thoroughly tested and reviewed before we merge them. We 
cannot afford to have regressions or problems creeping in due to 
infrastructure changes.

-Vijay