Release version 0.6.1

erlanglab · Apr 13, 2017 · bfd015e · bfd015e
1 parent 8c7f242
commit bfd015e
Show file tree

Hide file tree

Showing 5 changed files with 8 additions and 8 deletions.
diff --git a/README.md b/README.md
@@ -9,7 +9,7 @@ The Erlang Performance Lab tool (erlangpl for short) can be started using escrip
 ### Download prebuilt script
 
 The easiest way to get started is to download a prebuilt `erlangpl` script
-([download link](https://github.com/erlanglab/erlangpl/releases/download/0.6.0/erlangpl.tar.gz)).
+([download link](https://github.com/erlanglab/erlangpl/releases/download/0.6.1/erlangpl.tar.gz)).
 
 ### Build it manually
 
@@ -97,7 +97,7 @@ Videos from those experiments were posted on [YouTube](https://www.youtube.com/c
 
 ## Developing
 
-### Erlang 
+### Erlang
 #### Running development release
 
 You can also start the tool as a regular Erlang release and connect to its console to debug the tool itself.
@@ -119,12 +119,12 @@ We are recomending [yarn](https://yarnpkg.com/lang/en/) for that.
 yarn && yarn start
 ```
 
-Now, application can be found at `localhost:3000` and will be listening for messages from `localhost:37575` where you have to have [erlangpl](https://github.com/erlanglab/erlangpl) running. 
+Now, application can be found at `localhost:3000` and will be listening for messages from `localhost:37575` where you have to have [erlangpl](https://github.com/erlanglab/erlangpl) running.
 
 #### Writing Elm code
 
 Although `erlangpl-ui` is written in React we belive in Elm power. Because of that we support Elm in out build process.
-This is possible because of [react-elm-components](https://github.com/evancz/react-elm-components) and [elm-webpack](https://github.com/elm-community/elm-webpack-loader). 
+This is possible because of [react-elm-components](https://github.com/evancz/react-elm-components) and [elm-webpack](https://github.com/elm-community/elm-webpack-loader).
 
 You can write any separate component in Elm and then wrap it into React component which can be integrated with whole application. Elm code should be placed in `ui/src/elm` and every component whould have main file in this directory and all files related to this component in directory with the same name. React wrapper file should have the same name as Elm component and `flow` should be disabled for this file.
 

diff --git a/apps/epl/src/epl.app.src b/apps/epl/src/epl.app.src
@@ -1,7 +1,7 @@
 {application, epl,
  [
   {description, "Erlang Performance Lab"},
-  {vsn, "0.6.0"},
+  {vsn, "0.6.1"},
   {registered, []},
   {applications, [
                   kernel,

diff --git a/elm-package.json b/elm-package.json
@@ -1,5 +1,5 @@
 {
-    "version": "1.0.0",
+    "version": "0.6.1",
     "summary": "helpful summary of your project, less than 80 characters",
     "repository": "https://github.com/user/project.git",
     "license": "BSD3",

diff --git a/package.json b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "erlangpl",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "private": true,
   "devDependencies": {
     "autoprefixer": "6.7.2",

diff --git a/rel/reltool.config b/rel/reltool.config
@@ -4,7 +4,7 @@
        {lib_dirs, ["../apps", "../deps"]},
        {erts, [{mod_cond, derived}, {app_file, strip}]},
        {app_file, strip},
-       {rel, "erlangpl", "0.6.0",
+       {rel, "erlangpl", "0.6.1",
         [
          kernel,
          stdlib,