Hi Guozhang, Note that our documentation for the time-based release plan says the following about what happens after the feature freeze:
"We will leave another week for "minor" features to get in (see below for definitions), but at this point we will start efforts to stabilize the release branch and contribute mostly tests and fixes" https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan So, minor KIPs can still be double committed after Wednesday. We should only do that if we are confident that they won't cause stabilisation issues though. Ismael On Thu, Sep 14, 2017 at 7:48 PM, Guozhang Wang <wangg...@gmail.com> wrote: > Hello folks, > > This is a heads up on 1.0.0 progress post the KIP-deadline: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=71764913 > > > In this release we have a total of 33 KIPs either newly adopted or > inherited from the previous release. Among them 15 KIPs has been merged to > trunk, and others are still ongoing / under reviews. > > Please note that the feature freeze deadline is Sept. 20th (next > Wednesday), and after that deadline any accepted KIPs will be pushed to the > next minor release. For those KIP proposer / guiding committer: if you are > confident that the KIP's PRs can be merged to trunk, please make sure to do > so before next Wednesday. > > > Thanks, > -- Guozhang >
