[jira] [Updated] (KAFKA-4422) Drop support for Scala 2.10 (KIP-119)
[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 2956 [https://github.com/apache/kafka/pull/2956] > Drop support for Scala 2.10 (KIP-119) > - > > Key: KAFKA-4422 > URL: https://issues.apache.org/jira/browse/KAFKA-4422 > Project: Kafka > Issue Type: Task >Reporter: Ismael Juma >Assignee: Ismael Juma > Labels: kip > Fix For: 0.11.0.0 > > > Now that Scala 2.12 has been released, we should drop support for Scala 2.10 > in the next major Kafka version so that we keep the number of supported > versions at 2. Since we have to compile and run the tests on each supported > version, there is a non-trivial cost from a development and testing > perspective. > The clients library is in Java and we recommend people use the Java clients > instead of the Scala ones, so dropping support for Scala 2.10 should have a > smaller impact than it would have had in the past. Scala 2.10 was released in > January 2013 and support ended in March 2015. > Once we drop support for Scala 2.10, we can take advantage of APIs and > compiler improvements introduced in Scala 2.11 (introduced in April 2014): > http://scala-lang.org/news/2.11.0 > Link to KIP: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-119%3A+Drop+Support+for+Scala+2.10+in+Kafka+0.11 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4422) Drop support for Scala 2.10 (KIP-119)
[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Summary: Drop support for Scala 2.10 (KIP-119) (was: Drop support for Scala 2.10) > Drop support for Scala 2.10 (KIP-119) > - > > Key: KAFKA-4422 > URL: https://issues.apache.org/jira/browse/KAFKA-4422 > Project: Kafka > Issue Type: Task >Reporter: Ismael Juma >Assignee: Ismael Juma > Labels: kip > Fix For: 0.11.0.0 > > > Now that Scala 2.12 has been released, we should drop support for Scala 2.10 > in the next major Kafka version so that we keep the number of supported > versions at 2. Since we have to compile and run the tests on each supported > version, there is a non-trivial cost from a development and testing > perspective. > The clients library is in Java and we recommend people use the Java clients > instead of the Scala ones, so dropping support for Scala 2.10 should have a > smaller impact than it would have had in the past. Scala 2.10 was released in > January 2013 and support ended in March 2015. > Once we drop support for Scala 2.10, we can take advantage of APIs and > compiler improvements introduced in Scala 2.11 (introduced in April 2014): > http://scala-lang.org/news/2.11.0 > Link to KIP: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-119%3A+Drop+Support+for+Scala+2.10+in+Kafka+0.11 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4422) Drop support for Scala 2.10
[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Status: Patch Available (was: Open) > Drop support for Scala 2.10 > --- > > Key: KAFKA-4422 > URL: https://issues.apache.org/jira/browse/KAFKA-4422 > Project: Kafka > Issue Type: Task >Reporter: Ismael Juma >Assignee: Ismael Juma > Labels: kip > Fix For: 0.11.0.0 > > > Now that Scala 2.12 has been released, we should drop support for Scala 2.10 > in the next major Kafka version so that we keep the number of supported > versions at 2. Since we have to compile and run the tests on each supported > version, there is a non-trivial cost from a development and testing > perspective. > The clients library is in Java and we recommend people use the Java clients > instead of the Scala ones, so dropping support for Scala 2.10 should have a > smaller impact than it would have had in the past. Scala 2.10 was released in > January 2013 and support ended in March 2015. > Once we drop support for Scala 2.10, we can take advantage of APIs and > compiler improvements introduced in Scala 2.11 (introduced in April 2014): > http://scala-lang.org/news/2.11.0 > Link to KIP: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-119%3A+Drop+Support+for+Scala+2.10+in+Kafka+0.11 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4422) Drop support for Scala 2.10
[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Labels: kip (was: ) > Drop support for Scala 2.10 > --- > > Key: KAFKA-4422 > URL: https://issues.apache.org/jira/browse/KAFKA-4422 > Project: Kafka > Issue Type: Task >Reporter: Ismael Juma >Assignee: Ismael Juma > Labels: kip > Fix For: 0.11.0.0 > > > Now that Scala 2.12 has been released, we should drop support for Scala 2.10 > in the next major Kafka version so that we keep the number of supported > versions at 2. Since we have to compile and run the tests on each supported > version, there is a non-trivial cost from a development and testing > perspective. > The clients library is in Java and we recommend people use the Java clients > instead of the Scala ones, so dropping support for Scala 2.10 should have a > smaller impact than it would have had in the past. Scala 2.10 was released in > January 2013 and support ended in March 2015. > Once we drop support for Scala 2.10, we can take advantage of APIs and > compiler improvements introduced in Scala 2.11 (introduced in April 2014): > http://scala-lang.org/news/2.11.0 > Before we do this, we should start a discussion thread followed by a vote in > the mailing list. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4422) Drop support for Scala 2.10
[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Description: Now that Scala 2.12 has been released, we should drop support for Scala 2.10 in the next major Kafka version so that we keep the number of supported versions at 2. Since we have to compile and run the tests on each supported version, there is a non-trivial cost from a development and testing perspective. The clients library is in Java and we recommend people use the Java clients instead of the Scala ones, so dropping support for Scala 2.10 should have a smaller impact than it would have had in the past. Scala 2.10 was released in January 2013 and support ended in March 2015. Once we drop support for Scala 2.10, we can take advantage of APIs and compiler improvements introduced in Scala 2.11 (introduced in April 2014): http://scala-lang.org/news/2.11.0 Link to KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-119%3A+Drop+Support+for+Scala+2.10+in+Kafka+0.11 was: Now that Scala 2.12 has been released, we should drop support for Scala 2.10 in the next major Kafka version so that we keep the number of supported versions at 2. Since we have to compile and run the tests on each supported version, there is a non-trivial cost from a development and testing perspective. The clients library is in Java and we recommend people use the Java clients instead of the Scala ones, so dropping support for Scala 2.10 should have a smaller impact than it would have had in the past. Scala 2.10 was released in January 2013 and support ended in March 2015. Once we drop support for Scala 2.10, we can take advantage of APIs and compiler improvements introduced in Scala 2.11 (introduced in April 2014): http://scala-lang.org/news/2.11.0 Before we do this, we should start a discussion thread followed by a vote in the mailing list. > Drop support for Scala 2.10 > --- > > Key: KAFKA-4422 > URL: https://issues.apache.org/jira/browse/KAFKA-4422 > Project: Kafka > Issue Type: Task >Reporter: Ismael Juma >Assignee: Ismael Juma > Labels: kip > Fix For: 0.11.0.0 > > > Now that Scala 2.12 has been released, we should drop support for Scala 2.10 > in the next major Kafka version so that we keep the number of supported > versions at 2. Since we have to compile and run the tests on each supported > version, there is a non-trivial cost from a development and testing > perspective. > The clients library is in Java and we recommend people use the Java clients > instead of the Scala ones, so dropping support for Scala 2.10 should have a > smaller impact than it would have had in the past. Scala 2.10 was released in > January 2013 and support ended in March 2015. > Once we drop support for Scala 2.10, we can take advantage of APIs and > compiler improvements introduced in Scala 2.11 (introduced in April 2014): > http://scala-lang.org/news/2.11.0 > Link to KIP: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-119%3A+Drop+Support+for+Scala+2.10+in+Kafka+0.11 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4422) Drop support for Scala 2.10
[ https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4422: --- Issue Type: Task (was: Bug) > Drop support for Scala 2.10 > --- > > Key: KAFKA-4422 > URL: https://issues.apache.org/jira/browse/KAFKA-4422 > Project: Kafka > Issue Type: Task >Reporter: Ismael Juma >Assignee: Ismael Juma > Fix For: 0.11.0.0 > > > Now that Scala 2.12 has been released, we should drop support for Scala 2.10 > in the next major Kafka version so that we keep the number of supported > versions at 2. Since we have to compile and run the tests on each supported > version, there is a non-trivial cost from a development and testing > perspective. > The clients library is in Java and we recommend people use the Java clients > instead of the Scala ones, so dropping support for Scala 2.10 should have a > smaller impact than it would have had in the past. Scala 2.10 was released in > January 2013 and support ended in March 2015. > Once we drop support for Scala 2.10, we can take advantage of APIs and > compiler improvements introduced in Scala 2.11 (introduced in April 2014): > http://scala-lang.org/news/2.11.0 > Before we do this, we should start a discussion thread followed by a vote in > the mailing list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
