2027.X Versioning Questions

Ignition 2027 Early Access
1

I'm getting ready to start branching Embr for 2027 support, and I've got some questions WRT versioning, mostly around this statement:

  1. Does 2027.15.0 imply a March 2028 release of Ignition 2027?

  2. What's the expected relationship between the last 2027.2 release and the first 2027.15 release?

  3. Should I expect a module compiled against 2027.2.X to work against 2027.15.Y?
    Or are 2027.2, 2027.15, and (2027+?).Z going to be totally different targets?

Basically I'm trying to decipher if my build target should be simply 2027, or if I need specifically target 2027.2.

(Also I know things may change... a current vibes-based answer would be good enough :laughing:)

1 Like
2

The plan is that the major.minor tuple we previously used as the major version (e.g. 8.1, 7.9, 8.3) is collapsed into the major field, as in, the API stability layer is 2027. Every release of 2027 should have the same SDK/API contract (again, possibly barring the AI-specific things mentioned in the other thread).

Yes, plus/minus a few weeks.

I'm not sure what you're asking here.

1 Like
3

Great, this is what I was hoping for :grin:

Basically asking if 2027.2 and 2027.15 would have the same API level.
Same question, just framed a little different.

So if I'm understanding correctly:
If I have targets for 8.1, 8.3, and 2027, when 2027.15 is released as an LTS, it'll be the same SDK API contract as 2027.2.

(ignoring the AI-specific asterisks, which I'm not super worried about ATM).

4

Yep, that's the intention.
Moving to a new yearly release consistently intentionally allows us to make API breaking changes on a regular cadence, so that we're not doing the thing we've done in the past where we try to "cram" a bunch of stuff in to the next major release because that's our option to make breaking changes. Now that there's a...mega? release train, you get what you get.

1 Like
5

Then once 2027.15.0 is released, will only the patch number update until it's no longer supported or will it still follow months since the year it was originally released.

Are minor versions going to be released every month? (I feel like this was covered at ICC but I've slept since then)

Are the patch numbers going to be for things like fixing regressions between minor versions so then we may not have a patch version other then 0 sometimes not probably never reach 50+ again.

6

So basically, every year:

  • New release with the year of release as it version number
  • Previous years release is branded as LTS

?

7

Every other year.

The branch starting with 2027.2 will become LTS when the branch starting with 2028.2 is released. Then 2029.2 will become LTS when 2030.2 is released.

8

Every other month.

1 Like