[Gluster-Maintainers] Fwd: Re: [Gluster-users] Announcing GlusterFS release 3.12.0 (Long Term Maintenance)

[Shyam Ranganathan]

I would like to better understand why CentOS packages do not hit the SIG 
on time (defined as from RPMs built -> tested -> to announcement made, 
which is about 4 days this time around).

What is blocking this? What can change? What do we need to do as the 
gluster community to make this happen?

What question am I not asking?

Shyam

-------- Forwarded Message --------
Subject: Re: [Gluster-users] Announcing GlusterFS release 3.12.0 (Long 
Term Maintenance)
Date: Tue, 5 Sep 2017 21:07:11 +0300
From: Serkan Çoban <cobanserkan at gmail.com>
To: Shyam Ranganathan <srangana at redhat.com>
CC: announce at gluster.org

For rpm packages you can use [1], just installed without any problems.
It is taking time packages to land in Centos storage SIG repo...

[1] https://buildlogs.centos.org/centos/6/storage/x86_64/gluster-3.12/



On Tue, Sep 5, 2017 at 8:11 PM, Shyam Ranganathan <srangana at redhat.com> 
wrote:
> This is a major Gluster release that includes, features and bug fixes.
> Notable feature highlights are,
>
>     * Ability to mount sub-directories using the Gluster native protocol
> (FUSE)
>
>     * Brick multiplexing enhancements that help scale to larger brick counts
> per node
>
>     * Enhancements to gluster get-state CLI enabling better understanding of
> various bricks and nodes participation/roles in the cluster
>
>     * Ability to resolve GFID split-brain using existing CLI
>
>     * Easier GFID to real path mapping thus enabling diagnostics and
> correction for reported GFID issues (healing among other uses where GFID is
> the only available source for identifying a file)
>
> The features and changes are documented in the release notes [1]. A full
> list of bugs that have been addressed is included in the release notes as
> well [1].
>
> The packages can be downloaded from [2] and are signed with [3].
>
> Further, as 3.11 release is a short term maintenance release, features
> included in 3.11 are available with 3.12 as well, and could be of interest
> to users upgrading to 3.12 from older than 3.11 releases. The 3.11 release
> notes [2] captures the list of features that were introduced with 3.11.
>
> Upgrade guide for release-3.12 can be found here [4].
>
> Releases that will no longer receive updates (or are reaching EOL) with this
> release are: 3.11, 3.8 (see [5])
>
> Releases that will continue to be updated in the future as of this release
> are: 3.12, 3.10 (see [5])
>
> [1] 3.12.0 release notes:
> https://github.com/gluster/glusterfs/blob/release-3.12/doc/release-notes/3.12.0.md
>
> [2] Packages: https://download.gluster.org/pub/gluster/glusterfs/3.12/
>
> [3] Packages signed with:
> https://download.gluster.org/pub/gluster/glusterfs/3.12/rsa.pub
>
> [4] Upgrade guide to release 3.12:
> https://gluster.readthedocs.io/en/latest/Upgrade-Guide/upgrade_to_3.12/
>
> [5] Release schedule: https://www.gluster.org/release-schedule/
> _______________________________________________
> Announce mailing list
> Announce at gluster.org
> http://lists.gluster.org/mailman/listinfo/announce
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users