<div dir="ltr">Hi Amar,<br><br>We will be branching out release 11 this week.<br><br>Regards,<br>Shwetha</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 7, 2022 at 9:47 AM Amar Tumballi <<a href="mailto:amar@kadalu.io">amar@kadalu.io</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Other than 2 large PRs (CDC and zlib changes) we don't have any major pending tasks. I would like to propose we keep up with the proposed dates, and go ahead with the branching. If we merge these PRs, we can rebase and send it to the branch again.<div><br></div><div>Shwetha Can you please go ahead with the branching related activities?</div><div><br></div><div>-Amar</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 17, 2022 at 3:24 PM Xavi Hernandez <<a href="mailto:jahernan@redhat.com" target="_blank">jahernan@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Mon, Oct 17, 2022 at 10:40 AM Yaniv Kaul <<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="font-family:arial,helvetica,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 17, 2022 at 8:41 AM Xavi Hernandez <<a href="mailto:jahernan@redhat.com" target="_blank">jahernan@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">On Mon, Oct 17, 2022 at 4:03 AM Amar Tumballi <<a href="mailto:amar@kadalu.io" target="_blank">amar@kadalu.io</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Here is my honest take on this one.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 11, 2022 at 3:06 PM Shwetha Acharya <<a href="mailto:sacharya@redhat.com" target="_blank">sacharya@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">It is time to evaluate the fulfillment of our committed features/improvements and the feasibility of the proposed deadlines as per <a href="https://github.com/gluster/glusterfs/issues/3023" target="_blank">Release 11 tracker</a>.<br><br><br>Currently our timeline is as follows:<br><span style="background-color:rgb(255,255,255)"><font color="#000000"><br style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"><span style="box-sizing:border-box;font-weight:600;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px">Code Freeze:</span><span style="font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"> 31-Oct-2022</span><br style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"><span style="box-sizing:border-box;font-weight:600;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px">RC :</span><span style="font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"> 30-Nov-2022</span><br style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"><span style="box-sizing:border-box;font-weight:600;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px">GA :</span><span style="font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px"> 10-JAN-2023</span></font></span><br><br><b>Please evaluate the following and reply to this thread if you want to convey anything important:</b><div><br>- Can we ensure to fulfill all the proposed requirements by the Code Freeze?<br>- Do we need to add any more changes to accommodate any shortcomings or improvements?<br>- Are we all good to go with the proposed timeline?<br><br></div></div></blockquote><div><br></div><div>We have delayed the release already by more than 1year, and that is a significant delay for any project. If the changes we work on is not getting released frequently, the feedback loop for the project is delayed and hence the further improvements. So, regardless of any pending promised things, we should go ahead with the code-freeze and release on these dates.</div><div><br></div><div>It is crucial for any projects / companies dependent on the project to plan accordingly. There may be already few others who would have planned their product release around these dates. Lets keep the same dates, and try to achieve the tasks we have planned in these dates.</div></div></div></blockquote><div><br></div><div>I agree. Pending changes will need to be added to next release. Doing it at last time is not safe for stability.</div></div></div></blockquote><div><br></div><div style="font-family:arial,helvetica,sans-serif">Generally, +1. </div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">- Some info on my in-flight PRs:</div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">I have multiple independent patches for the flexible array member conversion of different variables that are pending:</div><div style="font-family:arial,helvetica,sans-serif"><a href="https://github.com/gluster/glusterfs/pull/3873" target="_blank">https://github.com/gluster/glusterfs/pull/3873</a></div><div style="font-family:arial,helvetica,sans-serif"><a href="https://github.com/gluster/glusterfs/pull/3872" target="_blank">https://github.com/gluster/glusterfs/pull/3872</a></div><div style="font-family:arial,helvetica,sans-serif"><a href="https://github.com/gluster/glusterfs/pull/3868" target="_blank">https://github.com/gluster/glusterfs/pull/3868</a>  (this one is particularly interesting, I hope it works!)</div><div style="font-family:arial,helvetica,sans-serif"><a href="https://github.com/gluster/glusterfs/pull/3861" target="_blank">https://github.com/gluster/glusterfs/pull/3861</a></div><div style="font-family:arial,helvetica,sans-serif"><a href="https://github.com/gluster/glusterfs/pull/3870" target="_blank">https://github.com/gluster/glusterfs/pull/3870</a> (already in review, perhaps it can get it soon?)<br></div></div></div></blockquote><div><br></div><div>I'm already looking at these and I expect they can be merged before the current code-freeze date.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div style="font-family:arial,helvetica,sans-serif"></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">I have this for one for inode related code, which got some attention recently:</div><div style="font-family:arial,helvetica,sans-serif"><a href="https://github.com/gluster/glusterfs/pull/3226" target="_blank">https://github.com/gluster/glusterfs/pull/3226</a></div></div></div></blockquote><div><br></div><div>I'll try to review this one before code-freeze, but it requires much more care. Any help will be appreciated.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">I think this one is worthwhile looking at:</div><div style="font-family:arial,helvetica,sans-serif"><a href="https://github.com/gluster/glusterfs/pull/3854" target="_blank">https://github.com/gluster/glusterfs/pull/3854</a></div></div></div></blockquote><div><br></div><div>I'll try to take a look at this one also.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">I wish we could get rid of old, unsupported versions:</div><div style="font-family:arial,helvetica,sans-serif"><a href="https://github.com/gluster/glusterfs/pull/3544" target="_blank">https://github.com/gluster/glusterfs/pull/3544</a></div><div style="font-family:arial,helvetica,sans-serif">(there's more to do, in different patches, but it's a start)</div></div></div></blockquote><div><br></div><div>This one is mostly ok, but I think we can't release a new version without an explicit check for unsupported versions at least at the beginning, to avoid problems when users upgrade directly from 3.x to 11.x.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">None of them is critical for release 11, though I'm unsure if I'll have the ability to complete them later.</div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif"><div>- The lack of EL9 official support (inc. testing infra.) is regrettable, and I think something worth fixing <b>before</b> release 11 - adding sanity on newer OS releases, which will use io_uring for example, is something we should definitely consider.</div><div><br></div></div><div style="font-family:arial,helvetica,sans-serif">Lastly, I thought zstandard compression to the CDC xlator is interesting for 11 (<a href="https://github.com/gluster/glusterfs/pull/3841" target="_blank">https://github.com/gluster/glusterfs/pull/3841</a>) - unsure if it's ready for inclusion, but overall impact for stability should be low, considered this is not a fully supported xlator anyway (and then <a href="https://github.com/gluster/glusterfs/pull/3835" target="_blank">https://github.com/gluster/glusterfs/pull/3835</a> should / could be considered as well).</div></div></div></blockquote><div><br></div><div>I already started the review but I'm not very familiarized with cdc and the compression libraries, so I'll need some more time.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">Last though:<br></div><div style="font-family:arial,helvetica,sans-serif">If we are just time-based - sure, there's value in going forward and releasing it - there are hundreds (or more) of great patches already merged, I think there's value here.</div><div style="font-family:arial,helvetica,sans-serif">If we wish to look at features and impactful changes to the users - I suggest we review <a href="https://github.com/gluster/glusterfs/issues/3023" target="_blank">https://github.com/gluster/glusterfs/issues/3023</a> , we look at what's missing, what's in-flight and can get in, draft the release announcement and see if there's enough content.</div></div></div></blockquote><div><br></div><div>At this point I don't think any of the remaining big features can be added, and given that release 11 has already been delayed quite a bit, I agree with Amar that we should provide a new version soon. I think it already contains very interesting changes that can improve performance and stability.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div style="font-family:arial,helvetica,sans-serif"><br></div><div style="font-family:arial,helvetica,sans-serif">(I'm for the former, I just think the latter is a good reasonable exercise to see what's in 11!)</div><div style="font-family:arial,helvetica,sans-serif">Y.</div><div style="font-family:arial,helvetica,sans-serif"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div><br></div><div>Xavi</div></div></div>
-------<br>
<br>
Community Meeting Calendar:<br>
Schedule -<br>
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
Bridge: <a href="https://meet.google.com/cpu-eiue-hvk" rel="noreferrer" target="_blank">https://meet.google.com/cpu-eiue-hvk</a><br>
<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
<br>
</blockquote></div></div>
</blockquote></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr">--<div><a href="https://kadalu.io" target="_blank">https://kadalu.io</a></div><div>Container Storage made easy!</div><div><br></div></div></div>
</blockquote></div>