On Tue, Mar 15, 2016 at 01:39:12PM +0530, Venky Shankar wrote: > On Tue, Mar 15, 2016 at 12:04:46PM +0530, Jiffin Tony Thottan wrote: > > > > Hi, > > > > I had created pull request in roadmap for DHT2 [1] with minimal details and > > it got merged > > > > @Venky/Shyam : can u please do a follow up > > > > [1] https://github.com/thotz/glusterweb/commit/f81253cfc6821d3589dbe6cde62025fa4c5c7bf7 > > Sure. Currently we're thinking if the POC should be merged upstream (I > think it should). It it is not merged in the master branch, it will not be there when we branch release-3.8. If it is not in the release branch, it will not be part of 3.8. We require to have the feature pages and/or technical design in the glusterfs-specs repository (under the accepted/release-3.8 directory) by the end of this week. See the linked roadmap for other requirements, all of them apply for experimental features too. Niels > Shyam wanted to check this with Jeff and others. Shyam, anything? > > > > > Regards, > > Jiffin > > > > On 14/03/16 14:49, Niels de Vos wrote: > > >Hi, > > > > > >We're kicking the 3.8 release back into shape and schedule. Our planned > > >6 month release cycle has completely failed on us, we're about 6 months > > >behind. I've taken the liberty to set aggressive deadlines and put this > > >on the roadmap on https://www.gluster.org/community/roadmap/3.8/ . > > > > > >The page explains the dates, it will be extremely difficult to convince > > >me to change it. A delay because a feature is not ready will not be > > >acceptable, the feature will be moved out into the next (major/minor) > > >release. > > > > > >Requirements that are listed on the roadmap affect all features. *ALL* > > >of these will need to be mostly fulfilled by the end of April. The last > > >day of April has been picked as branch date. Any feature that is not > > >ready at the time of branching (includes *ALL* requirements) will be > > >disabled/removed from the sources. There is an other chance to get the > > >feature in for the following release in 6 months time. > > > > > >All feature owners have been put on CC of this email. They need to go > > >through the roadmap and update the description, current status, links, > > >and any other missing parts before the end of this week. There need to > > >be visible progress on at least the contents in the roadmap, and in the > > >linked designs/feature pages. If there is no obvious attempt to improve > > >the status of the feature, it will be marked as "move to next release". > > > > > >Sending updates for the roadmap is easy, click the "Edit this page on > > >GitHub" link on the bottom of the page. It should create a pull request > > >that I can review, please assign it to me ("nixpanic" on GitHub). > > > > > >If a feature is not expected to be ready before the end of April, please > > >let me know as soon as possible. All tracking that we do makes it easier > > >when we are kept informed. > > > > > >For this release, Jiffin offered his assistance. If there are any > > >questions, do not hesitate to ask us (of course with the gluster-devel > > >list on CC). > > > > > >Thanks, > > >Jiffin & Niels > > > > > > > > >_______________________________________________ > > >Gluster-devel mailing list > > >Gluster-devel@xxxxxxxxxxx > > >http://www.gluster.org/mailman/listinfo/gluster-devel > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
