Wiki »
Release 1.0 Strategy¶
First step: release 0.18¶
- Spread CL
- CMake-Ă„nderungen?
1.0 Tasks / Issues¶
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
Content Ideas¶
RST¶
- Garbage collection of strange types
- Protobuf 3
- Manual review of all types
- Split into separate projects
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
RSC¶
- Cxx11
- Lock for single stream in logging module
- Garbage collection (e.g. math)
- CMake toolchains removal
- Split CMake utilities into own library
RSB C++¶
RSB Java¶
RSB Python¶
- Python 3 port
- py.test instead of nose
- pep8 pydocsyle etc.
- String/Byte converter conversion to new python data types
- Spread external?
RSB CL¶
- Native spread implementation
- New test framework
- Build system
Loading...