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

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

 



On Fri, Jun 3, 2016 at 10:16 AM, Niels de Vos <ndevos@xxxxxxxxxx> 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 <vbellur@xxxxxxxxxx> 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 - I will be tagging 3.7.12rc1 in about 12 hours from
>> now. Please merge patches needed for 3.7.12 by then. Post that,
>> patches would be pushed out to 3.7.13.
>
> I thought we didnt do the rc releases for the stable versions anymore?
> What is the reason for this change?
>

This is for the convenience of maintainers to submit their feedback on
the release content. A tag is more convenient than a commit ID to
provide feedback and log bugs if necessary. Hence the change.

Regards,
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