+1. This is a good idea as we have a lot of KIPs in flight. On Tue, Dec 13, 2016 at 3:53 AM Ismael Juma <ism...@juma.me.uk> wrote:
> Hi all, > > A while back Grant proposed moving inactive/dormant KIPs to a separate > table in the wiki. I think this is a good idea as it will make it easier > for people to see the KIPs that are actually active. The list that Grant > proposed then was: > > - KIP-6 - New reassignment partition logic for rebalancing (dormant) > > - KIP-14 - Tools standardization (dormant) > > - KIP-17 - Add HighwaterMarkOffset to OffsetFetchResponse (dormant) > > - KIP-18 - JBOD Support (dormant) > > - KIP-23 - Add JSON/CSV output and looping options to > ConsumerGroupCommand > > (dormant) > > - KIP-27 - Conditional Publish (dormant) > > - KIP-30 - Allow for brokers to have plug-able consensus and meta data > storage > > sub systems (dormant) > > - KIP-39: Pinning controller to broker (dormant) > > - KIP-44 - Allow Kafka to have a customized security protocol (dormant) > > - KIP-46 - Self Healing (dormant) > > - KIP-47 - Add timestamp-based log deletion policy (blocked - by KIP-33) > > - KIP-53 - Add custom policies for reconnect attempts to NetworkdClient > > - KIP-58 - Make Log Compaction Point Configurable (blocked - by KIP-33) > > - KIP-61: Add a log retention parameter for maximum disk space usage > > percentage (dormant) > > - KIP-68 Add a consumed log retention before log retention (dormant) > > > KIP-58 was adopted since then and it probably makes sense to add KIP-10 to > the list. > > Are people OK with this? Feel free to suggest KIPs that should or should > not be in the inactive/dormant list. > > Ismael > -- Thanks, Neha
