Good news everybody!
Yes indeed, that would be the final! The bytecode is the same as RC5. The only change is the metadata.
As the holidays are extremely nigh, we have decided to wait a little bit longer than usual to announce the release: we'll make it official by the end of the first week of the new year.
We still wanted to stage according to the two-week cycle (and before the end of the world). This ought to give you a little more time to build your projects, and it will allow us to provide better support to our users once we are back in full force from our xmas break.
In the mean time, if you'd like to have your support for 2.10.0 included with the release announcement, please do the following:
(1) Build your software against 2.10.0 with 2.10.0 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" % "1.2"
---
Thank you for your help and patience during this whole release cycle!
We're working on learning from the 2.10.0 cycle to improve the process for the 2.10.1 release (RC1 scheduled for mid-Feb) and the 2.11 cycle. (Have a look at the
roadmap if you're curious.) Your thoughts on this are welcome, as always, on this mailing list!
happy holidays!
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. This is what Josh does because he's lazy:
scalaVersion := "2.10.0"
scalaBinaryVersion <<= scalaVersion.identity