Robotics Service Bus

h1. Release 1.0 Strategy

{{>toc}} {>toc}

h2. First step: release 0.18

* Spread CL
* CMake-Änderungen?

h2. 1.0 Tasks / Issues

h3. Github Migration

* Own organization for rsb
* One project per language binding
* Things to migrate
** language bindings: C++, Java, Python, CL
** Protocol (description)
** Documentation / Manual
** C++ / CL tools
** RSBag
* Own organization for RST
** One project with definitions
** One project per language binding
* RSC in RSB organization
* Selectively migrate issues relevant for 1.0
* Select a CI service
** Should support triggering downstream projects, if possible
* Host documentation on github pages or readthedocs
* semver
* Remove automatic patch version counting

h3. Content Ideas

h4. RST

* Garbage collection of strange types
* Protobuf 3
** Manual review of all types
* Split into separate projects

h4. RSB Features

* Protocol without protobuf support to avoid runtime dependency etc
* Converter selection: clients always indicate which language types they need / produce
* Named participants such that converter selection can be configured
* Introspection protocol:
** batching
** metrics export (latency, events per connector, etc.)
* protocol buffers converter as own library or optional dependency depending on language features / conventions
* Socket transport:
** Subscription notification
** Queues