Re: [Gluster-devel] Patches to be merged before 3.6 branching
On 2014-07-15 11:30, Niels de Vos wrote: > On Mon, Jul 14, 2014 at 06:05:25PM +0100, Justin Clift wrote: >> On 14/07/2014, at 4:20 PM, Anders Blomdell wrote: >>> On 2014-07-14 16:03, Vijay Bellur wrote: Hi All, I intend creating the 3.6 branch tomorrow. After that, the branch will be restricted to bug fixes only. If you have any major patches to be reviewed and merged for release-3.6, please update this thread. >>> Does this mean that https://bugzilla.redhat.com/show_bug.cgi?id=1113050 >>> has no chance to get in (no patch for that yet, still trying to figure out >>> how things work inside gluster)? >> >> Sounds like that would be a bug fix, so it'd get applied to everything that >> it makes sense too. eg likely 3.6, 3.5, 3.7dev, etc. > > Indeed, if there is no patch available when release-3.6 gets branched, > bug fixes and (serious) usability improvements can get backported to the > 3.6 version. The process to do so has been documented here: > - http://www.gluster.org/community/documentation/index.php/Backport_Guidelines > > When the branching happened, the 3.6 release will be closed for new > feature enhancements. The goal is to stabilize the branch and not > introduce any complex/major changes anymore. Vijay will likely mention > this in his announcement of the release-3.6 branch too. > > There can be a thin line between 'usability bug' and 'feature'. If an > acceptable case is made for an improvement, I doubt it will have > difficulties getting included in any of the stable branches. > > >>> And I would really like to get http://review.gluster.org/8292, >> >> IPv6 support. Niels, have you had a change to look at this? Should we >> get this merged, and fix any bugs that turn up later? > > No, and unfortunately I will unlikely be able to look into that within > the next few weeks. I'd really like to see good IPv6 support in Gluster, > but for me it really is a long-term goal. OK, will have to keep my own version here then (some of my hosts are IPv6 only) since the current state of affairs, where you have to edit a lot of volfiles, etc in order to get it working is far too cumbersome. > Maybe the 'better peer identification' feature improves IPv6 support as > well. Some details and further pointers to discussions about it can be > found here: > - > http://www.gluster.org/community/documentation/index.php/Features/Better_peer_identification Very little IPv6 there, but very useful for multi-homed machines (which I also want, but not as badly). /Anders -- Anders Blomdell Email: anders.blomd...@control.lth.se Department of Automatic Control Lund University Phone:+46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Patches to be merged before 3.6 branching
On Mon, Jul 14, 2014 at 06:05:25PM +0100, Justin Clift wrote: > On 14/07/2014, at 4:20 PM, Anders Blomdell wrote: > > On 2014-07-14 16:03, Vijay Bellur wrote: > >> Hi All, > >> > >> I intend creating the 3.6 branch tomorrow. After that, the branch > >> will be restricted to bug fixes only. If you have any major patches > >> to be reviewed and merged for release-3.6, please update this > >> thread. > > Does this mean that https://bugzilla.redhat.com/show_bug.cgi?id=1113050 > > has no chance to get in (no patch for that yet, still trying to figure out > > how things work inside gluster)? > > Sounds like that would be a bug fix, so it'd get applied to everything that > it makes sense too. eg likely 3.6, 3.5, 3.7dev, etc. Indeed, if there is no patch available when release-3.6 gets branched, bug fixes and (serious) usability improvements can get backported to the 3.6 version. The process to do so has been documented here: - http://www.gluster.org/community/documentation/index.php/Backport_Guidelines When the branching happened, the 3.6 release will be closed for new feature enhancements. The goal is to stabilize the branch and not introduce any complex/major changes anymore. Vijay will likely mention this in his announcement of the release-3.6 branch too. There can be a thin line between 'usability bug' and 'feature'. If an acceptable case is made for an improvement, I doubt it will have difficulties getting included in any of the stable branches. > > And I would really like to get http://review.gluster.org/8292, > > IPv6 support. Niels, have you had a change to look at this? Should we > get this merged, and fix any bugs that turn up later? No, and unfortunately I will unlikely be able to look into that within the next few weeks. I'd really like to see good IPv6 support in Gluster, but for me it really is a long-term goal. Maybe the 'better peer identification' feature improves IPv6 support as well. Some details and further pointers to discussions about it can be found here: - http://www.gluster.org/community/documentation/index.php/Features/Better_peer_identification Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Patches to be merged before 3.6 branching
Hi Vijay, I Have two patches which is good to have for 3.6 1) http://review.gluster.org/#/c/8162/ -> I have one +1, I need to get the ack's again because of rebase. 2) http://review.gluster.org/#/c/8191/ -> I am going to resubmit this shortly. Thanks, Sachin. - Original Message - From: "Vijay Bellur" To: "Gluster Devel" Sent: Monday, July 14, 2014 7:33:05 PM Subject: [Gluster-devel] Patches to be merged before 3.6 branching Hi All, I intend creating the 3.6 branch tomorrow. After that, the branch will be restricted to bug fixes only. If you have any major patches to be reviewed and merged for release-3.6, please update this thread. Thanks, Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Patches to be merged before 3.6 branching
Also for fuse_readlink bug from MacOSX testing - http://review.gluster.com/#/c/8300/ On Tue, Jul 15, 2014 at 1:46 AM, Harshavardhana wrote: > I need reviews here to get these changes in for 3.6 , La FreeBSD - > http://review.gluster.com/#/c/8246/ > > On Tue, Jul 15, 2014 at 1:32 AM, Soumya Koduri wrote: >> Hi Vijay, >> >> I suggest below patch to be merged - >> http://review.gluster.org/#/c/7976/ >> >> Its not a critical one but fixes an issue with gfid-healing in the libgfapi >> path. >> >> Thanks, >> Soumya >> >> >> On 07/14/2014 07:33 PM, Vijay Bellur wrote: >>> >>> Hi All, >>> >>> I intend creating the 3.6 branch tomorrow. After that, the branch will >>> be restricted to bug fixes only. If you have any major patches to be >>> reviewed and merged for release-3.6, please update this thread. >>> >>> Thanks, >>> Vijay >>> ___ >>> Gluster-devel mailing list >>> Gluster-devel@gluster.org >>> http://supercolony.gluster.org/mailman/listinfo/gluster-devel >> >> ___ >> Gluster-devel mailing list >> Gluster-devel@gluster.org >> http://supercolony.gluster.org/mailman/listinfo/gluster-devel > > > > -- > Religious confuse piety with mere ritual, the virtuous confuse > regulation with outcomes -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Patches to be merged before 3.6 branching
I need reviews here to get these changes in for 3.6 , La FreeBSD - http://review.gluster.com/#/c/8246/ On Tue, Jul 15, 2014 at 1:32 AM, Soumya Koduri wrote: > Hi Vijay, > > I suggest below patch to be merged - > http://review.gluster.org/#/c/7976/ > > Its not a critical one but fixes an issue with gfid-healing in the libgfapi > path. > > Thanks, > Soumya > > > On 07/14/2014 07:33 PM, Vijay Bellur wrote: >> >> Hi All, >> >> I intend creating the 3.6 branch tomorrow. After that, the branch will >> be restricted to bug fixes only. If you have any major patches to be >> reviewed and merged for release-3.6, please update this thread. >> >> Thanks, >> Vijay >> ___ >> Gluster-devel mailing list >> Gluster-devel@gluster.org >> http://supercolony.gluster.org/mailman/listinfo/gluster-devel > > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-devel -- Religious confuse piety with mere ritual, the virtuous confuse regulation with outcomes ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Patches to be merged before 3.6 branching
Hi Vijay, I suggest below patch to be merged - http://review.gluster.org/#/c/7976/ Its not a critical one but fixes an issue with gfid-healing in the libgfapi path. Thanks, Soumya On 07/14/2014 07:33 PM, Vijay Bellur wrote: Hi All, I intend creating the 3.6 branch tomorrow. After that, the branch will be restricted to bug fixes only. If you have any major patches to be reviewed and merged for release-3.6, please update this thread. Thanks, Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Patches to be merged before 3.6 branching
On Monday 14 July 2014 07:33 PM, Vijay Bellur wrote: Hi All, I intend creating the 3.6 branch tomorrow. After that, the branch will be restricted to bug fixes only. If you have any major patches to be reviewed and merged for release-3.6, please update this thread. Thanks, Vijay I have 2 patches for review. [1] has got +1 and passed the regression. It has to be merged if it looks fine. [2] has passed the regression tests but need to be reviewed. [1]: http://review.gluster.org/#/c/8230/ [2]: http://review.gluster.org/#/c/8150/ Regards, Raghavendra Bhat ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Patches to be merged before 3.6 branching
On 14/07/2014, at 4:20 PM, Anders Blomdell wrote: > On 2014-07-14 16:03, Vijay Bellur wrote: >> Hi All, >> >> I intend creating the 3.6 branch tomorrow. After that, the branch >> will be restricted to bug fixes only. If you have any major patches >> to be reviewed and merged for release-3.6, please update this >> thread. > Does this mean that https://bugzilla.redhat.com/show_bug.cgi?id=1113050 > has no chance to get in (no patch for that yet, still trying to figure out > how things work inside gluster)? Sounds like that would be a bug fix, so it'd get applied to everything that it makes sense too. eg likely 3.6, 3.5, 3.7dev, etc. > I think http://review.gluster.org/8299 is important, since gluster will break > with some locales. Also a bug fix. It seems simpler to commit sooner rather than later, but it'll depend on reviews. > And I would really like to get http://review.gluster.org/8292, IPv6 support. Niels, have you had a change to look at this? Should we get this merged, and fix any bugs that turn up later? > http://review.gluster.org/8208 Seems like a bugfix, so it can likely go in after Susant and others have finished working on it. > and http://review.gluster.org/8203. Same as 8208, it looks like a bugfix. Seems further along the dev/review process. > All the things above should already be on > https://bugzilla.redhat.com/show_bug.cgi?id=1117822, so maybe this mail is > just > noise. Nah, reminders are useful. :) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Patches to be merged before 3.6 branching
On 2014-07-14 16:03, Vijay Bellur wrote: > Hi All, > > I intend creating the 3.6 branch tomorrow. After that, the branch > will be restricted to bug fixes only. If you have any major patches > to be reviewed and merged for release-3.6, please update this > thread. Does this mean that https://bugzilla.redhat.com/show_bug.cgi?id=1113050 has no chance to get in (no patch for that yet, still trying to figure out how things work inside gluster)? I think http://review.gluster.org/8299 is important, since gluster will break with some locales. And I would really like to get http://review.gluster.org/8292, http://review.gluster.org/8208 and http://review.gluster.org/8203. All the things above should already be on https://bugzilla.redhat.com/show_bug.cgi?id=1117822, so maybe this mail is just noise. /Anders -- Anders Blomdell Email: anders.blomd...@control.lth.se Department of Automatic Control Lund University Phone:+46 46 222 4625 P.O. Box 118 Fax: +46 46 138118 SE-221 00 Lund, Sweden ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Patches to be merged before 3.6 branching
My patch for improving peer identification [1] needs to get in. It's functionally complete and can be merged right now. But KP has some minor comments. I'll update it tonight, and it should be good for merge by the morning, ~kaushal [1] https://review.gluster.org/8238 On Mon, Jul 14, 2014 at 7:33 PM, Vijay Bellur wrote: > Hi All, > > I intend creating the 3.6 branch tomorrow. After that, the branch will be > restricted to bug fixes only. If you have any major patches to be reviewed > and merged for release-3.6, please update this thread. > > Thanks, > Vijay > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-devel ___ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
