Re: Release Management Process change - proposal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx> wrote:
> On Fri, May 13, 2016 at 3:11 AM, Aravinda <avishwan@xxxxxxxxxx> 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@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux