Hi, I can jump in and work with Rohit and Daan to make 4.6 happen.
+1 for the QA on master. It would be best if we could then all focus on stabilizing 4.6 aka master and wait with refactor stuff and new features until 4.6 is out, which is the start of 4.7. On the other hand, building new features in the mean time isn't a big issue, as rebasing to a master that gets more stable every day is much easier than it is today I'd say. You just cannot merge new stuff until 4.6 is out. Let's write down some guidelines and see if this approach makes sense. Regards, Remi > On 08 Jun 2015, at 21:43, Sebastien Goasguen <run...@gmail.com> wrote: > > Folks, > > We need to freeze 4.6 asap. > > I originally agreed to RM 4.6 and Daan also stepped up. > > But I would like to work on doing a release of ec2stack and gcestack, so I > will step down from 4.6 RM. > > Anybody wants to jump in. > > There is already a ton of things in 4.6 and we need to release. > > Ideally we also need to QA directly on master, so that we can build 4.7 on > top of a stable release. > > > -sebastien
