[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gluster-devel
Subject:    Re: [Gluster-devel] Release Management Process change - proposal
From:       Vijay Bellur <vbellur () redhat ! com>
Date:       2016-05-30 1:37:18
Message-ID: CAHn=sVDYNc+z_KC5WxPUwSMsibc0eqCY8B_1YV0xwdbw7ALf3w () mail ! gmail ! com
[Download RAW message or body]

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 June 9th after we have all acks in place.

Thanks!
Vijay



On Fri, May 13, 2016 at 9:10 AM, Vijay Bellur <vbellur@redhat.com> wrote:
> On Fri, May 13, 2016 at 3:11 AM, Aravinda <avishwan@redhat.com> 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 over a period of time.
>
> Thanks!
> Vijay
_______________________________________________
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel

[prev in list] [next in list] [prev in thread] [next in thread]