Thanks everyone for the feedback, I'll move this to a vote, but feel free to give more feedback here if there is anything important we've missed.
-Flavio > On 18 Dec 2015, at 19:30, Chris Nauroth <[email protected]> wrote: > > +1 for removal of 3.4.7 from the Apache mirrors. > > Removing something from Maven is tricky. Ivan pointed out that this will > break established builds. Also, a lot of people run their own private > mirrors of the central repository. By now, they would have replicated a > copy of 3.4.7. For users of those mirrors, they'll still be able to > establish a dependency on 3.4.7. We can try to remove the master copy, > but the nature of Maven's release process means that once something goes > out in the wild, it never can really be taken back completely. > > --Chris Nauroth > > > > > On 12/18/15, 9:08 AM, "Flavio Junqueira" <[email protected]> wrote: > >> If you can get your users to upgrade to 3.4.8 once it is out and give a >> grace period so that we can remove it from maven eventually, then better. >> If not, then let's leave it there. It is true that people use the maven >> dependency mostly if not uniquely because of the client, but I'd rather >> not generate any confusion about it being in one place and not in another >> if we can avoid it. >> >> -Flavio >> >>> On 18 Dec 2015, at 15:00, Ivan Kelly <[email protected]> wrote: >>> >>>> 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 >> >> >
