-
Notifications
You must be signed in to change notification settings - Fork 92
Support Scala.js 1.0 #408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks, Seth. There are two items here. Releasing |
Scratch that: I forgot that we can't release from the 1.x branch because of sbt 0.13. |
fwiw, I find the idea of a 2.0.0 release a lot more appealing than doing further 1.x releases. I'm not opposed to any further 1.x releases, I just feel that if we have x amount of maintainer energy to spend, let's spend it on forward motion (and if anyone appears who really wants/needs further 1.x changes, we could consider inviting them on board as a maintainer so they can do that themselves) just throwing an opinion out there. yours trumps mine |
I agree. In fact, the few Scala.js 1.0 milestone users are already using 2.0.0-M1, so it's of no use. |
to argue the other side for a moment though, one line of reasoning for doing further 1.x releases could be the transitive-dependency situation, e.g. the dependency of scalatest on scala-xml? I haven't really thought this through, but does ScalaTest 3.1 depend on scala-xml 1.x? so if we don't release for Scala.js 1.0, then ScalaTest can't either? that kind of thing? |
I've created #410, but also pushed a tag for 2.0.0-M1 https://github.com/scala/scala-xml/releases/tag/v2.0.0-M1%23sjs_1.0.0 They should be up on Sonatype in a few minutes: https://travis-ci.org/scala/scala-xml/jobs/646614052 |
Strange errors:
|
Must be Sonatype is getting slammed. We can hit restart on those jobs when things quiet down. |
Yeah, I believe it is on 1.2.0. https://github.com/scalatest/scalatest/blob/9d8061c359/project/scalatest.scala#L225 So far, we haven't released any 1.0.0-RCx releases, so I'm not sure how they're fairing. Although, ScalaTest is usually delayed in finding out these questions. |
no staging repos at https://oss.sonatype.org/#stagingRepositories . yeah, I guess just try again later UPDATE: oh, there were staging repos (the website was just being super slow), but they were empty. I dropped them. |
Thanks for dropping them. I've his restart on two jobs. It seems they got further along:
|
staging repos released |
Scala Steward made an initial stab at #407, but it was closed because additional work is needed
The text was updated successfully, but these errors were encountered: