Yeah I can take a look at those.
The plan for branching is to do all development off trunk and cut
branches for releases. 0.8 was sort of a one-off in this respect.
Going forward the idea is that all new code will go against trunk.
Topic delete would also be a great one.
I would recommend we hold off on splitting the jars. I think post
0.8.1 (0.9?) would be a better target. The reason is that we have a
bunch of major surgery to do there--move to nio, fix approach to
request definition, redo producer and consumer api, etc--and I think
it will be a lot easier to do all the surgery at once.
On Tue, Jun 25, 2013 at 7:53 AM, Sam Meder <[EMAIL PROTECTED]> wrote:
> On Jun 24, 2013, at 9:41 AM, Jay Kreps <[EMAIL PROTECTED]> wrote:
>> Hey Sam,
>> That's great. I would be happy to act as a point of contact if any
>> questions come up or you need a reviewer for patches.
> Great, I have a few patches outstanding, so if you could take a look:
>> We haven't had an official discussion of roadmap but trunk already has
>> support for keyed messages and log compaction and a cleanup of the log
>> code. I think the goal would be to make this release as small and
>> quick as possible with any bigger disruptive features going into 0.9.
> So the plan is to base 0.8.1 on trunk?
>> Here are some ideas of things that I think would fit well:
>> 1. Any good housekeeping issues. 0.8 was a pretty major rewrite and
>> getting that done and stable required ignoring a lot of basic issues
>> that impact the out-of-the-box experience---good errors,
>> documentation, logging, etc. We haven't filed a lot of JIRAs for this,
>> but anything you see that falls under this umbrella would be a good
>> target. Doing a few of these is often a good way to learn the code
> Mostly what I have been trying to do - some classes could probably also use some splitting up. I'll continue down this path.
>> 2. Quotas. Jonathan had proposed working on this, but I don't think he
>> ever got the time. https://issues.apache.org/jira/browse/KAFKA-656
>> 3. Phase 2 of this wiki:
> For us 3 seems definitely more valuable than 2. We'd also really like to have support for deleting topics (i.e. continue work on https://issues.apache.org/jira/browse/KAFKA-330) and would potentially want to change the build so it creates separate server and client artifacts.
>> Folks--any other ideas?
>> On Sun, Jun 23, 2013 at 11:01 PM, Sam Meder <[EMAIL PROTECTED]> wrote:
>>> I now have roughly a day a week I can dedicate to working on Kafka, so I am looking for issues in the 0.8.1 batch that you think might be good starting points. Input would be much appreciated.
>>> Speaking of issues, I think it would be good to either fix https://issues.apache.org/jira/browse/KAFKA-946 for 0.8 or just drop the code from the release.