> On 18 Dec 2015, at 11:10, Ivan Kelly <[email protected]> wrote: > >> +1 on removing 3.4.7. If others speak up soon I can go ahead and remove >> 3.4.7 from the website/archive and get started with the RC.. > Just to clarify, you'll only remove the archive and not touch the > maven repo? The issue is only in the server, and people are already > using the client via maven so deleting from maven would break them. > Also, the client has some fixes in 3.4.7 which we consider critical. >
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. -Flavio
