[Feature Request]: when 0.11.0 version release???

Question

[Feature Request]: when 0.11.0 version release???

kdxq opened this issue a year ago · comments

kdxq commented a year ago

What would you like to happen?

when 0.11.0 version release???

Programming Languages

plc4j
plc4go
plc4c
plc4net

Protocols

Christofer Dutz · Answer 1 · Wed Jul 19 2023 15:56:14 GMT+0800 (China Standard Time)

when done ;-)

Łukasz Dywicki · Answer 2 · Wed Jul 19 2023 20:36:25 GMT+0800 (China Standard Time)

I think that we could and even should make an 0.11.0-RC1 build (or a bit late 0.11.0-2Q2023 => 2nd quarter of 2023), to tag current develop state. We found that some of unit tests we had did not cover some edge cases, so we're still prone to manual testing conducted by end users. As usual, there is some ongoing development, but if we don't do releases we leave people to same problem summarized as "use latest snapshot" and miss a feedback loop of what got broken in mean while.

Sebastian Rühl · Answer 3 · Wed Jul 19 2023 20:47:34 GMT+0800 (China Standard Time)

I really dislike those "-RC/Milestone/whatever" releases as those trigger renovate/dependabot and suggest those are normal releases as those bots/implementation don't understand that this isn't a real release. And by just releasing something it doesn't magically stabilize. E.g. we still need to fix the s7 driver in golang.

Sebastian Rühl · Answer 4 · Wed Jul 19 2023 20:48:26 GMT+0800 (China Standard Time)

Also: We always have the option to backport changes into a point release if they a urgently needed.

Sebastian Rühl · Answer 5 · Wed Jul 19 2023 20:50:33 GMT+0800 (China Standard Time)

so to wrap that up: we don't have a date for a release yet

Łukasz Dywicki · Answer 6 · Wed Jul 19 2023 20:54:33 GMT+0800 (China Standard Time)

I really dislike those "-RC/Milestone/whatever" releases as those trigger renovate/dependabot and suggest those are normal releases as those bots/implementation don't understand that this isn't a real release. And by just releasing something it doesn't magically stabilize. E.g. we still need to fix the s7 driver in golang.

The way in which mentioned tools deal with our release is not related to issue. Reading your comment in reverse order I could understand that making no releases makes these tools happier. ;)
We won't stabilize things by releases, but do have a marker when things broke. With 11 months old snapshot you never know when things rotten.

I doubt if backporting a change made on a year old feature development branch (which develop in fact is) will ever succeed. It will work with minor patches, but not with new features which are based on i.e. MSpec generator updates etc.