search

eclipse / milo

Eclipse Milo™ - an open source implementation of OPC UA (IEC 62541).
http://www.eclipse.org/milo
Eclipse Public License 2.0
1.15k stars 427 forks source link

OPC UA 1.05 and Milo 1.0.0 Release #1130

Open kevinherron opened 1 year ago

kevinherron commented 1 year ago

Parent ticket for all 1.0 sub-tasks and issues.

kevinherron commented 1 year ago

ETA... late 2023, early 2024. Definitely not before the Germany OPC interop event in October.

perivarbakke commented 8 months ago

ETA... late 2023, early 2024. Definitely not before the Germany OPC interop event in October.

@kevinherron Can we still expect this release early 2024 (Q1)?

kevinherron commented 8 months ago

I don't know, I'm about to resume working on it. There's a chance it could be ready by April, after I've attended the OPC interoperability event in March.

The time I thought was going to be allocated to working on it at my job vs. on the side got reallocated to something higher priority.

apupier commented 5 months ago

provided https://github.com/eclipse/milo/pull/1263 for the migration from testNG to JUnit 5

andvasp commented 3 months ago

Hi @kevinherron,

Since there are breaking changes in this version (specially #1223), would it not be good to have a version 0.7 based on 1.0?

Thanks!

kevinherron commented 3 months ago

I don't see the point in that.

andvasp commented 3 months ago

The point is that with a published version it will be easier to use (migrate our code), test and even suggest any modifications to the API prior to 1.0, which should be more stable. And you don't need to worry about all the requirements to release version 1.0.

A lot of other systems can enjoy this version too as mentioned here #1098.

Why not incremental releases?

Anyway thanks for the great job you are doing here!

kevinherron commented 3 months ago

You can develop against dev/1.0 (we are currently doing this at $WORK for our next big release).

I don't want to do an intermediate release with a bunch of breaking changes, when it's a certainty that 1.0 will introduce more. It's just extra work I'd be asking people to deal with. 1.0 will be one big ugly migration effort which you can start at any time you like by developing against dev/1.0.

When 1.0 is released I have no intention of supporting any 0.x releases, which will be another pain point for anyone who migrated to a hypothetical 0.7.x release.

kevinherron commented 3 months ago

Sorry for the gruff response, I've got a lot on my plate between now and the end of the year 😬

andvasp commented 3 months ago

Don't worry. I didn't consider it as a rugged response.

stegal-bh commented 3 weeks ago

Hi guys, any update about ETA for the 1.0.0 release ?

kevinherron commented 3 weeks ago

Nobody but me occasionally working on this. Maybe something in January? Who knows.

Anybody who has time to build and test with dev/1.0 branch would be helping me out.

andvasp commented 3 weeks ago

Hi @kevinherron!

I will try to test it.