leap_platform.git/doc, branch 0.5.2 [leap_platform] update documentation of the platform. Todo: known-issues 2013-11-03T23:56:17+00:00 kwadronaut kwadronaut@leap.se 2013-11-03T23:56:17+00:00 6a4e2efe9c57dea50119506b3c86b8277c5b5bd0 






Copy the current state of the platform documentation into the doc directory.
2013-07-03T20:54:10+00:00

Micah Anderson
micah@riseup.net

2013-07-03T15:45:03+00:00

76824412771cdeaf4b62fcd711e2f722bd32e08f

Originally I thought it would be better to add the leap_doc git repository as a
submodule, but I decided against that:

 . it requires that the user has to start off by initializing submodules,
 something that the leap_cli does for you

 . it would result in more up-to-date documentation than was targeted for this
 release

 . it would result in an unfortunate directory structure (doc/doc/platform).

For these reasons it seemed to me better to put a snapshot of our current
platform documentation into the doc directory right before release. This just
means a step in our release process of refreshing these docs once we have
reviewed them and updated the known-issues for this release.

Change-Id: Ib395ea30553772fd195dd50315f026a2576feedd





Originally I thought it would be better to add the leap_doc git repository as a
submodule, but I decided against that:

 . it requires that the user has to start off by initializing submodules,
 something that the leap_cli does for you

 . it would result in more up-to-date documentation than was targeted for this
 release

 . it would result in an unfortunate directory structure (doc/doc/platform).

For these reasons it seemed to me better to put a snapshot of our current
platform documentation into the doc directory right before release. This just
means a step in our release process of refreshing these docs once we have
reviewed them and updated the known-issues for this release.

Change-Id: Ib395ea30553772fd195dd50315f026a2576feedd