[zenoh-dev] Work Plan

[Julien Enoch <julien.enoch@xxxxxxxxxxxxxx>]

Dear all,

Following Angelo’s email on « zenoh: Next Steps » , I would like to discuss the working plan for the next few months.

The current situation is the following:

• Prior to initial code drop to Eclipse, zenoh was managed in the those repositories:
• https://github.com/atolab/zenoh
• https://github.com/atolab/zenoh-c
• https://github.com/atolab/zenoh-java
• https://github.com/atolab/zenoh-go
• https://github.com/atolab/zenoh-python
• The latest release before code drop was 0.4.0 (0.4.1 for Zenoh and zenoh-java APIs that required a fix)
• The code that have been dropped to Eclipse has the tag "Eclipse-initial-contribution-2" in those repos. wrt. previous releases, it has been amended with new license (adding EPL 2.0 and updating of copyright header)
• Only the zenoh-java code has been modified prior to code drop to use « org.eclipse.java » as package name and Maven groupId.

Now, considering that the infrastructure of zenoh will be re-written in Rust in replacement of OCaml, and that the wire-protocol will also change, I don’t think it’s worth to plan an official Eclipse release based on the current code. It will be lot of efforts, especially for the IP review of OCaml dependencies, some of whom are under LGPL (AFAIK this is a problematic point for Eclipse).

As a consequence, I suggest the following plan:

• Release 0.4.2-M1:
• A milestone release of the current code, not requiring a full IP review of dependencies.
• This will allow users to have their 1st experiments with Eclipse zenoh, and hopefully give us some precious feedbacks. And to push to Maven Central the 1st version of zenoh-java with the new « org.eclipse.java » package.
• Note that we don’t plan to do a final release of 0.4.2.
• Release 0.5.0:
• The 1st version of Eclipse zenoh with the Rust based infrastructure. The goal being to provide at least the same features than in version 0.4.1.
• It will also includes some changes in the protocol, and possibly the APIs. It will not be interoperable with the previous versions.

Depending on the progress of Rust developments, we could do some Milestone releases. For instance:

• 0.5.0-M1: implementation of the protocol + a broker + the zenoh-net APIs
• 0.5.0-M2: addition of the zenoh APIs + the HTTP plugin + a built-in memory backend
• 0.5.0-M3: addition of the storages plugin + the InfluxDB backend + a router

If you have any comment or suggestion, please feel free to reply.

Best regards,

Julien Enoch
Senior Technologist — Advanced Technology Office
ADLINK Technology Inc.