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

3.21.0.CR1 #137

Open
2 tasks
gsmet opened this issue Mar 12, 2025 · 14 comments
Open
2 tasks

3.21.0.CR1 #137

gsmet opened this issue Mar 12, 2025 · 14 comments

Comments

@gsmet
Copy link
Contributor

gsmet commented Mar 12, 2025 •
edited by github-actions bot
Loading

Branch

3.21

Qualifier

CR1

Emergency release

  • This release is an emergency release.

Origin branch

No response

Major version

  • This release is a major version.
@github-actions GitHub Actions
Copy link

⚙️ Proceeding to step Prerequisites

You can follow the progress of the workflow here.

@github-actions GitHub Actions
Copy link

🙌 We are going to release the following release:

  • Quarkus 3.21.0.CR1
  • On branch 3.21 (it will get created a bit further in the process)
  • With Java 17
  • This is a preview release (e.g. Alpha, Beta, CR).

Important

Make sure you have merged all the required pull requests in the main branch.

Please approve with a @quarkusbot yes comment if you want to continue with the release.

If not, simply close this issue.

Tip

Don't go too far, we will need further input from you very soon.

Legend for the admonitions

[!IMPORTANT]
A manual confirmation/intervention is needed.

[!TIP]
Some useful information about the release process.

[!NOTE]
Some additional information.

[!WARNING]
Something important to consider.

[!CAUTION]
An error occurred.

Where am I?
  • Prerequisites
  • Approve the core release ⏸️ ☚ You are here
  • Create branch
  • Prepare the core release
  • Perform the core release
  • Sync core release to Maven Central
  • Release Gradle plugin
  • Execute post-core-release operations
  • Prepare the Quarkus Platform
  • Release the Quarkus Platform
  • Sync Platform release to Maven Central
  • Update extension catalog
  • Execute post-Platform-release operations
  • Update quickstarts
  • Announce release

@gsmet
Copy link
Contributor Author

gsmet commented Mar 12, 2025

@quarkusbot yes

@github-actions GitHub Actions
Copy link

⚙️ Proceeding to step Approve the core release

You can follow the progress of the workflow here.

Where am I?
  • Prerequisites
  • Approve the core release ⚙️ ☚ You are here
  • Create branch
  • Prepare the core release
  • Perform the core release
  • Sync core release to Maven Central
  • Release Gradle plugin
  • Execute post-core-release operations
  • Prepare the Quarkus Platform
  • Release the Quarkus Platform
  • Sync Platform release to Maven Central
  • Update extension catalog
  • Execute post-Platform-release operations
  • Update quickstarts
  • Announce release

@github-actions GitHub Actions
Copy link

✅ Core release is approved, proceeding...

Tip

Don't go too far, we will need some input from you very soon.

@github-actions GitHub Actions
Copy link

Warning

IMPORTANT This is the first Candidate Release and this release requires special care.

🙌 You have two options:

  • Let the release process handle things automatically: it will create the branch automatically from main and handle additional housekeeping operations
  • Perform all the operations manually

Important

To let the release process handle things automatically for you, simply add a @quarkusbot auto comment.

How to perform the operations manually?

If you choose to do things manually, make sure you perform all the following tasks:

  • Create the 3.21 branch and push it to the upstream repository
  • Rename the 3.21 - main milestone here to 3.21.0.CR1
  • Create a new milestone X.Y - main milestone here with X.Y being the next major/minor version name. Make sure you follow the naming convention, it is important.
  • Rename the triage/backport label to triage/backport-3.21
  • Create a new triage/backport label
  • Make sure all the current opened pull requests with the triage/backport-3.21 label also have the new triage/backport label (in the UI, you can select all the pull requests with the top checkbox then use the Label dropdown to apply the triage/backport label)
  • Send an email to [email protected] announcing that 3.21 has been branched and post on Zulip #dev stream:

Subject:

Quarkus 3.21 branched

Body:

Hi,

We just branched 3.21. The main branch is now **X.Y**.

Please make sure you add the appropriate backport labels from now on:

- for anything required in 3.21 (currently open pull requests included), please add the triage/backport label
- for fixes we also want in future 3.19, please add the triage/backport-3.19 label
- for fixes we also want in future 3.15 LTS, please add the triage/backport-3.15 label
- for fixes we also want in future 3.8 LTS, please add the triage/backport-3.8 label
- for fixes we also want in future 3.2 LTS, please add the triage/backport-3.2 label

Thanks!

--
The Quarkus dev team

Once you are done with all this, add a @quarkusbot manual comment to let the release process know you have handled everything manually.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch ⏸️ ☚ You are here
  • Prepare the core release
  • Perform the core release
  • Sync core release to Maven Central
  • Release Gradle plugin
  • Execute post-core-release operations
  • Prepare the Quarkus Platform
  • Release the Quarkus Platform
  • Sync Platform release to Maven Central
  • Update extension catalog
  • Execute post-Platform-release operations
  • Update quickstarts
  • Announce release

@gsmet
Copy link
Contributor Author

gsmet commented Mar 12, 2025

@quarkusbot auto

@github-actions GitHub Actions
Copy link

⚙️ Proceeding to step Create branch

