[Gluster-Maintainers] Jenkins build is back to normal : regression-test-burn-in #1089

See ___ maintainers mailing list maintainers@gluster.org http://www.gluster.org/mailman/listinfo/maintainers

[Gluster-Maintainers] Jenkins build is back to normal : regression-test-burn-in #1091

See ___ maintainers mailing list maintainers@gluster.org http://www.gluster.org/mailman/listinfo/maintainers

[Gluster-Maintainers] Build failed in Jenkins: regression-test-burn-in #1088

+ RET=1 ++ ls -l '/*.core' ++ wc -l + cur_count=0 ++ ls '/*.core' + cur_cores= + '[' 0 '!=' 0 ']' + '[' 1 -ne 0 ']' + filename=logs/glusterfs-logs-20160603:08:39:09.tgz + tar -czf /archives/logs/glusterfs-logs-20160603:08:39:09.tgz /var/log/glusterfs /var/log/messages /var/log/messages-20160508 /v

Re: [Gluster-Maintainers] [Gluster-devel] Release Management Process change - proposal

Hi Vijay, Discovered two regression issues in Geo-rep, identified the fix and patch posted to master and release-3.7. Waiting for regression tests run. Is it possible to take these patches for 3.7.12? Master: BZ http://review.gluster.org/14636 http://review.gluster.org/14425 Release-3.7:

Re: [Gluster-Maintainers] [Gluster-devel] Release Management Process change - proposal

On Fri, Jun 3, 2016 at 8:51 AM, Aravinda wrote: > Hi Vijay, > > Discovered two regression issues in Geo-rep, identified the fix and patch > posted to master and release-3.7. Waiting for regression tests run. > > Is it possible to take these patches for 3.7.12? Sure, I will

Re: [Gluster-Maintainers] [Gluster-devel] Release Management Process change - proposal

On Fri, Jun 3, 2016 at 10:16 AM, Niels de Vos wrote: > On Thu, Jun 02, 2016 at 10:55:58PM -0400, Vijay Bellur wrote: >> On Sun, May 29, 2016 at 9:37 PM, Vijay Bellur wrote: >> > Since we do not have any objections to this proposal, let us do the >> >