[Gluster-Maintainers] Maintainers acks needed for 3.7.12
Aravinda
avishwan at redhat.com
Thu Jun 16 05:54:29 UTC 2016
Thanks Kaushal for the reminder.
Following patches merged in Geo-rep after v3.7.12rc1, which are required
for 3.7.12 since these are regressions caused after the merge of
http://review.gluster.org/#/c/14322/
http://review.gluster.org/14641
http://review.gluster.org/14710
http://review.gluster.org/14637
I will acknowledge the working of Geo-replication components with the
above mentioned patches. Let me know if that is fine.
regards
Aravinda
On 06/15/2016 07:37 PM, Kaushal M wrote:
> Hi all,
>
> If anyone doesn't know about it yet, the release process for a release
> has changed. Refer to the mail thread [1] for more information.
>
> tl;dr, component maintainers need to now provide an acknowledgement
> that their component is ready to the release manager, for the manager
> to make the release. The maintainers are expected to test their
> components and make sure that it is not obviously broken. In the
> future, we expect to make this testing automated, which will require
> maintainers to provide these tests (using DiSTAF).
>
> Vijay, who's managing 3.7.12, sent out a call for acks [2], which
> hasn't recieved any acks apart from the Atin for GlusterD. It is
> possible that most of you missed this as it was part of another
> thread.
>
> I'm starting this thread as the official call for acks, so that it is
> more visible to all developers. I cc'd component maintainers (from
> MAINTAINERS) to make sure no one misses this.
>
> Use the tag v3.7.12rc1 to verify your components and provide your acks
> by replying to this thread.
>
> Thanks,
> Kaushal
>
> [1] https://www.gluster.org/pipermail/maintainers/2016-April/000679.html
> [2] https://www.gluster.org/pipermail/maintainers/2016-June/000847.html
More information about the maintainers
mailing list