I think that it is better to sort out the CI stuff for validating PRs before moving ahead with the next release. There was a recent mail from Bharat on a sample CI BVT run. As I understand it is still WIP, but once the remaining items are fixed it will be useful for validating PRs.
Also I can be the 2nd RM along with Will for the next release. -Koushik > On 25-Feb-2016, at 10:13 PM, Will Stevens <wstev...@cloudops.com> wrote: > > I am willing to step up as the RM for 4.9. I need to get caught up on the > workflow and what CI we have in place etc... Any help getting caught up on > how we are currently working would be appreciated. I need to get my lab > setup to start testing and working through the different PRs, so I am still > a little ways out from being able to actually get things moving. > > *Will STEVENS* > Lead Developer > > *CloudOps* *| *Cloud Solutions Experts > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > w cloudops.com *|* tw @CloudOps_ > > On Wed, Feb 10, 2016 at 3:58 AM, Sebastien Goasguen <run...@gmail.com> > wrote: > >> Morning folks, >> >> We have several crucial pending items, that we need to resolve before >> moving on: >> >> 1- We need an RM for master ( just saw some commits there that should be >> reverted or merged properly in other branches). >> >> 2- We need to automate writing release notes, pushing/tagging new docs >> when release come out and announcing releases on website. Currently neither >> 4.7 nor 4.8 have been announced. >> >> 3- CI is still almost inexistent >> >> -Sebastien
