Plan for 2.0.0-M16 🎯

[sbernard31]

This issue is about preparing the 2.0.0-M16 release.

This should contain only :

• Transport Layer Module design. #1295
• Integration of californium 3.12.1 (to fix Issue with running Contiki-NG with latest release of Leshan (2.0.0-M15) #1627)
• Fix TlvEncoder Date encoding for dates in a distant future (exceeding MAX_INT) #1630
• maybe some minor bug fixed in we found some.

To make the migration more smooth.

What is currently included for M16:

New commits in master since M15 :

e673ac753: [ci] Add build artifacts to test jobs.
1377e5262: Integration of Californium 3.12.1
f9137bb00: Clean revapi configuration.
3f9b3f7ad: Change module <name> to avoid them to be too long (ugly mvn output)
8d434d42d: Refactoring add oscore module - edit file content
d5c81f1ea: Refactoring add oscore module - no file content changes [dont build]
bc9031447: Separate DeviceManagement and Bootstrap Request class hierarchy.
ab4f9a457: Refactoring add bsserver module - edit file content
286962589: Refactoring add bsserver module - no file content changes [dont build]
6d2ff69c7: Refactoring rename module/package - edit file content
34caf241c: Refactoring rename module/package - no file content changes [dont build]

Redis Store Compatibility break :
No break.

When ?

Californium 3.12.1 will be release the 9th July (eclipse-californium/californium#2258)
I will be unavailable from 11th to 24th July.

So release will be at the earliest end of July.

[sbernard31]

@cyril2maq, @slaft, @niklas-sparfeld-gcx, @jvermillard, @JaroslawLegierski, @mgdlkundera, @jakubsobolewskisag

master is probably near to the state of what will be released in 2.0.0-M16. (except we find new critical bug)
So you can test master if wanted
This #1295 (comment) could help for migration.

Do not hesitate to share any concerns.

(I'm back on 24th)

[niklas-sparfeld-gcx]

The refactoring changed the sender interface to take a DownlinkDeviceManagementRequest instead of DownlinkRequest. This is of course fine, it's just that you didn't mention it here and I think it is an API change.

[sbernard31]

Yep refactoring lead to some renaming. I didn't list all modifications maybe I should do that at same time I did the rename 😕.

Now we have a clear separation between LWM2M (device management) Server and LWM2M Bootstrap Server, I split DownlinkRequest in DownlinkDeviceManagementRequest and DownlinkBootstrapRequest

There is more changes like this

[slaft]

Just to let you know that we've tested the current master. Nothing to report.

[sbernard31]

@niklas-sparfeld-gcx thx for you feedback 🙏 . Did you face any behavior issue ?

@slaft thx too for testing 🙏 . Not too painful to migrate ? No problem found with new naming ?

[sbernard31]

If there isn't veto I plan to release 2.0.0-M16 on Monday next week.

(of course if you want to discuss about some point before, let me know and we delay the release)

[slaft]

Not too painful to migrate ?

No, it went quite well.

No problem found with new naming ?

Nothing I noticed.

[sbernard31]

I start the release process. (Still possible for you to stop me but not for so long 😁 not anymore)

[sbernard31]

Release 2.0.0-M16 is out now.

Thx guys for your help 😉 !

(if you want to report issue about maven module refactoring please use #1295 (comment))