Re: Review of public APIs

2011-10-24 Thread Ivan Kelly
> For BOOKKEEPER-90, I still need to decide what to do about ByteString if we > do anything at all. Having ByteString in the API tries us to google > protobufs. Im not sure this is a huge issue, but it means that this API will > never be able to move away from it. Another open issue is that Hed

Re: Review of public APIs

2011-10-24 Thread Ivan Kelly
Yes, I agree on the 4.0 release thing. It will make it clear that there's been a big change. I've created two JIRAs for the changes, BOOKKEEPER-89 for bookkeeper, BOOKKEEPER-90 for hedwig. Please have a look [1][2]. BOOKKEEPER-89 is complete. For BOOKKEEPER-90, I still need to decide what to d

Re: Review of public APIs

2011-10-19 Thread Utkarsh Srivastava
I think it makes sense to delay the release if required for this cleanup. Such cleanup will get only harder after the release. On Wed, Oct 19, 2011 at 9:42 AM, Flavio Junqueira wrote: > Hi Ivan, Thanks for putting this list together. I don't have a good sense of > how many changes the modificatio

Re: Review of public APIs

2011-10-19 Thread Flavio Junqueira
Hi Ivan, Thanks for putting this list together. I don't have a good sense of how many changes the modifications you're proposing would induce. My concern is delaying the release further, even though I agree that cleaning up the interfaces is important. Also, I was thinking that some public