Zenoh 1.0.0 release

[Mallets]

Target date: April 22nd, 2024.

A dedicated project has been created to track all the PRs and issues that will land in the release. The high-level set of features is the following:

API polishing

• Review the API and verify the API follows Zenoh's API principles
• Polish-out some rough edges on the API

API alignment

• Provide a coverage matrix for the API and all supported languages
• Make sure the API is aligned across all language bindings

Shared Memory

• Provide Shared Memory support in any topology and not-only in clique
• New API for plugging different types of SHM backends

Protocol improvement

• Review of the protocol
• Improvement of declarations propagation

Tokio porting

• Move Zenoh's async runtime to Tokio
• Provide additional control on threads

CI/CD improvement

• Improve cross-repo integration
• Streamline release process

Eclipse Review

• Eclipse Zenoh 1.0.0 Release

[sanri]

Is it intended to support both async-std and tokio?

[Mallets]

Zenoh internal async runtime is migrating to Tokio. If an application wants to use async-std, it can still doing via async-std's compatibility features. For any additional discussion about this topic, I suggest to move here and not on the roadmap issue.

[sebbyjp]

Shared memory implemented with python bindings?

[keenanjohnson]

This is complete no?