Release

Assuming that the current development version is 0.3-SNAPSHOT:

0. Start from a clean repository (i.e. run git deep-clean).
1. Remove -SNAPSHOT suffix in version.sbt.
2. Update README.md ("Usage" section and links to scaladoc).
3. ./sbt +test +doc
4. Make sure everything is green under 2.10 and 2.11.
5. Commit changes with bokeh-scala 0.3 commit message.
6. Tag this commit as v0.3 and sign using your PGP key.
7. ./sbt +publishSigned +upload
8. Go to oss.sonatype.org, review changes and finalize release.
9. Increment version number in version.sbt to 0.4-SNAPSHOT.
10. Commit changes with New release cycle commit message.
11. ./sbt +publish (publish new snapshot to make scaladoc link alive).
12. Update bokeh-scala-sample, by using 0.3 in version and libraryDependencies in build.sbt.
13. Add release notes to v0.3 tag on GitHub.
14. Send announcement for the release to bokeh@continuum.io.

Note that step 8. is irreversible. Artifacts published to the central repository can't be removed (for good reasons). If the release is defunct, just fix the problem and create a new release. Let people know in the announcement there's a version that shouldn't be used.

tl;dr:

$ VERSION=$(grep --perl-regexp --only-matching "\d+\.\d+" version.sbt)
$ git deep-clean
$ sed -i s/-SNAPSHOT// version.sbt
$ ./sbt +test +doc || exit
$ git add version.sbt
$ git commit -m "bokeh-scala $VERSION"
$ git tag -s -m "bokeh-scala $VERSION" v$version
$ ./sbt +publishSigned +upload
$ sed 's/\([0-9]\+\.\)\([0-9]\+\)/echo "\1$((\2+1))-SNAPSHOT"/e' version.sbt
$ git add version.sbt
$ git commit -m "New release cycle"
$ git push origin --tags

Useful literature:

1. http://www.scala-sbt.org/0.13/docs/Using-Sonatype.html
2. http://central.sonatype.org/pages/releasing-the-deployment.html