Good news everybody!
Yes, that's an F-I-V-E. I messed up with that slightly lower number that shall not be named/released.
Here's the changelog since RC3:
e791a92667 Fixing OSGi distribution.
eccdc2fefc SI-6754 Fix for rangepos crasher.
e6441f16e8 SI-6685 fixes error handling in typedApply
We will announce RC5's availability on Monday Dec 10th.
If you'd like to have your support for 2.10.0-RC5 included with the release announcement, please do the following before it's Monday Dec 10th in San Francisco:
(1) Build your software against 2.10.0-RC5 with 2.10.0-RC5 dependencies.
(2) Publish your software somewhere convenient like maven-central or other publicly accessible repository.
(3) Respond to this email with (only) the following. Please keep this thread clean, so I can easily parse the entries:
(a) Name of your project
(b) Brief (one sentence) description of the project
(c) URL for the project website
(d) Instructions for obtaining the project.
Here's an example for the scala-arm project:
---
Name: Scala-arm
Description: Scala-arm provides automated resource management to ensure all your resources are closed without all the extra work!
Location: "com.jsuereth" % "scala-arm_2.10.0-RC5" % "1.2"
---
Thank you for your help!
adriaan
PS:
Concerning (1), here's how to build using SBT 0.12.1:
(1) Create a ~/.sbt/repositories file that looks like this:
[repositories]
local
maven-central
(2) Make sure you have the sonatype release resolver for both Scala + other staged artifacts that haven't hit maven central
(3) Make sure you've set your cross-building appropriately for RC. This is what Josh does because he's lazy:
scalaVersion := "2.10.0-RC5"
scalaBinaryVersion <<= scalaVersion.identity