diff --git a/index.html b/index.html
index 72f376d..e9cf6ee 100644
--- a/index.html
+++ b/index.html
@@ -61,6 +61,7 @@ describe("Jasmine", function() {
Download
diff --git a/release-notes.html b/release-notes.html
new file mode 100644
index 0000000..d25f3a2
--- /dev/null
+++ b/release-notes.html
@@ -0,0 +1,78 @@
+
+
+
+
+
+
+ pivotal/jasmine @ GitHub
+
+
+
+
+
+
+Release Notes
+
+
+
Release 0.11.1 — June 25, 2010
+
Jasmine Core
+
Features
+
+ - Jasmine no longer logs “Jasmine Running…” messages to the log by default. This can be enabled in runner.html by adding ’ trivialReporter.logRunningSpecs = true;’
+ - The ‘wasCalled’, ‘wasCalledWith’, ‘wasNotCalled’ and ‘wasNotCalledWith’ matchers have been deprecated. The new matchers ‘toHaveBeenCalled’ and #‘oHaveBeenCalledWith’ have been added. You can use the ‘not’ method to achieve the ‘wasNot…’ expectation. (e.g. ‘not.toHaveBeenCalled’)
+
+
Notables
+
+ - A barebones version of Jasmine is now available on http://pivotal.github.com/jasmine
+
+
Release 0.11.0 — June 23, 2010
+
Jasmine Core
+
Features
+
+ - The version number has been removed from the generated single-file /lib/jasmine.js. We’re also now uploading this file, with the version number in the filename, to github’s Downloads page.
+ - Old-style matchers (those using this.report(), from before 0.10.x) are no longer supported. See the README for instructions on writing new-style matchers.
+ - jasmine.log pretty-prints its parameters to the spec’s output.
+ - Jasmine no longer depends on ‘window’.
+ - HTML runner should show number of passes/fails by spec, not expectation.
+ - Small modification to JsApiReporter data format
+
+
Bugs fixed:
+
+ - If multiple beforeEach blocks were declared, they were executed in reverse order.
+ - Specs with duplicate names confused TrivialReporter output.
+ - Errors in describe functions caused later tests to be weirdly nested.
+ - Nested specs weren’t reported properly by the JsApiReporter.
+
+
Known issues:
+
+ - If you turn on the mock clock, you’ll get a spurious log message at the end of your spec.
+
+