[Gluster-Maintainers] 3.8 Plan changes - proposal

[Shyam]

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.

>
>
>     2. Ensure that most of our components have tests in distaf by 3.8. I
>     would like us to have more deterministic pre-release testing for 3.8
>     and having tests in distaf should help us in accomplishing that goal.
>
>
> A major hurdle here is the test infrastructure setup. We have around 25
> slaves(NetBSD and CentOS combined) for our .t based regressions. If we
> could get more slaves to setup the distaf based jenkins jobs to run them
> in parallel we can push module owners to start contributing distaf tests.
>
>
>     3. Add "forward compatibility" section to all feature pages proposed
>     for 3.8 so that we carefully review the impact of a feature on all
>     upcoming Gluster.next features.
>
> +1
>
>
>     4. Have Niels de Vos as the maintainer for 3.8 with immediate
>     effect. This is a change from the past where we have had release
>     maintainers after a .0 release is in place. I think Niels' diligence
>     as a release manager will help us in having a more polished .0 release.
>
> +1
>
>     5. Move out 3.8 by 2-3 months (end of May or early June 2016) to
>     accomplish these changes.
>
>     Would like to know your thoughts and opinions about this proposal
>     before we reach out to the broader community about the changes.
>
>     Thanks,
>     Vijay
>     _______________________________________________
>     maintainers mailing list
>     maintainers at gluster.org <mailto:maintainers at gluster.org>
>     http://www.gluster.org/mailman/listinfo/maintainers
>
>
>
>
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> http://www.gluster.org/mailman/listinfo/maintainers
>