Update readme, changelog in preparation for 0.1.0

Author: psalz

CHANGELOG.md

@@ -0,0 +1,14 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
+and this project adheres to [Semantic
+Versioning](http://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2019-09-05
+
+__Hello, World!__ This is our first release!
+

README.md

@@ -1,4 +1,6 @@
-# Celerity Runtime
+![Celerity Logo](docs/celerity_logo.png)
+
+# Celerity Runtime - [![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/celerity/celerity-runtime/blob/master/LICENSE) [![Semver 2.0](https://img.shields.io/badge/semver-2.0.0-blue)](https://semver.org/spec/v2.0.0.html) [![PRs # Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/celerity/celerity-runtime/blob/master/CONTRIBUTING.md)
 
 The Celerity distributed runtime and API aims to bring the power and ease of
 use of SYCL to distributed memory clusters.
@@ -11,28 +13,18 @@ projects in the future.
 
 ## Dependencies
 
-* [Boost](http://www.boost.org) (tested with version 1.65 - 1.68)
 * A supported SYCL implementation, either
 	- [hipSYCL](https://github.com/illuhad/hipsycl), or
 	- [ComputeCpp](https://www.codeplay.com/products/computesuite/computecpp)
+* [Boost](http://www.boost.org) (tested with version 1.65 - 1.68)
 * A MPI 2 implementation (tested with OpenMPI 4.0 and MSMPI 10.0)
 * [CMake](https://www.cmake.org)
-* A C++14 compiler (tested with MSVC 14, gcc 7 and Clang 8)
-
-### Automatically Downloaded Dependencies
-
-These dependencies are downloaded automatically during the CMake build process,
-for convenience:
-
-* [Catch2](https://github.com/catchorg/Catch2) for testing
-* The [spdlog](https://github.com/gabime/spdlog) logging library
+* A C++14 compiler
 
 ## Building
 
-Building is as simple as calling `cmake && make`, depending on your setup you
-might however also have to provide some library paths etc.
-
-## Building Examples
+Building can be as simple as calling `cmake && make`, depending on your setup
+you might however also have to provide some library paths etc.
 
 The runtime comes with several examples that are built automatically when
 the `CELERITY_BUILD_EXAMPLES` CMake option is set (true by default).
@@ -44,9 +36,13 @@ relevant header files and libraries to the `CMAKE_INSTALL_PREFIX`. This includes
 a CMake [package configuration
 file](https://cmake.org/cmake/help/latest/manual/cmake-packages.7.html#package-configuration-file)
 which is placed inside the `lib/cmake` directory. Once included in a CMake
-project, you can use the
-`add_celerity_to_target(TARGET target SOURCES source1 source2...)` function to
-set everything up.
+project, you can use the `add_celerity_to_target(TARGET target SOURCES source1
+source2...)` function to set everything up.
+
+## Running a Celerity Application
+
+Celerity is built on top of MPI, which means a Celerity application can be
+executed like any other MPI application (i.e., using `mpirun` or equivalent).
 
 ## Environment Variables
 
@@ -58,4 +54,5 @@ set everything up.
 * `CELERITY_PROFILE_OCL` controls whether OpenCL-level profiling information
   should be used or not (currently not supported when using hipSYCL).
 * `CELERITY_LOG_LEVEL` controls the logging output level. One of `trace`, `debug`,
-  `info`, `warn`, `err`, `critical`, or `off`.
+  `info`, `warn`, `err`, `critical`, or `off`.
+