[Gluster-Maintainers] Release 3.7.2 in progress, do not merge patches into the release-3.7 branch

Atin Mukherjee amukherj at redhat.com
Fri Jun 19 05:45:08 UTC 2015

On 06/19/2015 10:01 AM, Atin Mukherjee wrote:
> On 06/19/2015 09:16 AM, Pranith Kumar Karampuri wrote:
>> hi Atin,
>>      I saw the mail just now after merging
>> http://review.gluster.org/11152 :-(.
>>      From EC side http://review.gluster.org/11319 is a show stopper. It
>> fixes a potential data corruption that Bhaskar saw on his setup for
>> appending writes. But it was submitted for review just now.
> I will wait for another couple of hours for pushing the tag. By this
> time if it passes the regression we can merge it otherwise we will have
> to mark it as a known issue and move it for 3.7.3. Does it make sense?
I've sent the patch [1] for release notes for 3.7.2
Kindly review.


I've put the EC bug as known issue as of now, if gets merged I will
modify the release note accordingly, but that has to happen in another
two hours of time ;)

[1] http://review.gluster.org/11320

> ~Atin
>> Pranith
>> On 06/18/2015 11:41 PM, Atin Mukherjee wrote:
>>> Hi All,
>>> As I've started working on the release notes for 3.7.2, I would request
>>> all the maintainers not to merge any patches in release-3.7 till I
>>> create the tag. review.gluster.org/11091 would be considered as an
>>> exception here as its a show stopper and this patch is waiting for
>>> NetBSD's vote since few days. Apart from it, I don't think we have any
>>> functional blockers, if we do, please let me know by today such that my
>>> release note doesn't get affected too much.
>>> Please let me know in case of any issue/concern.


More information about the maintainers mailing list