Small clarification: "Two KIPs may get in after the release (provided high quality, documented and well-tested PR):"
I meant "after the next release candidate but still get into 0.10.0 release" Gwen On Thu, Apr 28, 2016 at 11:02 AM, Ismael Juma <[email protected]> wrote: > Thanks for the update Gwen. Looking at that list, it seems to me that the > community did very well in a relatively short period of time (and it > doesn't include the large number of bug fixes, test and documentation > improvements). > > Ismael > > On Thu, Apr 28, 2016 at 10:53 AM, Gwen Shapira <[email protected]> wrote: > >> Hi Team Kafka, >> >> Here's a short status update before I am merging trunk into 0.10.0 >> branch and creating a new release candidate, tomorrow morning. >> >> KIPs included in the release: >> KIP-28 Kafka Streams >> KIP-31 Relative offsets in compressed messages >> KIP-32 Add timestamps to messages >> KIP-36 Rack awareness >> KIP-41 KafkaConsumer max records >> KIP-42 Client interceptors >> KIP-45 Standardize client sequences (Note: There is currently a >> blocking asking to modify the APIs again - KAFKA-3633, I am unhappy >> about the last minute changes, but happy to discuss) >> KIP-51 List Connectors REST API >> KIP-4 Admin API (Just the metadata changes) >> KIP-35 Protocol version improvements >> KIP-43 SASL improvements >> KIP-52 Connector Control API >> >> KIPs that unfortunately need to be pushed out: >> KIP-33 Time-based index >> KIP-47 Timestamp-based deletion policy >> KIP-49 Fair Partition Assignment policy >> KIP-50 Improve Authz interface >> >> Two KIPs may get in after the release (provided high quality, >> documented and well-tested PR): >> KIP-57 - fixing an issue with LZ4 compression (since it is a bug fix) >> KIP-56 - Cross Origins HTTP Requests for KafkaConnect (since it is low >> risk) >> >> Tests, bug fixes and documentation changes are welcome any time. >> >> Yours, >> ${RM} >>
