This sounds like a good idea. KIPs seem to work well for Kafka. It's easy
for discussions to get lost or just not seen on the mailing list.

2017-06-09 21:36 GMT+02:00 Harsha <[email protected]>:

> Hi All,
>           We’ve seen good adoption of KIP approach in Kafka community
>           and would like to see we adopt the similar approach for storm
>           as well.
> Its hard to keep track of proposed changes and mailing list threads to
> know what all changes that are coming into  and what design/backward
> incompatible changes being approved.  It will be good to have this
> documented and go through discussion then Vote phase to get them
> approved before we merge the PRs. This will keep everyone informed of
> what changes happened even if they are not following the mailing list
> they can go to wiki to see the list of changes went into a release.
> Community overall will be well informed of the changes as well. Would
> like to hear your thoughts.
>
> Thanks,
> Harsha
>

Reply via email to