Re: [leshan-dev] [cf-dev] Californium 1.0.1 released

[Julien Vermillard <jvermillard@xxxxxxxxx>]

On Wed, Jan 20, 2016 at 10:23 AM, Hudalla Kai (INST/ESY1) <Kai.Hudalla@xxxxxxxxxxxx> wrote:

Julien,

 

I assume you were referring to the latest milestone (0.1.11-M7) using Californium 1.0.1 J

Yes, waiting for maven central to sync before sending the mail.
 

However, I think we should also start to discuss what we would like the 1.0.0 version of leshan to include and what not. In particular I think we should come up with an idea how we want to deal with the still unreleased LWM2M spec.

Yeah, painful topic :(  The 1.0 should not be too long and the draft should now stabilise a little, since the new crazy feature will go to the 1.1 draft. IMO we miss more industrial and implementation oriented company in the OMA DM group. you should consider sending someone for fixing the spec :)

 

In the projects at Bosch where we would like to use leshan (and thus LWM2M for device management) we are often asked which “version”, i.e. release candidate or draft, of the spec we support on the server side. This is difficult to answer since we are currently more or less implementing changes to the spec in leshan on a case by case basis, i.e. if someone feels that we should have it in leshan we implement it. However, we currently make no claims regarding any level of compliance with the spec, or do we?

We tend to support the last published draft with maximum possible backward compatibility. Then once 1.0 is released we can use the registration version parameter (if we decide to support 1.1 draft).
 

 

On the client side we have the same problem but it is even harder to tackle since most of the devices we are talking about are not using leshan but wakaama etc. which we cannot easily keep in sync with leshan (server) …

 

How do you guys at Sierra Wireless are dealing with this problem?

On the server side we have model of which object with which resources the device is supporting, so we build the UI and device management job following this "application" model. Now for workflow object like SW/FW updates it's not so simple.
 

 

Regards,

Kai

From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On Behalf Of Julien Vermillard
Sent: Tuesday, January 19, 2016 5:51 PM
To: Californium (Cf) developer discussions; leshan developer discussions
Subject: Re: [cf-dev] Californium 1.0.1 released

 

Thanks!

let's release Leshan :)

--
Julien Vermillard

 

On Tue, Jan 19, 2016 at 9:32 AM, Hudalla Kai (INST/ESY1) <Kai.Hudalla@xxxxxxxxxxxx> wrote:

Hi,

yesterday we have released Californium 1.0.1 and published artifacts to Maven Central [1] and the Eclipse Release Repo [2].

This is a small bug-fix release only which mainly address some issues with interrupted DTLS handshakes in Scandium.See attached changelogs for details. Users of Californium 1.0.0 should be able to upgrade by simply replacing the 1.0.0 artifacts with the corresponding 1.0.1 artifacts.

The Californium team is glad to announce that we have switched to using GitHub for reporting bugs, issues and improvement ideas instead of Bugzilla. So, if you want to report a bug or have an idea for improvement, please create an issue on the corresponding GitHub project(s) for the affected Californium components [3] or drop us a line on this mailing list.

[1] http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.eclipse.californium%22
[2] https://repo.eclipse.org/content/groups/releases/
[3] https://github.com/eclipse/californium

Regards,
Kai


_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev

 

_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev