@hachikuji Usually I would try to find a sustainable long term solution for a problem, which in this case is what is the criteria for decision the feature to be included in a given release. Currently for each feature release we tell developer that major feature needs to be merged before feature freeze date. I would take intelligent risk if the feature is related to availability of Kafka.
For other things like this non-so-critical feature which has waited almost two years since its first proposal, I am inclined to enforce the rule and not include the feature after feature freeze date. The concern is that if we break the rule because we subjectively think the PR is low-risk, it will be harder to enforce the rule in a fair and objective manner. Developers of other major KIPs (e.g. KIP-368) will similarly ask to include their PRs after deadline. Then future release manager has to either reject these which would seem unfair, or always include these which would increase the risk and potentially delay the time of release. It is probably more sustainable to reduce the subjective judgement involved in deciding whether a PR is safe. So I think we can include this feature if we can agree on and modify the release plan template in such a way that is clear and easy to enforce in an objective manner. Maybe @ijuma can also comment on this. What do you think? [ Full content available at: https://github.com/apache/kafka/pull/2267 ] This message was relayed via gitbox.apache.org for [email protected]
