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
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:
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
> following for 3.7.12:
>
> 1. Treat June 1st as the cut-off for patch acceptance in release-3.7.
> 2. I will tag 3.7.12rc1 on June 2nd.
Gentle reminder
Since we do not have any objections to this proposal, let us do the
following for 3.7.12:
1. Treat June 1st as the cut-off for patch acceptance in release-3.7.
2. I will tag 3.7.12rc1 on June 2nd.
3. All maintainers to ack content and stability of components by June 9th.
4. Release 3.7.12 around
On Fri, May 13, 2016 at 3:11 AM, Aravinda wrote:
> +1 from Geo-rep.
>
> Will explicit ack to be done in the mailing list?
>
Yes, sending out a note on gluster-devel would be appropriate. A
description of tests done etc. in the note would help us track and
improve quality
+1 from Geo-rep.
Will explicit ack to be done in the mailing list?
regards
Aravinda
On 05/10/2016 12:01 AM, Vijay Bellur wrote:
Hi All,
We are blocked on 3.7.12 owing to this proposal. Appreciate any
feedback on this!
Thanks,
Vijay
On Thu, Apr 28, 2016 at 11:58 PM, Vijay Bellur
Hi All,
We are blocked on 3.7.12 owing to this proposal. Appreciate any
feedback on this!
Thanks,
Vijay
On Thu, Apr 28, 2016 at 11:58 PM, Vijay Bellur wrote:
> Hi All,
>
> We have encountered a spate of regressions in recent 3.7.x releases. The
> 3.7.x maintainers are
Hi All,
We have encountered a spate of regressions in recent 3.7.x releases. The
3.7.x maintainers are facing additional burdens to ensure functional,
performance and upgrade correctness. I feel component maintainers should
own these aspects of stability as we own the components and