<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On 14-Mar-2016 6:45 pm, "Niels de Vos" <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
><br>
> On Mon, Mar 14, 2016 at 05:54:00PM +0530, Atin Mukherjee wrote:<br>
> ><br>
> ><br>
> > On 03/14/2016 02:49 PM, Niels de Vos wrote:<br>
> > > Hi,<br>
> > ><br>
> > > We're kicking the 3.8 release back into shape and schedule. Our planned<br>
> > > 6 month release cycle has completely failed on us, we're about 6 months<br>
> > > behind. I've taken the liberty to set aggressive deadlines and put this<br>
> > > on the roadmap on <a href="https://www.gluster.org/community/roadmap/3.8/">https://www.gluster.org/community/roadmap/3.8/</a> .<br>
> > ><br>
> > > The page explains the dates, it will be extremely difficult to convince<br>
> > > me to change it. A delay because a feature is not ready will not be<br>
> > > acceptable, the feature will be moved out into the next (major/minor)<br>
> > > release.<br>
> > Is this applicable for all Gluster 4.0 initiatives as well? Since all of<br>
> > these will come as experimental features as part of 3.8 does feature<br>
> > freeze criteria apply for them?<br>
><br>
> Yes, anything that is expected to be ready for experimental use should<br>
> fulfill all requirements. Gluster 4.0 features in 3.8 would need to be<br>
> usable and configurable by most of our users. Experimental features may<br>
> become fully stable and 'supported' during the 3.8 lifecycle.<br>
Given the experimental nature of 4.0 features, I was wondering how do we define the scope of readiness. Usable is the right term and none of these features should break legacy stuffs. I am little doubtful about the word "stable". Can stable and experimental go together? (Very few IMO)<br>
Let me know if you think otherwise.<br>
><br>
> Features that are not in a usable or stable state, or do not provide any<br>
> of the other requirements will be stripped out of the 3.8 release.<br>
><br>
> HTH,<br>
> Niels<br>
><br>
><br>
> > > Requirements that are listed on the roadmap affect all features. *ALL*<br>
> > > of these will need to be mostly fulfilled by the end of April. The last<br>
> > > day of April has been picked as branch date. Any feature that is not<br>
> > > ready at the time of branching (includes *ALL* requirements) will be<br>
> > > disabled/removed from the sources. There is an other chance to get the<br>
> > > feature in for the following release in 6 months time.<br>
> > ><br>
> > > All feature owners have been put on CC of this email. They need to go<br>
> > > through the roadmap and update the description, current status, links,<br>
> > > and any other missing parts before the end of this week. There need to<br>
> > > be visible progress on at least the contents in the roadmap, and in the<br>
> > > linked designs/feature pages. If there is no obvious attempt to improve<br>
> > > the status of the feature, it will be marked as "move to next release".<br>
> > ><br>
> > > Sending updates for the roadmap is easy, click the "Edit this page on<br>
> > > GitHub" link on the bottom of the page. It should create a pull request<br>
> > > that I can review, please assign it to me ("nixpanic" on GitHub).<br>
> > ><br>
> > > If a feature is not expected to be ready before the end of April, please<br>
> > > let me know as soon as possible. All tracking that we do makes it easier<br>
> > > when we are kept informed.<br>
> > ><br>
> > > For this release, Jiffin offered his assistance. If there are any<br>
> > > questions, do not hesitate to ask us (of course with the gluster-devel<br>
> > > list on CC).<br>
> > ><br>
> > > Thanks,<br>
> > > Jiffin & Niels<br>
> > ><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > Gluster-devel mailing list<br>
> > > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> > > <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
> > ><br>
><br>
> _______________________________________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</p>