we also need cycles to fill up the documentation for the new features introduced in 4.6.0, like new API, http endpoints.
On Mon, Oct 30, 2017 at 11:58 AM, Sijie Guo <guosi...@gmail.com> wrote: > Hi all, > > just a reminder here - it has been 2 weeks pass the planned code freeze > week and 2 weeks left for the deadline of 4.6.0 release. > > It is our first release after switch to a time-based release schedule. It > would be great that we can stick to the release schedule. > > We already 131 closed issues and 16 open issues for 4.6.0. There are quite > a lot of good changes there: > > - fileinfo cache improvement > - replication worker fixes for respecting to placement policy > - http endpoints > - new ledger api > - lifecycle components > - persistable bookie status > - abstract service discovery interface > - protobuf upgrade > - gc related improvements (using netty recycle object pools) > > If BP-14 is going to take much longer time, I would suggest moving it into > next release cycle. > > - Sijie > > > On Sat, Oct 21, 2017 at 4:27 AM, Jia Zhai <zhaiji...@gmail.com> wrote: > >> 👍 >> >> On Fri, Oct 20, 2017 at 1:21 PM, Enrico Olivelli <eolive...@gmail.com> >> wrote: >> >> > Il ven 20 ott 2017, 06:51 Jia Zhai <zhaiji...@gmail.com> ha scritto: >> > >> > > Sounds good to me. Let's postpone it. >> > > >> > >> > Thank you >> > Maybe this way we will have time to clean up a few flaky tests >> > >> > Enrico >> > >> > >> > > On Fri, Oct 20, 2017 at 12:37 AM, Enrico Olivelli < >> eolive...@gmail.com> >> > > wrote: >> > > >> > > > Hi Jia, >> > > > I think it would be time to freeze 4.6 but I would like to have some >> > more >> > > > time to include BP14 in 4.6. >> > > > I think that 3 weeks would be good. >> > > > >> > > > Thoughts? >> > > > >> > > > Enrico >> > > > -- >> > > > >> > > > >> > > > -- Enrico Olivelli >> > > > >> > > >> > -- >> > >> > >> > -- Enrico Olivelli >> > >> > >