You can follow the progress of the workflow here.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch ⚙️ ☚ You are here
  • Prepare the core release
  • Perform the core release
  • Sync core release to Maven Central
  • Release Gradle plugin
  • Execute post-core-release operations
  • Prepare the Quarkus Platform
  • Release the Quarkus Platform
  • Sync Platform release to Maven Central
  • Update extension catalog
  • Execute post-Platform-release operations
  • Update quickstarts
  • Announce release

@github-actions GitHub Actions
Copy link

✅ Branch 3.21 has been created and the milestone and backport labels adjusted.

We created a new 3.22 - main milestone for future developments.

Make sure to adjust the name of the milestone if needed as the name has simply been inferred from the current release.

Important

Please announce that we branched 3.21 by sending an email to [email protected] and posting on Zulip #dev stream:

(Make sure to adjust the version in the email if you renamed the milestone)

Subject:

Quarkus 3.21 branched

Body:

Hi,

We just branched 3.21. The main branch is now 3.22.

Please make sure you add the appropriate backport labels from now on:

- for anything required in 3.21 (currently open pull requests included), please add the triage/backport label
- for fixes we also want in future 3.19, please add the triage/backport-3.19 label
- for fixes we also want in future 3.15 LTS, please add the triage/backport-3.15 label
- for fixes we also want in future 3.8 LTS, please add the triage/backport-3.8 label
- for fixes we also want in future 3.2 LTS, please add the triage/backport-3.2 label

Thanks!

--
The Quarkus dev team

Tip

Apart from sending the email and posting on Zulip, no intervention from you is needed, the release process is in progress.

The next steps take approximately 3 hours so don't panic if it takes time.
You will receive feedback in this very issue when further input is needed or if an error occurs.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch ⚙️ ☚ You are here
  • Prepare the core release
  • Perform the core release
  • Sync core release to Maven Central
  • Release Gradle plugin
  • Execute post-core-release operations
  • Prepare the Quarkus Platform
  • Release the Quarkus Platform
  • Sync Platform release to Maven Central
  • Update extension catalog
  • Execute post-Platform-release operations
  • Update quickstarts
  • Announce release

@github-actions GitHub Actions
Copy link

✅ The core artifacts have been pushed to s01.oss.sonatype.org.

Warning

IMPORTANT You need to wait for them to be synced to Maven Central before continuing with the release.

The publication of the core artifacts will take 60-80 minutes.

Tip

We started a separate workflow to monitor the situation for you. It will automatically continue the release process once it detects the artifacts have been synced to Maven Central.

If things go south

If things go south, you can monitor the situation manually:

Once these two conditions are met, you can continue with the release by adding a @quarkusbot continue comment.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch
  • Prepare the core release
  • Perform the core release
  • Sync core release to Maven Central ⏸️ ☚ You are here
  • Release Gradle plugin
  • Execute post-core-release operations
  • Prepare the Quarkus Platform
  • Release the Quarkus Platform
  • Sync Platform release to Maven Central
  • Update extension catalog
  • Execute post-Platform-release operations
  • Update quickstarts
  • Announce release

@quarkusbot
Copy link
Collaborator

@quarkusbot continue

✅ We have detected that the core artifacts have been synced to Maven Central.

@github-actions GitHub Actions
Copy link

⚙️ Proceeding to step Sync core release to Maven Central

You can follow the progress of the workflow here.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch
  • Prepare the core release
  • Perform the core release
  • Sync core release to Maven Central ⚙️ ☚ You are here
  • Release Gradle plugin
  • Execute post-core-release operations
  • Prepare the Quarkus Platform
  • Release the Quarkus Platform
  • Sync Platform release to Maven Central
  • Update extension catalog
  • Execute post-Platform-release operations
  • Update quickstarts
  • Announce release

@github-actions GitHub Actions
Copy link

✅ Core artifacts have been synced to Maven Central, continuing...

@github-actions GitHub Actions
Copy link

🙌 Now is time to update Quarkus in the Quarkus Platform. This is a manual process.

Tip

In the case of preview releases (e.g. Alpha1, CR1...), the release will be built from the main branch

Important

First, you need to update the Platform locally, create a pull request, wait for CI and merge it.

You can find detailed instructions below.

  • Go into your Quarkus Platform clone directory:
cd <your quarkus-platform clone>
  • Follow (roughly) these steps (upstream is the upstream repository, origin is your fork):
git checkout main
git pull upstream main
git checkout -b quarkus-3.21.0.CR1
./update-quarkus-version.sh 3.21.0.CR1
  • Check the diff with git diff
  • Then:
git add .
git commit -m 'Upgrade to Quarkus 3.21.0.CR1'
git push origin quarkus-3.21.0.CR1

Important

Once everything has been merged to branch main, you can continue with the release by adding a @quarkusbot continue comment.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch
  • Prepare the core release
  • Perform the core release
  • Sync core release to Maven Central
  • Release Gradle plugin
  • Execute post-core-release operations
  • Prepare the Quarkus Platform ⏸️ ☚ You are here
  • Release the Quarkus Platform
  • Sync Platform release to Maven Central
  • Update extension catalog
  • Execute post-Platform-release operations
  • Update quickstarts
  • Announce release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gsmet @quarkusbot