On Thu, May 4, 2017 at 4:38 PM, Niels de Vos <ndevos@xxxxxxxxxx> wrote: > On Thu, May 04, 2017 at 03:39:58PM +0530, Pranith Kumar Karampuri wrote: >> On Wed, May 3, 2017 at 2:36 PM, Kaushal M <kshlmster@xxxxxxxxx> wrote: >> >> > On Tue, May 2, 2017 at 3:55 PM, Pranith Kumar Karampuri >> > <pkarampu@xxxxxxxxxx> wrote: >> > > >> > > >> > > On Sun, Apr 30, 2017 at 9:01 PM, Shyam <srangana@xxxxxxxxxx> wrote: >> > >> >> > >> Hi, >> > >> >> > >> Release 3.11 for gluster has been branched [1] and tagged [2]. >> > >> >> > >> We have ~4weeks to release of 3.11, and a week to backport features that >> > >> slipped the branching date (May-5th). >> > >> >> > >> A tracker BZ [3] has been opened for *blockers* of 3.11 release. Request >> > >> that any bug that is determined as a blocker for the release be noted >> > as a >> > >> "blocks" against this bug. >> > >> >> > >> NOTE: Just a heads up, all bugs that are to be backported in the next 4 >> > >> weeks need not be reflected against the blocker, *only* blocker bugs >> > >> identified that should prevent the release, need to be tracked against >> > this >> > >> tracker bug. >> > >> >> > >> We are not building beta1 packages, and will build out RC0 packages once >> > >> we cross the backport dates. Hence, folks interested in testing this >> > out can >> > >> either build from the code or wait for (about) a week longer for the >> > >> packages (and initial release notes). >> > >> >> > >> Features tracked as slipped and expected to be backported by 5th May >> > are, >> > >> >> > >> 1) [RFE] libfuse rebase to latest? #153 (@amar, @csaba) >> > >> >> > >> 2) SELinux support for Gluster Volumes #55 (@ndevos, @jiffin) >> > >> - Needs a +2 on https://review.gluster.org/13762 >> > >> >> > >> 3) Enhance handleops readdirplus operation to return handles along with >> > >> dirents #174 (@skoduri) >> > >> >> > >> 4) Halo - Initial version (@pranith) >> > > >> > > >> > > I merged the patch on master. Will send out the port on Thursday. I have >> > to >> > > leave like right now to catch train and am on leave tomorrow, so will be >> > > back on Thursday and get the port done. Will also try to get the other >> > > patches fb guys mentioned post that preferably by 5th itself. >> > >> > Niels found that the HALO patch has pulled in a little bit of the IPv6 >> > patch. This shouldn't have happened. >> > The IPv6 patch is currently stalled because it depends on an internal >> > FB library. The IPv6 bits that made it in pull this dependency. >> > This would have lead to a -2 on the HALO patch by me, but as I wasn't >> > aware of it, the patch was merged. >> > >> > The IPV6 changes are in rpcsvh.{c,h} and configure.ac, and don't seem >> > to affect anything HALO. So they should be easily removable and should >> > be removed. >> > >> >> As per the configure.ac the macro is enabled only when we are building >> gluster with "--with-fb-extras", which I don't think we do anywhere, so >> didn't think they are important at the moment. Sorry for the confusion >> caused because of this. Thanks to Kaushal for the patch. I will backport >> that one as well when I do the 3.11 backport of HALO. So will wait for the >> backport until Kaushal's patch is merged. > > Note that there have been disucssions about preventing special vendor > (Red Hat or Facebook) flags and naming. In that sense, --with-fb-extras > is not acceptible. Someone was interested in providing a "site.h" > configuration file that different vendors can use to fine-tune certain > things that are too detailed for ./configure options. > > We should remove the --with-fb-extras as well, specially because it is > not useful for anyone that does not have access to the forked fbtirpc > library. > > Kaushal mentioned he'll update the patch that removed the IPv6 default > define, to also remove the --with-fb-extras and related bits. The patch removing IPV6 and fbextras is at https://review.gluster.org/17174 waiting for regression tests to run. I've merged the Selinux backports, https://review.gluster.org/17159 and https://review.gluster.org/17157 into release-3.11 > > Thanks, > Niels > >> >> >> >> > >> > > >> > >> >> > >> >> > >> Thanks, >> > >> Kaushal, Shyam >> > >> >> > >> [1] 3.11 Branch: https://github.com/gluster/glusterfs/tree/release-3.11 >> > >> >> > >> [2] Tag for 3.11.0beta1 : >> > >> https://github.com/gluster/glusterfs/tree/v3.11.0beta1 >> > >> >> > >> [3] Tracker BZ for 3.11.0 blockers: >> > >> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.0 >> > >> >> > >> _______________________________________________ >> > >> maintainers mailing list >> > >> maintainers@xxxxxxxxxxx >> > >> http://lists.gluster.org/mailman/listinfo/maintainers >> > > >> > > >> > > >> > > >> > > -- >> > > Pranith >> > > >> > > _______________________________________________ >> > > Gluster-devel mailing list >> > > Gluster-devel@xxxxxxxxxxx >> > > http://lists.gluster.org/mailman/listinfo/gluster-devel >> > >> >> >> >> -- >> Pranith > >> _______________________________________________ >> maintainers mailing list >> maintainers@xxxxxxxxxxx >> http://lists.gluster.org/mailman/listinfo/maintainers > _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel