Re: [Gluster-Maintainers] Release manager for GlusterFS 3.9 needed

2016-06-21 Thread Pranith Kumar Karampuri
On Tue, Jun 21, 2016 at 4:41 PM, Niels de Vos wrote: > On Tue, Jun 21, 2016 at 04:10:20PM +0530, Pranith Kumar Karampuri wrote: > > hi, > >maintaining a release by single person does take a lot of time > away > > from development. Is it okay if two people maintain the

Re: [Gluster-Maintainers] Release manager for GlusterFS 3.9 needed

2016-06-21 Thread Niels de Vos
On Tue, Jun 21, 2016 at 04:42:29PM +0530, Pranith Kumar Karampuri wrote: > On Tue, Jun 21, 2016 at 4:41 PM, Niels de Vos wrote: > > > On Tue, Jun 21, 2016 at 04:10:20PM +0530, Pranith Kumar Karampuri wrote: > > > hi, > > >maintaining a release by single person does

[Gluster-Maintainers] Release manager for GlusterFS 3.9 needed

2016-06-21 Thread Niels de Vos
Hello all! As GlusterFS 3.8 has been released, we need to start planning the 3.9 release. It would be best if someone volunteers for this task so that we stick to the release schedule. 3.9 is planned to be released in three months, that would be September this year. With this release cycle the

Re: [Gluster-Maintainers] Release manager for GlusterFS 3.9 needed

2016-06-21 Thread Pranith Kumar Karampuri
hi, maintaining a release by single person does take a lot of time away from development. Is it okay if two people maintain the release? If yes, Aravinda and I would like to volunteer. On Tue, Jun 21, 2016 at 3:13 PM, Niels de Vos wrote: > Hello all! > > As GlusterFS

Re: [Gluster-Maintainers] Maintainers acks needed for 3.7.12

2016-06-21 Thread Niels de Vos
On Wed, Jun 15, 2016 at 07:37:02PM +0530, Kaushal M wrote: > Hi all, > > If anyone doesn't know about it yet, the release process for a release > has changed. Refer to the mail thread [1] for more information. > > tl;dr, component maintainers need to now provide an acknowledgement > that their

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

2016-06-21 Thread jenkins
t - 0 second ./tests/basic/exports_parsing.t - 0 second Result is 1 + RET=1 ++ wc -l ++ ls -l '/*.core' + cur_count=0 ++ ls '/*.core' + cur_cores= + '[' 0 '!=' 0 ']' + '[' 1 -ne 0 ']' + filename=logs/glusterfs-logs-20160621:15:48:19.tgz + tar -czf /archives/logs/glusterfs-logs-20160621:15:4

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

2016-06-21 Thread jenkins
See ___ maintainers mailing list maintainers@gluster.org http://www.gluster.org/mailman/listinfo/maintainers