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. Thanks, Niels <snip> > [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
signature.asc
Description: PGP signature
_______________________________________________ maintainers mailing list [email protected] http://lists.gluster.org/mailman/listinfo/maintainers
