Merge pull request #88 from degrim/Release1.0

Update docs and VERSION for 1.0 release

Author: opiethehokie

CHANGELOG.md

@@ -1,11 +1,16 @@
-## v0.9.0 June 30, 2016
+# Changelog
+
+## v1.0.0 Aug 24, 2016
 
-This version of the buildpack includes the following changes:
+- Add support for running pre and post compile scripts using NPM and Bower to install front-end javascript and css libraries.
+
+## v0.9.0 June 30, 2016
 
 - Add support for the .NET CLI 1.0 Preview 2 build and .NET Core 1.0 RTM
 - The default .NET CLI version to be installed is now 1.0.0-preview2-003121
 
 ## v0.8.0 May 16, 2016
+
 - Switch to .NET CLI from DNX
 - Add support for RC2 apps
 - Remove support for RC1 and lower apps using DNX
@@ -14,12 +19,14 @@ This version of the buildpack includes the following changes:
 - Remove support for lucid64 stack
 
 ## v0.7.0 Sep 30, 2015
+
 - Make NuGet.Config optional, detect only looks for project.json files
 - Support published apps for offline mode and faster staging
 - Remove Mono
 - Switch to .NET Core
 
 ## v0.6.0 Sep 10, 2015
+
 - Add support for beta7 apps
 
 ## v0.5.0 Aug 17, 2015

README.md

@@ -4,8 +4,8 @@ A Cloud Foundry buildpack for .NET Core applications. Tested with [ASP.NET Core
 
 For more information about ASP.NET Core see:
 
-* https://github.com/aspnet/home
-* http://docs.asp.net/en/latest/conceptual-overview/aspnet.html
+* [ASP.NET Github](https://github.com/aspnet/home)
+* [Introduction to ASP.NET Core](http://docs.asp.net/en/latest/conceptual-overview/aspnet.html)
 
 ## Usage
 
@@ -87,7 +87,7 @@ Applications can be pushed with their other dependencies after "publishing" the
 
 For this publish command to work, you will need to make some changes to your application code to ensure that the dotnet cli publishes it as a self-contained application rather than a portable application.
 
-See [Types of portability in .Net Core][] for more information on how to make the required changes to publish your application as a self-contained application.
+See [.NET Core App Types][] for more information on how to make the required changes to publish your application as a self-contained application.
 
 Also note that if you are using a `manifest.yml` file in your application, you can [specify the path][] in your manifest.yml to point to the publish output folder so that you don't have to be in that folder to push the application to Cloud Foundry.
 
@@ -157,5 +157,5 @@ Open an issue on this project.
 [Hello World sample]: https://github.com/IBM-Bluemix/aspnet-core-helloworld
 [ASP.NET Core 1.0 RTM]: https://github.com/aspnet/Home/releases/tag/1.0.0
 [Kestrel]: https://github.com/aspnet/KestrelHttpServer
-[Types of portability in .Net Core]: http://dotnet.github.io/docs/core-concepts/app-types.html
+[.NET Core App Types]: https://docs.microsoft.com/en-us/dotnet/articles/core/app-types
 [specify the path]: http://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#path

VERSION

@@ -1 +1 @@
-0.9.0
+1.0.0