[Gluster-Maintainers] [Gluster-devel] Release 3.10: Backports (reminder and action needed)
srangana at redhat.com
Tue Feb 21 16:19:07 UTC 2017
Status on this looks good. Further backports that made it to 3.9/3.8
have also made it to 3.10
On 02/15/2017 10:22 AM, Shyam wrote:
> Checking back on status this week.
> Everything looks good, the 2 missing backports are also in (thanks Ashish).
> We probably will have one last check pre-release.
> On 02/06/2017 01:12 PM, Shyam wrote:
>> A recheck after one more week, and our status is healthy, backports that
>> appear in 3.8 or 3.9 are appearing against 3.10 as well. Thank you.
>> However the exception raised last week is not handled yet.
>> The following commits were merged into master post 3.10 branching and
>> also backported to 3.9. Essentially this would mean they need to be
>> backported to 3.10 as well, but are missing against that release.
>> Request one of you to take a look and let us know if these backports are
>> needed, and if so backport the same.
>> 1) https://review.gluster.org/#/c/16439/
>> Commit message: cluster/disperse: Do not log fop failed for lockless fops
>> Commit in release 3.9: 0f63bda0df91ee7ff42e3262c74220178ef87a21
>> 2) https://review.gluster.org/#/c/16444/
>> Commit message: cluster/ec: Do not start heal on good file while IO is
>> going on
>> Commit in release 3.9: bc1ce55a7c83c7f5394b26a65bd4a3a669b5962a
>> On 01/26/2017 03:09 PM, Shyam wrote:
>>> As we have branched release 3.10 (some time ago), patches that are being
>>> backported to 3.8/9 and are *applicable* to 3.10 need to be backported
>>> to 3.10 as well.
>>> An analysis of this state since branching shows the following commits in
>>> 3.9 not backported to 3.10. Ashish, request you to address this at your
>>> bc1ce55a7c83c7f5394b26a65bd4a3a669b5962a (Ashish Pandey) Wed, 11 Jan
>>> 2017 17:19:30 +0530 cluster/ec: Do not start heal on good file while IO
>>> is going on
>>> 0f63bda0df91ee7ff42e3262c74220178ef87a21 (Ashish Pandey) Thu, 19 Jan
>>> 2017 18:20:44 +0530 cluster/disperse: Do not log fop failed for lockless
>>> Gluster-devel mailing list
>>> Gluster-devel at gluster.org
>> maintainers mailing list
>> maintainers at gluster.org
> Gluster-devel mailing list
> Gluster-devel at gluster.org
More information about the maintainers