<div dir="ltr"><div><div><div><div>Hey Shyam,<br><br></div>Can we also have the heal info summary feature [1], which is merged upstream [2].<br></div>I haven't raised an issue for this yet, I can do that by tomorrow and I need to write a doc for that.<br><br>[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1261463">https://bugzilla.redhat.com/show_bug.cgi?id=1261463</a><br>[2] <a href="https://review.gluster.org/#/c/12154/">https://review.gluster.org/#/c/12154/</a><br><br><br>Thanks & Regards,<br>Karthik<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 31, 2017 at 4:21 PM, Shyam Ranganathan <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 09/11/2017 10:21 AM, Shyam Ranganathan wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi,<br>
<br>
The next community release of Gluster is 3.13, which is a short term maintenance release is slated for release on 30th Nov [1] [2]. Thus giving a 2 month head room to get to 4.0 work done, while maintaining the cadence of releasing every 3 months.<br>
<br>
This mail is to announce the scope, schedule and request contributors for the features that will make it to 3.13.<br>
<br>
1) Scope:<br>
3.13 is expected to be *lean* in scope, as most work is expected to be around 4.0 in the coming months. This STM can be considered as a sneak peek for some 4.0 features, that will *not* break any compatibility in the 3.x release line.<br>
<br>
2) The release calendar looks as follows,<br>
- Feature proposal end date: Sep-22-2017<br>
- Branching: Oct-16-2017<br>
</blockquote>
<br></span>
3.13 was not branched on time, primarily due to lack of attention from my side.<br>
<br>
I am planning on branching the release tomorrow (1st Nov 2017 @ 11:00 PM UTC) and as such have the following features in master that will be a part of this release, and need some information from the respective feature owners.<br>
<br>
1) Initial versions of GFProxy, possibly tech preview (issue #242)<br>
- Announced in the summit, so I made some changes to the issue in github<br>
- @poornimag are all things tech preview related already in the code?<br>
<br>
2) Data corruption in write ordering of rebalance and application writes (issue #308)<br>
- @raghavendrahg will this be ready in time before the branching?<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<items from here are either ready or done and there are no further details needed at present><br>
<br>
3) Include details about memory pools in statedumps (issue #307)<br>
<br>
4) posix: provide an option to reserve backend storage space (issue #236)<br>
<br>
5) Have max-port range in glusterd.vol (issue #305)<br>
<br>
6) snpashots issues with other processes accessing the mounted brick snapshots (issue #276)<br>
<br>
7) List all the connected clients for brick and also exported bricks / snaps from each brick process (issue #178)<br>
<br>
8) gfapi: APIs needed to register cbk functions for upcalls (issue #315)<br>
<br>
9) gfapi: new macros GLFS_XALLOC/GLFS_FREE adds a glfs_mem_header for exported memory (issue #312)<br>
<br>
10) Compilation warnings with gcc 7.x (issue #259) (partially fixed for 3.13)<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- Release: Nov-30-2017<br>
<br>
- Feature proposal:<br>
- Contributors need to request for features that will be a part of the 3.13 release, sending a mail to the devel list, and including the github issue # for the feature<br>
<br>
- Branching: date by when declared features (appearing in the release lane, in the github project board [3]) need to be completed, incomplete or features that are not ready by the branching date, would be pushed out to the next release.<br>
<br>
Thanks,<br>
Shyam<br>
<br>
[1] Github milestone: <a href="https://github.com/gluster/glusterfs/milestone/6" rel="noreferrer" target="_blank">https://github.com/gluster/glu<wbr>sterfs/milestone/6</a><br>
[2] Release schedule: <a href="https://www.gluster.org/release-schedule/" rel="noreferrer" target="_blank">https://www.gluster.org/releas<wbr>e-schedule/</a><br>
[3] Github project board: <a href="https://github.com/gluster/glusterfs/projects/1" rel="noreferrer" target="_blank">https://github.com/gluster/glu<wbr>sterfs/projects/1</a><br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br>
</blockquote>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a></div></div></blockquote></div><br></div></div>