[Gluster-Maintainers] [Gluster-devel] Release 4.0: Making it happen!

Amar Tumballi atumball at redhat.com
Thu Jan 18 03:35:01 UTC 2018

220 <https://github.com/gluster/glusterfs/issues?q=is%3Aissue+220>
I1cccb304a <https://review.gluster.org/#/q/I1cccb304a>I6e25dbb69
<https://review.gluster.org/#/q/If13913fa9> “[Cleanup] Dictionary data
structure and memory allocations” Amar
384 <https://github.com/gluster/glusterfs/issues?q=is%3Aissue+384>
I6111c13cf <https://review.gluster.org/#/q/I6111c13cf>I1448fbe9d
<https://review.gluster.org/#/q/I549b5e912> “RFE: new on-wire protocol
(XDR) needed to support iattx and cleaner dictionary structure” Amar

203 <https://github.com/gluster/glusterfs/issues?q=is%3Aissue+203>
I4d1235b9e <https://review.gluster.org/#/q/I4d1235b9e> “the protocol
xlators should prevent sending binary values in a dict over the networks”

Out of the above,

220 - will be an on-going effort. Some effort towards that is already
started, and merged.

384 - https://review.gluster.org/19098 is the patch with most of the
changes. I have now split the patch into two parts. Current one mostly will
pass the regression and just introduces all the new functionality. (best
way to do the diff is 'diff -pru client-rpc-fops.c client-rpc-fops_v2.c',
and similar on server to see if the diff is fine).

The other patch will follow and can be treated as a bug fix on the base
patch, and I am fine to send a rebase to release branch after it merges in
master later (but before release-4.0 happens).

203 - Is again a larger task, where individual translator owners should
make sure they don't have a specific binary type (or a structure) being
passed on wire, but have a proper encoding/decoding method for it.
Infrastructure to warn people about such 'keys' is already present. That is
the end of my task for the github, and would leave completion to
corresponding maintainers. (Everyone please look at logs :-)

So, help is needed with 384 for now. Thanks to Poornima who did help with
some reviews and feedback on patch, if she finds it fine, and someone else
helps with review, the patch may get merged today.


On Thu, Jan 18, 2018 at 1:17 AM, Vijay Bellur <vbellur at redhat.com> wrote:

> On Tue, Jan 16, 2018 at 7:27 AM, Shyam Ranganathan <srangana at redhat.com>
> wrote:
>> On 01/10/2018 01:14 PM, Shyam Ranganathan wrote:
>> > Hi,
>> >
>> > 4.0 branching date is slated on the 16th of Jan 2018 and release is
>> > slated for the end of Feb (28th), 2018.
>> This is today! So read on...
>> Short update: I am going to wait a couple more days before branching, to
>> settle release content and exceptions. Branching is hence on Jan, 18th
>> (Thursday).
>> >
>> > We are at the phase when we need to ensure our release scope is correct
>> > and *must* release features are landing. Towards this we need the
>> > following information for all contributors.
>> >
>> > 1) Features that are making it to the release by branching date
>> >
>> > - There are currently 35 open github issues marked as 4.0 milestone [1]
>> > - Need contributors to look at this list and let us know which will meet
>> > the branching date
>> Other than the protocol changes (from Amar), I did not receive any
>> requests for features that are making it to the release. I have compiled
>> a list of features based on patches in gerrit that are open, to check
>> what features are viable to make it to 4.0. This can be found here [3].
>> NOTE: All features, other than the ones in [3] are being moved out of
>> the 4.0 milestone.
>> > - Need contributors to let us know which may slip and hence needs a
>> > backport exception to 4.0 branch (post branching).
>> > - Need milestone corrections on features that are not making it to the
>> > 4.0 release
>> I need the following contributors to respond and state if the feature in
>> [3] should still be tracked against 4.0 and how much time is possibly
>> needed to make it happen.
>> - Poornima, Amar, Jiffin, Du, Susant, Sanoj, Vijay
> I request an extension till end of next week to complete my task.
> Thanks,
> Vijay
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> http://lists.gluster.org/mailman/listinfo/maintainers

Amar Tumballi (amarts)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20180118/cb5ab431/attachment.html>

More information about the maintainers mailing list