[Gluster-Maintainers] Release 5.4: Earlier than Mar-10th
Atin Mukherjee
amukherj at redhat.com
Tue Feb 26 11:50:40 UTC 2019
Milind - response inline.
Shyam - I'm not sure if you're tracking this. But at this point any blocker
bugs attached to 5.4 should also have clones of release-6 and attached to
the release tracker, otherwise we'll regress!
On Tue, Feb 26, 2019 at 5:00 PM Milind Changire <mchangir at redhat.com> wrote:
> On Fri, Feb 8, 2019 at 8:26 PM Shyam Ranganathan <srangana at redhat.com>
> wrote:
>
>> Hi,
>>
>> There have been several crashes and issues reported by users on the
>> latest 5.3 release. Around 10 patches have been merged since 5.3 and we
>> have a few more addressing the blockers against 5.4 [1].
>>
>> The original date was March 10th, but we would like to accelerate a 5.4
>> release to earlier this month, once all critical blockers are fixed.
>>
>> Hence there are 3 asks in this mail,
>>
>> 1) Packaging team, would it be possible to accommodate an 5.4 release
>> around mid-next week (RC0 for rel-6 is also on the same week)? Assuming
>> we get the required fixes by then.
>>
>> 2) Maintainers, what other issues need to be tracked as blockers? Please
>> add them to [1].
>>
>> 3) Current blocker status reads as follows:
>> - Bug 1651246 - Failed to dispatch handler
>> - This shows 2 patches that are merged, but there is no patch that
>> claims this is "Fixed" hence bug is still in POST state. What other
>> fixes are we expecting on this?
>> - @Milind request you to update the status
>>
> Bug 1651246 has been addressed.
> Patch has been merged on master
> <https://review.gluster.org/c/glusterfs/+/22221> as well as release-5
> <https://review.gluster.org/c/glusterfs/+/22237> branches.
> Above patch addresses logging issue only.
>
Isn't this something which is applicable to release-6 branch as well? I
don't find https://review.gluster.org/#/c/glusterfs/+/22221/ in release-6
branch which means we're going to regress this in release 6 if this isn't
backported and marked as blocker to release 6.
>
>> - Bug 1671556 - glusterfs FUSE client crashing every few days with
>> 'Failed to dispatch handler'
>> - Awaiting fixes for identified issues
>> - @Nithya what would be the target date?
>>
>> - Bug 1671603 - flooding of "dict is NULL" logging & crash of client
>> process
>> - Awaiting a fix, what is the potential target date for the same?
>> - We also need the bug assigned to a person
>>
> Bug 1671603 has been addressed.
> Patch has been posted on master
> <https://review.gluster.org/c/glusterfs/+/22126> and merged on release-5
> <https://review.gluster.org/c/glusterfs/+/22127> branches.
>
Are you sure the links are correct? Patch posted against release 5 branch
is abandoned? And also just like above, same question for release-6 branch,
I don't see a patch?
Above patch addresses logging issue only.
>
>
>> Thanks,
>> Shyam
>>
>> [1] Release 5.4 tracker:
>> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4
>> _______________________________________________
>> maintainers mailing list
>> maintainers at gluster.org
>> https://lists.gluster.org/mailman/listinfo/maintainers
>>
>
>
> --
> Milind
>
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20190226/6152a31f/attachment-0001.html>
More information about the maintainers
mailing list