[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cf-dev] Preparing a 1.0.5 release and 2.0.0-M3 milestone
|
Any news about the 2.0.0-M3 release ?
Do we still plan to move tcp work from 2.0.0 to another branch as
discussed here[1] ?
Simon
[1] https://dev.eclipse.org/mhonarc/lists/cf-dev/msg00932.html
Le 09/01/2017 à 17:33, Simon Bernard a écrit :
yep :)
Le 09/01/2017 à 17:18, Hudalla Kai (INST/ESY1) a écrit :
On Mon, 2017-01-09 at 16:24 +0100, Simon Bernard wrote:
Sounds good for me too.
About Leshan, we did a lot of change recently and we should made a
release before to integrate the last version of californium in which
there is a lot of changes too.
The idea is to not cumulate the risk of thoses changes.
Sounds reasonable. My understanding is that we would create another
milestone of
leshan based on leshan's (then) current master and then start
migration of
leshan to Californium 2.0.0-M3, right?
Simon
Le 09/01/2017 à 16:18, Kraus Achim (INST/ESY1) a écrit :
Sounds good for me.
Mit freundlichen Grüßen / Best regards
Achim Kraus
Bosch Software Innovations GmbH
Communications (INST/ESY1)
Stuttgarter Straße 130
71332 Waiblingen
GERMANY
www.bosch-si.de
www.blog.bosch-si.com
Registered office: Berlin, Register court: Amtsgericht
Charlottenburg, HRB
148411 B
Executives: Dr.-Ing. Rainer Kallenbach; Michael Hahn
-----Ursprüngliche Nachricht-----
Von: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Hudalla Kai (INST/ESY1)
Gesendet: Montag, 9. Januar 2017 16:14
An: cf-dev@xxxxxxxxxxx
Betreff: [cf-dev] Preparing a 1.0.5 release and 2.0.0-M3 milestone
Hi list,
it has been quite some time that we did the last release (1.0.4) and
milestone (2.0.0-M2). I have already been contacted by Eclipse staff
regarding our plans for the next release ...
I would like to do a 1.0.5 by the end of this week (i.e. until Jan
13th
2017).
There are only a few things that have been fixed (or that needed
fixing, for
that matter ;-)):
* 1fb61cc (HEAD -> 1.0.x, origin/1.0.x) [#180] Use
System.lineSeparator for
logging.
* 45e57d5 [#186] Buffer ChangeCipherSpec message received
out-of-sequence.
* 6b9aea2 [#183] Fix Base64 encoding when using NO_PADDING option.
* b0e9454 Do not automatically include Uri-Port (only for proxying)
* 8030887 Fix #58 NullPointerException on concurrent requests via
async
CoapClient#advanced
* 83d963e [bug #53] Cipher suite negotiation now considers
certificate type.
* 4c68c9b [bug #54] Provide script for creating demo certificates.
* 555843b [#41] Move code for fixing #36 to Blockwise layer
* 2113763 Release 1.0.4
Anything else you would like to see addressed in it?
I would then also like to create 2.0.0-M3 once PR #170 [1] has been
merged so
that we can start to rebase leshan onto it.
WDYT?
[1] https://github.com/eclipse/californium/pull/170
--
Mit freundlichen Grüßen / Best regards
Kai Hudalla
Chief Software Architect
Bosch Software Innovations GmbH
Schöneberger Ufer 89-91
10785 Berlin
GERMANY
www.bosch-si.com
Registered office: Berlin, Register court: Amtsgericht
Charlottenburg, HRB
148411 B;
Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
_______________________________________________
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
