Prep for v0.2 release

Signed-off-by: Magnus <[email protected]>

CHANGELOG

@@ -0,0 +1,58 @@
+--- V 0.2 ---
+
+RVI TOP LEVEL:
+    Updated documentation to reflect changes. Pegged build deps on
+    v0.2 of dependant repos in rebar.config. Removed unsupported
+    option from setup_rvi_node.sh screen
+
+    Added lager start at system startup.
+
+    Added RPM that builds and installs on Tizen and Debian.
+
+    Updated and documented configuration files in hvac_demo and root
+    dir to reflect new funcationality.
+
+    Added web socket support (in service_edge).
+
+    Now builds against v0.2 of all dependencies.
+
+
+SERVICE EDGE:
+    Fixed correct json decoding of parameters
+    Added websocket support
+
+
+SERVICE DISCOVERY:
+    Changed debug to info to get a cleaner log. 
+
+    Scrubbed duplicates from get_network_addresses()
+
+
+SCHEDULE:
+    Now survives a failure to send to a remote node.
+
+    Changed debug to info. 
+
+    Added direct message send if setup_data_link returns that the data link is already up.
+
+RVI COMMON:
+    Renamed error code to not_available
+
+    Added new status code (already_conencted). 
+
+    Added get_component_config with default value as extra arg
+
+    Added result handler for web socket dispatcher in service_edge_rpc.erl
+
+
+DATA LINK
+    Now handles node_address set to 0.0.0.0 to indicate that node is
+    behind firewall and can only do outbound connections
+
+    Now does auto reconnect to static nodes that are not available at boot time
+
+    Ripped out bert_rpc usage. Replaced with homebrewed protocol manager. 
+
+
+
+

TODO

@@ -21,9 +21,6 @@ All repos
    Fix config.
    Prune xxx_lib.erl
 
-Protocol & Data Link components.
-   Check that we use bert as a codec, not any other method
-
 Service Discovery
    Node service prefix matching should return the one with the longest
    prefix match. This allows for default static nodes to be setup with
@@ -39,4 +36,8 @@ Scheduler
    If two different services are invoked on a remote node that is
    currently not available, the services may be invoked out of order
    when the node does become connected. Scheduluer should queue
-   messages on a per-node basis, not per-service. 
+   messages on a per-node basis, not per-service. 
+
+Data Link
+   Any broken connection to a statically configured node should
+   periodically get a reconnect attempt.