Next LTS will be 3.15 #2043
Merged
Next LTS will be 3.15 #2043
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maxandersen
reviewed
Jul 11, 2024
|
🙈 The PR is closed and the preview is expired. |
maxandersen
reviewed
Jul 11, 2024
_posts/2024-11-07-next-lts-3-15.adoc
Outdated
|
|
||
| If you contribute to Quarkus or the Quarkus Platform and need a feature in the next Quarkus LTS, | ||
| make sure it has been merged in the https://github.com/quarkusio/quarkus[Quarkus repository] before August 13th included | ||
| (the day before the `3.14.0.CR1` release). |
There was a problem hiding this comment.
should we put something like "After August 13th main will be what becomes Quarkus 3.16" or similar so its explicit main is for new stuff.
There was a problem hiding this comment.
It's explained in the details for each version.
maxandersen
reviewed
Jul 11, 2024
_posts/2024-11-07-next-lts-3-15.adoc
Outdated
| **Consequently, and this is important: | ||
| if you contribute to Quarkus or the Quarkus Platform and need a feature in the next Quarkus LTS, | ||
| make sure it has been merged in the https://github.com/quarkusio/quarkus[Quarkus repository] before August 13th included | ||
| (the day before the `3.14.0.CR1` release).** |
There was a problem hiding this comment.
we should have something for Quarkiverse/non-quarkus participators too, in the original LTS (https://quarkus.io/blog/lts-releases/) we had something like:
Quarkus Extension Maintainers and Contributors
All of the above applies to Quarkus extension maintainers and contributors as well. In addition, we will be recommending that extension maintainers and contributors consider bug fixes and enhancements for LTS releases. This will ensure that LTS releases are as stable and robust as possible.
This means that extension maintainers and contributors will need to consider having branches and versioning in place for LTS releases.
There was a problem hiding this comment.
I added something along these lines in the 3.15 paragraph.
cescoffier
reviewed
Jul 11, 2024
|
I think I addressed your comments. |
|
Let me know when you're OK with me publishing it. |
cescoffier
approved these changes
Jul 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
** If you are updating a guide, please submit your pull request to the main repository: https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc **