<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 7, 2016 at 8:14 AM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All,<br>
<br>
I am considering the following changes for 3.8:<br>
<br>
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.<br></blockquote><div><br></div><div>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.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
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.<br></blockquote><div><br></div><div>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.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
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.<br></blockquote><div> </div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
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.<br></blockquote><div> </div><div>+1 </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
5. Move out 3.8 by 2-3 months (end of May or early June 2016) to accomplish these changes.<br>
<br>
Would like to know your thoughts and opinions about this proposal before we reach out to the broader community about the changes.<br>
<br>
Thanks,<br>
Vijay<br>
_______________________________________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org" target="_blank">maintainers@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/maintainers</a><br>
</blockquote></div><br></div></div>