> PS: Might be a good time to present a project update at the IoT WG call :)
I'd like to wait until 0.5.0 to do that. I anticipate that will be the last major release before 1.0.
I ran out of time here with 0.4.0, but Milo 0.5.0 will fully pass the OPC Foundation's compliance test tool and servers based on Milo will be ready to undergo the official certification process by test labs. The only remaining issue is that the new diagnostics implementation in 0.4.0 "lazily" updates its values, which doesn't play nice with the CTT tests that verify the diagnostics work. Technically this isn't even non-compliant but it's not worth trying to fight that point rather than just modify the implementation.
And errgh, is it allowed to release a 1.0 but remain in incubation? I'd like to indicate that the API is stable and the implementation is considered feature complete (enough) by using version 1.0.0, but I have not managed to build enough of a community of contributors or documentation to reasonably graduate yet.
