https://kotlinlang.org logo
Join Slack
Powered by
might be a lazyweb question but it seems to have c...
# eap
z
might be a lazyweb question but it seems to have changed recently - is there a (new) way to consume intermediate releases as defined in github tags? Such as this one https://github.com/JetBrains/kotlin/releases/tag/build-1.5.0-RC-507
s
For now -- unfortunately no. We used bintray for our dev builds for very long time, but unfortunately it will be closed soon. So we migrated to our internal infrastructure and trying to figure out what to do next, because we are not ready to support stable infrastructure for repo with dev builds. We still able to share some builds from time to time for example to check that fix helped. Could you please share your use-case? How you used our dev builds? and why Mx and RC builds is not enough?
z
we run shadow jobs against upcoming releases and catch a lot of bugs early that way, and in the past it's be great to be able to close the loop by testing the next eap/rc/etc release tag containing the fix
➕ 3
for example, in this case I want to verify this one https://youtrack.jetbrains.com/issue/KT-44925
s
I see, thanks! Maybe we'll come with some solution like "sharing build every week" or something like that. cc @nk
👍🏼 1
👍 4
r
That would be wonderful. I also miss testing dev builds for the exact same reason (I’m maintaining a compiler plugin). Earlier dev builds would be especially helpful to test the IR backend, because there are a few bugs in the milestone release that stop us from testing further.
n
We have a bootstrap repository that is used internally for building Kotlin repository and updated every 2-3 weeks now https://maven.pkg.jetbrains.space/kotlin/p/kotlin/bootstrap/ Also master is constantly being published into maven snapshots: https://oss.sonatype.org/content/repositories/snapshots/ (it's impossible to browse the link but this the link for kotlin-compiler).
d
2 Views
Open in Slack
PreviousNext
Powered by