> The same fixes that are in 3.4.7 will be in 3.4.8, and we'll add the one to > the deadlock. I was thinking that we should remove it from the maven repo too > and ask people to move their dependencies back to 3.4.6. I'm fine if you want > to hold removing 3.4.7 from the maven repo until we have 3.4.8 out, but I > think we should do it as a way of really preventing folks from using it in > the future.
This will break people. We've already moved all versions of our software to 3.4.7 (due to a client hitting https://issues.apache.org/jira/browse/ZOOKEEPER-706). If 3.4.7 is removed from the repo it will force a change for us. Maven is used primarily to pull zookeeper to be used a a client. There's no (known) problem with the client, so there's no problem with people continuing to use it as a client, even when 3.4.8 is out. -Ivan
