Hi all, sorry about dropping the ball here. So going over the unresolved issues, I think these ones would be nice to tackle before cutting an RC:
* ZOOKEEPER-1833: fix windows build (one sub-task still opened: ZOOKEEPER-1868) * ZOOKEEPER-1029: C client bug in zookeeper_init (if bad hostname is given) (no one has this assigned, I'll try to get a patch out by tomorrow) * ZOOKEEPER-832: Invalid session id causes infinite loop during automatic reconnect (I've asked Rakesh if can wrap it up, if anyone else can help that would be great) * ZOOKEEPER-2033: zookeeper follower fails to start after a restart immediately following a new epoch (pinged Flavio to get some feedback) Everything else can probably be punted for 3.4.8, unless anyone disagrees. -rgs On 16 May 2015 at 13:41, Michi Mutsuzaki <[email protected]> wrote: > > Hi Raul, > > There are 13 unresolved issues marked for 3.4.7: http://s.apache.org/95J > > We should triage them and decide whether they need to be fixed in > 3.4.7 or then can be pushed out to 3.4.8. > > On Sat, May 16, 2015 at 9:43 AM, Raúl Gutiérrez Segalés > <[email protected]> wrote: > > On Apr 30, 2015 7:51 PM, "Raúl Gutiérrez Segalés" <[email protected]> > > wrote: > >> > >> Hi all, > >> > >> I went over all the tickets and I think we should be able to close them > > over the next week: > >> > >> http://goo.gl/6Jjtj1 > >> > >> After that, I'll cut an RC if that sounds reasonable. Thanks! > > > > I'd like to add one more: > > https://issues.apache.org/jira/browse/ZOOKEEPER-602. With that, I think > > we should be ready to cut an RC unless anyone thinks differently. > > > > > > -rgs
