[jira] [Commented] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

["Ewen Cheslack-Postava (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823513#comment-15823513 ] 

Ewen Cheslack-Postava commented on KAFKA-4421:
----------------------------------------------

[~ijuma] A) should this be set up for the next release given that we produced beta 2.12 artifacts for the previous minor release and B) when do we actually want to commit to this? Seems like we shouldn't commit to anything permanent until we commit to Java 8+ permanently, but I think folks want to see support for this earlier. How do we want to handle Scala 2.12 until we remove java 7 support?

> Update release process so that Scala 2.12 artifacts are published
> -----------------------------------------------------------------
>
>                 Key: KAFKA-4421
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4421
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Ismael Juma
>             Fix For: 0.10.2.0
>
>
> Since Scala 2.12 requires Java 8 while Kafka still supports Java 7, the *All commands don't include Scala 2.12. As such, simply running releaseTarGzAll won't generate the Scala 2.12 artifacts and we also need to run `./gradlew releaseTagGz -PscalaVersion=2.12`.
> The following page needs to be updated to include this and any other change required:
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Process



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)