v1.0.0
Version 1.0.0 of up-cpp is a major rewrite of the library targeted at the 1.6.0 uProtocol spec. This is the release for milestone alpha.2.
What's Changed
- Full support for uProtocol 1.6.0 (formerly called 1.5.8)
- Brand new API with clear separation between uProtocol layers
- Revised error propagation model to avoid silent failures
- Complete code rewrite
- Improved documentation
- Improved build process for developers and users of up-cpp
- Extensive unit test coverage (94.1% at time of tagging)
- Callbacks are now represented as RAII-style connections to reduce the risk of registration leaks
- uE developers now write code to the up-cpp API and not the transport-specific implementations, allowing for transports to be swapped without rewriting the whole uE
Full Changelog: up-v1.5.7-0.1.3...v1.0.0
Known Issues
- No support for Layer 3 uProtocol services (target milestone: alpha.3)
- Layer 2 integration tests are incomplete (#172 #173 #174)
- Removal of fulfilled RPC requests from the
RpcClient
's expiration queue does not occur until the request's scheduled timeout (#221) - Several unaddressed findings from
valgrind
checks (#196) - A small number of unit tests can fail intermittently (#162)
- Some parameter validity checks are missing (#193 #194)
- Payload builder does not support the
PROTOBUF_WRAPPED_IN_ANY
format (#141) - Several unaddressed
clang-tidy
findings (#232) - TCK tests have not been run to verify compatibility with other uProtocol implementations (target milestone: alpha.3)
New Contributors
- @ruchirchauhan made their first contribution in #126
- @BishrutSubedi made their first contribution in #128
- @pranavishere2 made their first contribution in #143
- @debruce made their first contribution in #124
- @netomi made their first contribution in #167
- @agosh01 made their first contribution in #176
- @MarkStokes71 made their first contribution in #171