From 7ebba1c54e3cdbe216eb9c81a12229b8f9d4779f Mon Sep 17 00:00:00 2001
From: Eugene Yokota <eed3si9n@gmail.com>
Date: Sun, 21 Feb 2016 18:50:17 -0500
Subject: [PATCH] sbt 0.13.11 is the new 0.13.10

---
 build.sbt                                    | 2 +-
 notes/{0.13.10.markdown => 0.13.11.markdown} | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)
 rename notes/{0.13.10.markdown => 0.13.11.markdown} (98%)

diff --git a/build.sbt b/build.sbt
index c1682d13e..448656eb2 100644
--- a/build.sbt
+++ b/build.sbt
@@ -7,7 +7,7 @@ import Sxr.sxr
 // but can be shared across the multi projects.
 def buildLevelSettings: Seq[Setting[_]] = inThisBuild(Seq(
   organization := "org.scala-sbt",
-  version := "0.13.10-SNAPSHOT",
+  version := "0.13.11-SNAPSHOT",
   bintrayOrganization := Some(if (publishStatus.value == "releases") "typesafe" else "sbt"),
   bintrayRepository := s"ivy-${publishStatus.value}",
   bintrayPackage := "sbt",
diff --git a/notes/0.13.10.markdown b/notes/0.13.11.markdown
similarity index 98%
rename from notes/0.13.10.markdown
rename to notes/0.13.11.markdown
index 5f6c34fd8..0d8d2debd 100644
--- a/notes/0.13.10.markdown
+++ b/notes/0.13.11.markdown
@@ -155,13 +155,13 @@
 
 ### Configurable Scala compiler bridge
 
-sbt 0.13.10 adds `scalaCompilerBridgeSource` setting to specify the compiler brigde source. This allows different implementation of the bridge for Scala versions, and also allows future versions of Scala compiler implementation to diverge. The source module will be retrieved using library management configured by `bootIvyConfiguration` task.
+sbt 0.13.11 adds `scalaCompilerBridgeSource` setting to specify the compiler brigde source. This allows different implementation of the bridge for Scala versions, and also allows future versions of Scala compiler implementation to diverge. The source module will be retrieved using library management configured by `bootIvyConfiguration` task.
 
 [#2106][2106]/[#2197][2197]/[#2336][2336] by [@Duhemm][@Duhemm]
 
 ### Dotty awareness
 
-sbt 0.13.10 will assume that Dotty is used when `scalaVersion` starts with `0.`.
+sbt 0.13.11 will assume that Dotty is used when `scalaVersion` starts with `0.`.
 The built-in compiler bridge in sbt does not support Dotty,
 but a separate compiler bridge is being developed at [smarter/dotty-bridge](https://github.com/smarter/dotty-bridge) and
 an example project that uses it is available at [smarter/dotty-example-project](https://github.com/smarter/dotty-example-project).
@@ -170,7 +170,7 @@ an example project that uses it is available at [smarter/dotty-example-project](
 
 ### Inter-project dependency tracking
 
-sbt 0.13.10 adds `trackInternalDependencies` and `exportToInternal` settings. These can be used to control whether to trigger compilation of a dependent subprojects when you call `compile`. Both keys will take one of three values: `TrackLevel.NoTracking`, `TrackLevel.TrackIfMissing`, and `TrackLevel.TrackAlways`. By default they are both set to `TrackLevel.TrackAlways`.
+sbt 0.13.11 adds `trackInternalDependencies` and `exportToInternal` settings. These can be used to control whether to trigger compilation of a dependent subprojects when you call `compile`. Both keys will take one of three values: `TrackLevel.NoTracking`, `TrackLevel.TrackIfMissing`, and `TrackLevel.TrackAlways`. By default they are both set to `TrackLevel.TrackAlways`.
 
 When `trackInternalDependencies` is set to `TrackLevel.TrackIfMissing`, sbt will no longer try to compile internal (inter-project) dependencies automatically, unless there are no `*.class` files (or JAR file when `exportJars` is `true`) in the output directory. When the setting is set to `TrackLevel.NoTracking`, the compilation of internal dependencies will be skipped. Note that the classpath will still be appended, and dependency graph will still show them as dependencies. The motivation is to save the I/O overhead of checking for the changes on a build with many subprojects during development. Here's how to set all subprojects to `TrackIfMissing`.