Hi,
It's time to prepare the 3.12.6 release, which falls on the 10th of
each month, and hence would be 12-02-2018 this time around.
This mail is to call out the following,
1) Are there any pending *blocker* bugs that need to be tracked for
3.12.6? If so mark them against the provided tracker [1
This seems to be working well so far. I noticed that this one doesn't vote
correctly. I've fixed this up and also fixed up all the jobs where the
voting wasn't accurate.
Overall regression time seems to have dropped down to 3.5h now from 6h or
so. I attribute this to less slower down in some speci
On 01/29/2018 05:10 PM, Shyam Ranganathan wrote:
> Hi,
>
> I have posted an initial draft version of the release notes here [1].
>
> I would like to *suggest* the following contributors to help improve and
> finish the release notes by 06th Feb, 2017. As you read this mail, if
> you feel you cann
On Thu, Feb 1, 2018 at 2:48 PM, Shyam Ranganathan
wrote:
> On 02/01/2018 08:25 AM, Xavi Hernandez wrote:
> > After having tried several things, it seems that it will be complex to
> > solve these races. All attempts to fix them have caused failures in
> > other connections. Since I've other work
On 02/01/2018 08:25 AM, Xavi Hernandez wrote:
> After having tried several things, it seems that it will be complex to
> solve these races. All attempts to fix them have caused failures in
> other connections. Since I've other work to do and it doesn't seem to be
> causing serious failures in produ
After having tried several things, it seems that it will be complex to
solve these races. All attempts to fix them have caused failures in other
connections. Since I've other work to do and it doesn't seem to be causing
serious failures in production, for now I'll leave this. I'll retake this
when
GlusterFS Coverity covscan results are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-02-01-d663b9a3
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman
All pending actions as noted in the mail are complete, and 4.0.0rc0 has
been tagged.
This brings us to the most important phase of 4.0 which is testing out
things that are not covered in our automated regression runs and such.
For now, let's get some packages (as soon as I trigger the release job