I see - this would be done in Ivy. OK by me. So, to summarize, there are 3 possibilities:
* Push Curator into ZooKeeper proper under a new recipes artifact. Curator would get n committers from Netflix with the understanding that their focus is on Curator * Start a sub-project ala BookKeeper for ZooKeeper with its own committer list * Put Curator into the Incubator and follow that road Ted (and now I) prefer the first option. I believe Patrick prefers the third option but would accept the second. How do the others feel? -JZ On 12/5/11 3:06 PM, "Ted Dunning" <ted.dunn...@gmail.com> wrote: >There would be two artifacts. The recipes artifact would have a >particular >version of ZK as a dependency. There might be point releases of the >recipes to backport features. > >It is customary with tightly coupled things like this to synchronize major >version numbers. With ZK, major and minor might be appropriate. That >doesn't affect the schedule, however. > >On Mon, Dec 5, 2011 at 2:55 PM, Jordan Zimmerman ><jzimmer...@netflix.com>wrote: > >> How would that work? >> >> On 12/5/11 2:49 PM, "Ted Dunning" <ted.dunn...@gmail.com> wrote: >> >> >I don't think that is necessary. >> > >> >On Mon, Dec 5, 2011 at 2:44 PM, Jordan Zimmerman >> ><jzimmer...@netflix.com>wrote: >> > >> >> I understand the limitations >> >> (being tied to ZK server's release schedule), etc. >> >> >> >>
