Hey Michael, Awesome. I have a minor request. The APIs are currently documented as a wiki list. Would you mind adding a code snippet instead? It's a bit easier to process.
How will be best to manage this, as we will obviously build off your KIP’s > protocol changes, to avoid a merge hell, should we branch from your branch > in the confluent repo or is it worth having a KIP-98 special branch in the > apache git, that we can branch/fork from? I was thinking about this also. Ideally we'd like to get the changes in as close together as possible since we only want one magic bump and some users deploy trunk. The level of effort to change the format for headers seems not too high. Do you agree? My guess is that the KIP-98 message format patch will take 2-3 weeks to review before we merge to trunk, so you could hold off implementing until that patch has somewhat stabilized. That would save some potential rebase pain. -Jason
