Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: kafka-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of junrao@gmail.com designates
 209.85.160.47 as permitted sender)
MIME-Version: 1.0
Date: Fri, 1 Jun 2012 21:16:45 -0700
Message-ID: 
 <CAFbh0Q1bBb4uaheiiYRGjK7+nWhhQc1rjJwCv+fw8t+CzFv2=g@mail.gmail.com>
Subject: kafka replication status
From: Jun Rao <junrao@gmail.com>
To: kafka-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b15a8c39fba2504c17591cb

--047d7b15a8c39fba2504c17591cb
Content-Type: text/plain; charset=ISO-8859-1

Hi,

As of this week, we closed 2 big jiras: kafka-46 (commit thread) and
kafka-348 (merge from trunk). Basic replication (without failure) is
working now.

We have people signed up on the following jiras:

KAFKA-336: Admin RPC between controller and broker
KAFKA-335: Embedded controller
KAFKA-329: Create topic support (revisit based on v3 design)

Those jiras are blocking a bunch of other jiras and we'd like to close them
in a week or so.

In the meantime, the following jiras can still be worked on more or
less independently and we welcome  contribution from the community.
KAFKA-288: rework java producer API
KAFKA-289: reuse TopicData when sending produce request
KAFKA-354: refactor setter/getter in scala style
KAFKA-356: create a generic thread class

Thanks,

Jun

--047d7b15a8c39fba2504c17591cb--