Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cf-dev] Release Plan for Californium ?

Hi Simon,

I have started to add some of the open issues on GitHub [1] to the 2.0.0-M3 and
2.0.0 milestones. 

On Wed, 2016-11-16 at 16:55 +0100, Simon Bernard wrote:
> It sounds good to me to put coap+tcp in a more long term branch.
> 
> About the blockwise, we currently use the 2.0.0M2 version of californium 
> and it seems to works :).
> This is just a feeling but I have some doubt about the possibility to 
> extract the blockwise transfer from the stack without extracting the 
> observe layer which is upper it.
> As a Leshan developper and so Californium user, I also appreciate the 
> transparent way blockwise is currently handled. How will this change 
> impact the API ?
> 
> About fixing the scope or the date, I prefer to fix the scope. This 
> allow us to know which modification go in the 2.0 banch and which go in 
> the more long term branch (3.0 ?)
> 

Are there any more issues we need to address in 2.0.0? If so, could you please
try to create corresponding issues so that we can start working on them? Or do
you feel that the current issues and their assignment already reflect the
intended scope of 2.0.0?

I would also like to create a 2.0.0-M3 ASAP so that we can start to adopt the
latest changes in leshan as well. WDYT?

[1] https://github.com/eclipse/californium/issues

Kai

Back to the top