[
https://issues.apache.org/jira/browse/KAFKA-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823745#comment-15823745
]
Ismael Juma commented on KAFKA-4421:
------------------------------------
[~ewencp], since [~guozhang] did 0.10.1.1 with Scala 2.12 artifacts, I was
hoping he would update the release process page to include the additional
steps. As you said, it's a bit odd to do it for 0.10.1.1, but not 0.10.2.0.
If the process is not too onerous, I'd just publish Scala 2.12 artifacts for
every future release. We already run PR builds against it, so there is a level
of testing. We can keep the beta label for 0.10.2.0 perhaps since it receives
less testing than the Scala 2.11 artifacts.
I intend to submit a KIP to drop support for Scala 2.10 in the next major Kafka
release as it's 4 years old and I think it's a good policy to support the 2
most recent versions only.
> 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)
