The plan is indeed to cut an RC for 3.4.8 early January with this issue fixed. Raul volunteered to do it, but because folks will be away during the holidays, I'm suggesting we wait until after the holidays to bootstrap the process. But, if Raul wants to cut an RC now, I'm totally fine with it as long as we give enough time to folks to review it and vote.
A slightly separate issue is what to do with 3.4.7. It is a bad release and we don't want folks using it, so I started this discussion to determine what to do with it. I'm suggesting we remove it from mirrors and from the web site, just like we did with 3.3.1 back in the day. -Flavio > On 18 Dec 2015, at 09:34, Ivan Kelly <[email protected]> wrote: > >> The specific issue is described and it is being discussed in ZOOKEEPER-2347. >> Please share your opinion about the 3.4.7 release in this thread. > It looks like there's already a fix for the issue and very little has > gone into 3.4 since the release, so why no release a 3.4.8? > > -Ivan
