-
Notifications
You must be signed in to change notification settings - Fork 408
Roadmap
We are currently focusing on Leshan 2.0.0 which aims to implement LWM2M v1.1
We are mainly driven by user inputs and user contributions. So we don't really have a defined roadmap for Leshan.
You can have a look to LWM2M supported features.
In a general way, you could have an idea about what will be available at short term looking at opened PR.
Current short/mid term topic are mainly housekeeping :
- work on transport layer abstraction (#1025)
- Experiment Transport layer with java-coap (fork) (#1373)
Potentially, any 1.1.x LWM2M feature could be integrated in Leshan 2.0.0.
Currently, users show interest and/or bring contributions for :
-
Resource Instance Operation(:heavy_check_mark: done) -
SenML-JSON support(:heavy_check_mark: done), -
SenML-CBOR support(:heavy_check_mark: done), -
CBOR support(:heavy_check_mark: done), -
Composite operation.(:heavy_check_mark:Read-Composite #957✔️Write-Composite#959, ✔️Observe-Composite #1034) -
Send operation, (:heavy_check_mark: #971) - OSCORE (:construction: #725),
- Write-Attribute at client side (#534 )
Those features may be available in final Leshan 2.0.0.
dachaac began to work on "Support of EST and better certificate support" (:construction: 1135) but unfortunately there is no more activity on this anymore, if somebody is interested on this he should manifest himself on this issue.
Most missing impacting features are :
- OSCORE (still in development but move very very slowly,no guarantee we will have a minimal viable feature for 2.0.0 #725) (needed by community)
- CoAP over TCP transport. (#1047) (never asked by community)
- Non-IP transport. (#1046) (needed by community, but not sure we can implement )
To be able to add new transport layer and maybe decrease strong dependency to Californium an big task would be refactor the code to make easier to add new transport layer (#1025)
Here is some works we identify but there is no guarantee that we implement all of this for the 2.0.0 :
Keep in mind this is a community project, you can have influence on what will be available in the 2.0.0. So tell us what miss you the most.
The 2.0.0 version will be available when it will be ready. (Debian spirit !)
If you are fine with LWM2M 1.0, just use 1.x stable version of Leshan.
If you need LWM2M 1.1 features, there are milestone releases. They should be usable, but the API is not stable. So, if you are interested in LWM2M 1.1 support in Leshan, you should :
- use/test those milestone releases,
- report us any bug or feebacks,
- share what part of LWM2M 1.1 missing you more,
- contribute code.
This is the best way to get a final 2.0.0 release which fits your needs.
We do not define release date for milestones. Generally this is each 2 or 3 month. But if you need a release sooner, just ask us on the mailing list leshan-dev or github issue!
All contributions you make to our web site (including this wiki) are governed by our Terms of Use, so please take the time to actually read it. Your interactions with the Eclipse Foundation web properties and any information you may provide us about yourself are governed by our Privacy Policy.