Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OPC UA 1.05 and Milo 1.0.0 Release #1130

Open
3 of 10 tasks
kevinherron opened this issue Jun 12, 2023 · 13 comments
Open
3 of 10 tasks

OPC UA 1.05 and Milo 1.0.0 Release #1130

kevinherron opened this issue Jun 12, 2023 · 13 comments
Milestone

Comments

@kevinherron
Copy link
Contributor

kevinherron commented Jun 12, 2023

Parent ticket for all 1.0 sub-tasks and issues.

@kevinherron kevinherron added this to the 1.0 milestone Jun 12, 2023
@kevinherron kevinherron pinned this issue Jun 12, 2023
@kevinherron

This comment was marked as outdated.

@perivarbakke

This comment was marked as outdated.

@kevinherron

This comment was marked as outdated.

@apupier
Copy link
Contributor

apupier commented Apr 19, 2024

provided #1263 for the migration from testNG to JUnit 5

@andvasp
Copy link

andvasp commented Jun 28, 2024

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
Copy link
Contributor Author

I don't see the point in that.

@andvasp
Copy link

andvasp commented Jun 28, 2024

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
Copy link
Contributor Author

kevinherron commented Jun 28, 2024

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
Copy link
Contributor Author

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

@andvasp
Copy link

andvasp commented Jul 1, 2024

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

@stegal-bh
Copy link

stegal-bh commented Sep 11, 2024

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

@kevinherron
Copy link
Contributor Author

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
Copy link

andvasp commented Sep 13, 2024

Hi @kevinherron!

I will try to test it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants