[Gluster-Maintainers] Release 3.11: Has been Branched (and pending feature notes)

Niels de Vos ndevos at redhat.com
Mon May 1 09:15:43 UTC 2017

On Sun, Apr 30, 2017 at 11:31:37AM -0400, Shyam wrote:
> Hi,
> Release 3.11 for gluster has been branched [1] and tagged [2].
> We have ~4weeks to release of 3.11, and a week to backport features that
> slipped the branching date (May-5th).

Do we have a list of tasks that need to be performed upon branching?
I've seen emails for the Gerrit merge permissions, but am not sure about
other bits (Bugzilla version seems to exist already). At least someone
should look into the nightly builds+tests for the CentOS CI [4], let me
know if I should have a go at it.


> [1] 3.11 Branch: https://github.com/gluster/glusterfs/tree/release-3.11
> [2] Tag for 3.11.0beta1 :
> https://github.com/gluster/glusterfs/tree/v3.11.0beta1

With tags like this we need to add a release note that users who tested
packages with this version will need to downgrade when GA is done. This
is because 

    $ rpmdev-vercmp 3.11.0beta1 3.11.0-1
    3.11.0beta1 > 3.11.0-1

The previous scheme (like 3.10rc1) forced updates to users when the .0
release became available. Why was this changed?

> [3] Tracker BZ for 3.11.0 blockers:
> https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.0

[4] https://github.com/gluster/glusterfs-patch-acceptance-tests/issues/83
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20170501/bb348e70/attachment.sig>

More information about the maintainers mailing list