Re: [cf-dev] Roadmap

[Kai <sophokles.kh@xxxxxxxxx>]

Hi Joe,

I have already reached out to Matthias Kovatsch (the Californium project lead) regarding the road map et al. However, I havent't gotten an answer yet. He seems to be pretty busy lately with his new job :-(

Kai

On Fri, Aug 26, 2016 at 6:32 AM Joe Magerramov <joe.magerramov@xxxxxxxxx> wrote:

Hi Kai,

what's the latest on 1.1 release?

On Fri, Jul 8, 2016 at 12:07 AM Hudalla Kai (INST/ESY1) <Kai.Hudalla@xxxxxxxxxxxx> wrote:

On Do, 2016-07-07 at 16:29 +0200, Simon Bernard wrote:
> Hi,
>
>    About the 1.1.0 branch, I have no comments. (I didn't looked at
> the 
> TCP PR yet, but I will)
That would be great, I think Joe has done a great job there :-)

>
>    About the 2.0.0 branch, a stable release for October seems not 
> realistic for me. From my point this is a long term development
> branch.
It's good to hear your opinion on that, I think this will mainly become
an issue of scoping (what should be supported, what not?). That's also
the reason why I have tried to be a little more specific about the
feature I had in mind.

>    For the 2.0.0-M2 (+ improve support for failing over
> Notifications 
> for observed resources) did you have something specific in mind ? I
> know 
> there is severals point to address before to consider failing over 
> Notifications as finished but I don't plan to do that soon.
>
No, nothing specific, just smoothing the edges and make it work
reliably for the use case it should address. Given the CRs currently
being discussed within the LWM2M working group at OMA I think we should
revisit our expectations regarding which scenarios Californium should
support for failing over clients to other nodes. In particular, I am
not sure if it is a good idea to try to support observation of server
(LWM2M client) resources that change their IP addresses. But I think we
should discuss this on a separate thread.


> Simon
>
>
>
> Le 06/07/2016 à 18:14, Hudalla Kai (INST/ESY1) a écrit :
> >
> > Forgot to add links ...
> >
> >
> > On Mi, 2016-07-06 at 16:11 +0000, Hudalla Kai (INST/ESY1) wrote:
> > >
> > > Hi committers,
> > >
> > > I don't know if you have noticed, but Joe Magerramov has created
> > > two
> > > PRs [1][2] for adding CoAP-over-TCP support to Californium based
> > > on
> > > the
> > > corresponding RFC [3] which from my point of view can soon be
> > > merged
> > > to
> > > master and/or the 2.0.x branch.
> > >
> > > Joe has rightfully brought up the question of when this
> > > contribution
> > > might be reflected in an upcoming release. We haven't been very
> > > good
> > > (read: have sucked terribly) in providing a roadmap for
> > > Californium
> > > in
> > > the past so I would like to take this opportunity to improve in
> > > this
> > > area :-)
> > >
> > > We have just recently spawned the 2.0.x branch in order to work
> > > on
> > > long
> > > needed support for clustering and horizontal scale out. However,
> > > this
> > > is still work in progress AFAIK and I would not (yet) put it into
> > > a
> > > release. Therefore I would rather propose to do a 1.1 release
> > > (from
> > > master) any time soon including the TCP support (if we can do it
> > > in a
> > > non-API-breaking way).
> > >
> > > So, here's my proposal for a first roadmap:
> > >
> > > 1.1.x branch
> > >
> > > Aug: 1.1.0-M1 (+ initial support for TCP, + all bugfixes from
> > > 1.0.x
> > > branch)
> > > Sep: 1.1.0
> > >
> > > 2.0.x branch
> > >
> > > Aug: 2.0.0-M2 (+ improve support for failing over Notifications
> > > for
> > > observed resources)
> > > Sep: 2.0.0-M3 (+ support for TCP)
> > > Oct: 2.0.0
> > >
> > > WDYT?
> > [1] https://github.com/eclipse/californium/pull/66
> > [2] https://github.com/eclipse/californium/pull/67
> > [3] https://tools.ietf.org/html/draft-ietf-core-coap-tcp-tls-02
> > _______________________________________________
> > 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
> _______________________________________________
> 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
_______________________________________________
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

_______________________________________________
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