Good question. Some fixes are clearly critical (e.g., consumer deadlocks) that would impact everyone and need to go into 0.8. Unfortunately the criticality of most other fixes is subjective and I'm not sure how feasible it is to develop a global criteria. It probably needs to be determined through consensus whether it needs to go into 0.8 or not. How about for now: by default we will not incorporate fixes into 0.8 unless there is a compelling argument (e.g., regression/clear bug with no good workaround) to do so.
Joel On Tue, Jul 2, 2013 at 5:11 PM, Jay Kreps <[EMAIL PROTECTED]> wrote:
My vote is that a patch can go into 0.8 if (1) it fixes a critical issue or (2) the change is trivial and it makes the 0.8 experience better (e.g., improving log4j readability). kafka-946 may fall into (2).
Jun On Tue, Jul 2, 2013 at 7:34 PM, Joe Stein <[EMAIL PROTECTED]> wrote:
+1 on Jun's defn. On Tue, Jul 2, 2013 at 10:21 PM, Jun Rao <[EMAIL PROTECTED]> wrote:
Jay Kreps 2013-07-03, 15:57
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext