On the Road to 1.0

[elBoberido]

Brief feature description

This is a tracking issue for our 1.0 release.

Detailed information

Required features/strategies for our 1.0 release.

• N:M communication Support for n:m communciation (multiple senders on a topic / CaProID) #25
• new Publisher/Subscriber API Improvements to Publisher/Subscriber API #218

Postponed to 2.0

• ...

[elBoberido]

Please add stuff you think should go into our 1.0 release in the comment section. Vote by the 👍 and 👎 if you want the idea into 1.0

[elBoberido]

I think the API compliance tests should be ready for the 1.0 release
#284

[elBoberido]

Building blocks should also be finished, at least the mandatory ones from #252

[elBoberido]

iceoryx-posh and iceoryx-utils meet ROS Quality Level 1 for Linux/Mac/Windows (maybe Level 2?)

[elBoberido]

Rework non-shm interprocess communicution

• rework the initial registering at RouDi, and make sure an application always get a response, at least an error response, even if the application is build with an incompatible iceoryx version compared to RouDi
• document the serialization and/or refactor the current one
• don't transmit the response deep down in multiple classes, but let the classes just return their response to the caller, which makes testing easier

[elBoberido]

decide if we use C++14 as standard (#220)

[elBoberido]

detect if an application registers at RouDi is build with an incompatible iceoryx version compared to RouDi

[budrus]

see https:/eclipse/iceoryx/projects/2 for content of 1.0 release