One last note (for now):
For RC0 we would like to have relevant release notes for features that
are a part of the release.
Towards this, I have submitted an initial template version of the
release notes [1], and would like to encourage all contributors who have
features submitted (or even ot
Hi,
We would tag the 3.12 release branch RC0 on 31st July, (say 1:00 PM
Eastern TZ [1]).
All features that have been granted an exception for a backport, should
be merged (or read for a merge) by this time, for a smooth RC0 tagging.
Further, post RC0 we would be generating packages as well
Hi,
Release 3.12 has been branched today, and the following branches and
tags created on our git repo.
- release-3.12 [1]
- v3.12.0alpha1 tag [2]
- v4.0dev tag [2]
What this means:
- Fixes for bugs need to be backported to 3.12 branch going forward
- As of this mail, the active bra
Hi,
Prepare for a lengthy mail, but needed for the 3.12 release branching,
so here is a key to aid the impatient,
Key:
1) If you asked for an exception to a feature (meaning delayed backport
to 3.12 branch post branching for the release) see "Section 1"
- Handy list of nick's that maybe in
Hi,
3.11.2 has been tagged and packaging is underway, thanks to all for your
contributions and help. Release notes are here [2].
With this the release tracker bug for 3.11.2 is closed and a 3.11.3
tracker is open [1]. Future blocker bugs for 3.11.3 need to be marked as
a blocker against this
On Fri, Jul 21, 2017 at 3:26 AM, Raghavendra Gowdappa
wrote:
> Hi all,
>
> We've a bug [1], due to which read-ahead is completely disabled when the
> workload is read-only. One of the easy fix was to make read-ahead as an
> ancestor of open-behind in xlator graph (Currently its a descendant). A
>
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-07-21-88af8d7a
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
Hi all,
We've a bug [1], due to which read-ahead is completely disabled when the
workload is read-only. One of the easy fix was to make read-ahead as an
ancestor of open-behind in xlator graph (Currently its a descendant). A patch
has been sent out by Rafi to do the same. As noted in one of the
