On Mon, May 01, 2017 at 09:24:57AM -0400, Shyam wrote: > On 05/01/2017 05:15 AM, Niels de Vos wrote: > > 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? > > See it here [5] > > It was a text file on my laptop (and shared with other current release > owners for 3.10 and 3.11) that was being refined across the releases and > should get reflected in the docs site sometime post 3.11 release, by when we > would have run through this a couple of times.
Right, I was looking at the docs and could not find it. Getting the page on a standard location would be good, we can improve it easy there as welll. > > > 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. > > Thank you for letting us know, this was not in the list. > > Who manages this? I do not see 3.10 here as well. Not sure, I've done the initial work, and Nigel did some improvements. Anyone that cares enough about the testing should be able to send a patch for it. Nigel has configured things to do automatic deployments, iirc, so no access to the CentOS CI Jenkins is needed. Niels > > > > > 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 > > > [5] Release tasks: https://hackmd.io/s/rJFbZ34kb# > - This may not be updated regularly, just a heads up, this is being put up > due to the query above. >
signature.asc
Description: PGP signature
_______________________________________________ maintainers mailing list [email protected] http://lists.gluster.org/mailman/listinfo/maintainers
