Thanks. i had a heads up before on another thread but I couldn’t do because of my workload on the task I was working on.
I will cut today and the vote thread sent tomorrow morning or later tonight. I personally want 2.7.0 out early next year. I will work proactively on that (and welcome anyone’s help on that) It would be nice to have large message streamed in AMQP as we convert to core right now. That’s the main thing I held a 2.7.0 release before. If I can’t do it I will still do it. But if anyone is willing to help here it would be awesome. On Mon, Dec 17, 2018 at 11:57 AM Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > I'd say it has already been too long since the last one so I wouldnt > wait until next year. A heads up is nice, and somewhat required when > its been a long cycle and especially so if previous heads up have been > missed. In this case I'd personally say it would be fine to proceed > even later today if it seems ready and noone specifically objects, so > it is out before people start to disappear for holidays. Other > versions numbers are still available if anyone needs to do another > release after. > > Robbie > > On Mon, 17 Dec 2018 at 16:03, Clebert Suconic <clebert.suco...@gmail.com> > wrote: > > > > Would be too bad if I cut this tomorrow? So we have time for a vote > before > > the Christmas week. Or anyone would rather have it next year ? > > > > I had promised few weeks back but i was busy with a big chunk of work > > around performance on AMQP. > > -- > > Clebert Suconic > -- Clebert Suconic
