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.

Sign up for GitHub

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

Jump to bottom

quarkus 3.3, branching for 3.2 LTS and the change from nativeimage:svm to sdk:graal-sdk #248

Closed
turing85 opened this issue Jul 19, 2023 · 4 comments
Closed

quarkus 3.3, branching for 3.2 LTS and the change from nativeimage:svm to sdk:graal-sdk #248

turing85 opened this issue Jul 19, 2023 · 4 comments
Assignees
@turing85
Labels
maintenance

Comments

@turing85
Copy link
Contributor

turing85 commented Jul 19, 2023 •
edited
Loading

The next minor release of quarkus (3.3) brings some changes that must be handled in conjunction.

  1. quarkus 3.2 as LTS
    For LTS support, we need a separate branch. I propose to use a 3.0 branch, which "tracks" quarkus 3.2, making our 3.0 compatible with quarkus 3.2 LTS. We need to set-up corresponding dependabot-rules.
  2. With quarkus 3.3, Move to sdk:graal-sdk over nativeimage:svm quarkusio/quarkus#34145 is planned to come into effect. The change on our end was already done in Use graal-sdk instead of svm #246, but is - as of now - unreleased. When quarkus 3.3 lands (and we upgraded), we need to produce a new release. I propose version 3.1.0, so it does not interfer with the 3.0-branch for LTS support of quarkus 3.2.
  3. As of now, it is unclear whether the change to nativeimage:svm will be downstreamed to 3.2. Hence we need to look out for this change hitting 3.2. The relevant commit-id in quarkus is 70e837b427d4f4be6c6946e559561f6236d6d834.
  4. We should provide a compatibility list that shows which of our releases correlate to (LTS)-releases of quarkus. As of now:
    • Our 2.x is compatible with quarkus 2.x (I have no exact data on this, I know it is compatible with at least 2.13.x)
    • Our 3.0 is compatible with all quarkus 3.0-, 3.1- and 3.2-releases
    • Our latest3.0 will support quarkus 3.2 LTS
    • Our latest 3.1 will support quarkus 3.3 and onwards
@turing85 turing85 self-assigned this Jul 19, 2023
@turing85 turing85 changed the title quarkus 3.3, branching 3.2 for LTS and the change from nativeimage:svm to sdk:graal-sdk quarkus 3.3, branching for 3.2 LTS and the change from nativeimage:svm to 'sdk:graal-sdk` Jul 19, 2023
@turing85 turing85 changed the title quarkus 3.3, branching for 3.2 LTS and the change from nativeimage:svm to 'sdk:graal-sdk` quarkus 3.3, branching for 3.2 LTS and the change from nativeimage:svm to sdk:graal-sdk Jul 19, 2023
@turing85 turing85 mentioned this issue Jul 21, 2023
Closed
@middagj
Copy link
Contributor

middagj commented Jul 21, 2023

Small comment, does a 3.1 increment leaves enough room for a possible non-patch release on 3.2 LTS? Or that is just not expected as also Quarkus does not leave room for it.

@turing85
Copy link
Contributor Author

Well, everything in 3.0 must be on minor level semantics, i.e. only non-breaking changes. If we want the possibility for breaking changes, we'd need a 3.2 brach and "leava a gap" (which is most probably confusing to most people)

@middagj
Copy link
Contributor

middagj commented Jul 21, 2023

True, let's do 3.1. Purpose of LTS is to be stable, so means patch only.

@turing85
Copy link
Contributor Author

turing85 commented Aug 18, 2023 •
edited
Loading

Branch 3.0.x has been created.
The documentation update for the compatibility list has been merged (#250) and downstreamed to branches 3.0.x and 2.x.
A PR for the corresponding dependabot-config has been created (#261). When this PR is merged, it will be downstreamed to branches 3.0.x and 2.x.
A Release PR for version 3.1.0 has also been created (#262).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@turing85 turing85

Labels
maintenance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@middagj @turing85