On Wed, Jun 15, 2016 at 07:37:02PM +0530, 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.
I actually used the nightly builds from here: http://artifacts.ci.centos.org/gluster/nightly/ Save the release-3.7.repo file under /etc/yum.repos.d/ on a CentOS-6 or CentOS-7 system. Then execute these commands: # yum install centos-release-gluster37 # yum install glusterfs-server This should install the last nightly build for 3.7. Gluster/NFS seems to be fine. Basic NFS works, and cthon passes too. Niels > Thanks, > Kaushal > > [1] https://www.gluster.org/pipermail/maintainers/2016-April/000679.html > [2] https://www.gluster.org/pipermail/maintainers/2016-June/000847.html
signature.asc
Description: PGP signature
_______________________________________________ maintainers mailing list maintainers@gluster.org http://www.gluster.org/mailman/listinfo/maintainers
