-
Notifications
You must be signed in to change notification settings - Fork 406
Release 1.15.0 #668
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
I agree we should release 1.15.0. I've worked on applying the 1.15.0 label to open issues, so we can track progress and the remaining effort: |
How critical are the remaining issues in the 1.15.0 milestone? Could some of them be moved to a future milestone to release 1.15.0 faster ? |
Would be much appreciated. Happy to volunteer the time to upgrade the Typelevel ecosystem. |
@ashawley are you around and interested in helping push this forward? (fsvo "helping") |
I should have free time soon to contribute to getting a release out here. Sorry for the delay. |
note that one possibility would be to just close our eyes, roll whatever we have and call it 1.15.0-M1 (or 1.15.0-RC1), and then work towards 1.15.0 final after thought prompted because I just hit "ambiguous implicit error due to BooleanOperators" myself today over at scala/scala-parallel-collections#113, so now I know what y'all are talking about there :-) |
@SethTisue i'll do that this weekend |
@SethTisue So, the Dotty build is blocking the release. Specifically, it appears it didn't build javadoc jars, which Sonatype checks for when validating the release. Here the publish output from Dotty:
And here's Scala 2.12 (JVM):
As you can see Dotty only published 6 files while 2.12 published 8. I don't know a lot about how Dotty publishes. Is this expected? Is there some other SBT command I need to run for Dotty? EDIT: I ran |
This comes from your sbt build: Lines 170 to 174 in b296397
The usual workaround to keep sonatype happy is to still publish a doc jar but leave it empty, this is accomplished by having in your sbt build: sources in (Compile, doc) := Seq() except here you only want to do it for dotty so you probably want: sources in (Compile, doc) := {
if (isDotty.value) then Seq() else (sources in (Compile, doc)).value
} |
@smarter Thanks! |
You could also turn off the dotty build for now: the scalacheck build is at version 0.24.0-RC1 so it's way too old to be useful currently anyway. You could try bumping it to |
@smarter I'll try with what I have since it's currently on and already running. If this build fails, I'll turn it off for now and we can revisit. |
OK yeah the SBT snippet didn't totally work so I released without Dotty. We can try to fix this before the real 1.15.0 release. |
Anyway, just released 1.15.0-M1. |
I released a 0.27 artifact based on #684, which isn't yet merged, but since we're talking about a milestone release, I don't think that's problematic. |
thanks Erik, thanks Lars! the 0.27 artifact is working great for me over in scala-parallel-collections 👍 |
Do you all feel like we should go ahead and release 1.15.0? I'm also up for doing an M2 if folks would rather be cautious. |
(no opinion) |
There's a few open PRs tagged with 1.15.0. I suggest to go through with them and then follow up with RC1. |
@larsrh Sounds good. I'm fine with merging both as-is or making changes. Would appreciate at least one more set of eyes. |
Are we ready for RC1? @SethTisue, @non? |
RC1 is out, final will follow next week if no issues are found. |
okay if we keep this open until actual 1.15.0 is out? |
I took the liberty of filling in the gaps in the changelog. |
Release planSince Scalacheck doesn't use macros, many library authors that depend on Scalacheck used |
Added to release notes:
|
@larsrh may I suggest that Typelevel tweet about this? possible tweet text:
|
if you omit yourself out of modesty I will be VERY ANGRY |
I did not, but I did include you 😉 |
In #667, @smarter said:
The text was updated successfully, but these errors were encountered: