[Gluster-Maintainers] 3.8 Plan changes - proposal

Atin Mukherjee amukherj at redhat.com
Thu Jan 7 04:20:23 UTC 2016



On 01/07/2016 08:14 AM, Vijay Bellur 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.
+1
> 
> 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.
I am not sure how much effort all the components would need to put in
terms of bandwidth to achieve this. From GlusterD perspective our hands
are pretty tight and we'd definitely need help to convert the existing
tests into new framework.
> 
> 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.
Makes sense
> 
> 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.
IMHO, 4.0 MVP shouldn't be the only reason to hold 3.8.0 release. We
could still make the first cut of 4.0 as part of 3.8.x. However if there
are some other factors I'd leave it up to you to decide.
> 
> 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
> http://www.gluster.org/mailman/listinfo/maintainers


More information about the maintainers mailing list