Update master branch for release

[etsardou]

• Merge C++ work
• Merge JS work (if needed)
• Update README.md file with the implementations
• @klpanagi Add important links in README.md such as:
• https://github.com/rapp-project/rapp-api/blob/master/python/README.md
• https://github.com/rapp-project/rapp-api/blob/master/python/RappCloud/README.md
• https://github.com/rapp-project/rapp-api/blob/master/python/RappCloud/CloudMsgs/README.md

[alexge233]

@etsardou @dudekw I have rejected the pull request; there are major conflicts, and also some classes must be refactored by WUT.

[klpanagi]

Proper README.md links exist on branch devel.

[alexge233]

@etsardou and @klpanagi I've updated master with cpp branch, and merged cpp_dev on devel.
However, I personally think that master should have the cpp_dev / devel code since it has been extensively tested with unit tests and stress tests. Let me know if you want me to proceed with that.

[klpanagi]

@alexge233, I really cannot read the git tree anymore...

You have made a direct merge to master (even a direct commit to master) and the tree has been broken. Even devel branch holds a direct commit!

devel branch holds both js and python development work and should be the one to merge into master.

If i understand correctly, devel CANNOT be merged to master because of conflicts in cpp implementations...

[alexge233]

Hi,

1. Direct commit was a direct edit of README from github and removing some files which I didn't add (package.xml and CMakeLists.txt). The merge was from cpp which has been our long stable version (0.6.1)
2. The devel branch has had cpp_dev merged because I'm removing it tomorrow (it was our own devel branch)
3. Only file in conflict was README.md
4. Any conflict in cpp implementation is solved by accepting devel (from cpp_dev) and ignoring master (if we are to move to 0.7.0)