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.6.8 #38

Closed
1 task
gsmet opened this issue Jan 26, 2024 · 21 comments
Closed
1 task

3.6.8 #38

gsmet opened this issue Jan 26, 2024 · 21 comments

Comments

@gsmet
Copy link
Contributor

gsmet commented Jan 26, 2024 •
edited by github-actions bot
Loading

Branch

3.6

Qualifier

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.

Where am I?
  • Prerequisites ⚙️ ☚ You are here
  • Approve the core release
  • Create branch (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts
  • Update documentation
  • Announce release

@github-actions GitHub Actions
Copy link

We are going to release the following release:

  • Quarkus 3.6.8
  • On branch 3.6
  • With Java 11
  • This is a maintenance release.

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

If not, simply close this issue.

Where am I?
  • Prerequisites ⚙️ ☚ You are here
  • Approve the core release
  • Create branch (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts
  • Update documentation
  • Announce release

@gsmet
Copy link
Contributor Author

gsmet commented Jan 26, 2024

@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 (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts
  • Update documentation
  • Announce release

@github-actions GitHub Actions
Copy link

✅ Core release is approved, proceeding...

@github-actions GitHub Actions
Copy link

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

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.

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 ⏸️ ☚ You are here
  • Create branch (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts
  • Update documentation
  • 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 (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts
  • Update documentation
  • 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.

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

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

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts
  • Update documentation
  • Announce release

@gsmet
Copy link
Contributor Author

gsmet commented Jan 26, 2024

@quarkusbot continue

@github-actions GitHub Actions
Copy link

⚙️ Proceeding to step Prepare the Quarkus Platform

You can follow the progress of the workflow here.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts
  • Update documentation
  • Announce release

@github-actions GitHub Actions
Copy link

✅ The Platform branch 3.6 is ready to be released, continuing...

@github-actions GitHub Actions
Copy link

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

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

The publication of the Platform artifacts will take 20-40 minutes.

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 (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts
  • Update documentation
  • Announce release

@quarkusbot
Copy link
Collaborator

@quarkusbot continue

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

@github-actions GitHub Actions
Copy link

⚙️ Proceeding to step Sync Platform release to Maven Central

You can follow the progress of the workflow here.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch (if needed)
  • 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 ⚙️ ☚ You are here
  • Update extension catalog
  • Execute post-Platform-release operations
  • Update JBang catalog
  • Publish CLI
  • Update quickstarts
  • Update documentation
  • Announce release

@github-actions GitHub Actions
Copy link

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

@github-actions GitHub Actions
Copy link

🚨 An error occurred while executing step Update quickstarts.

For minor versions, we shouldn't have code updates in the Quickstarts.

So, if you got the build failing, either something got wrongly merged in the main branch of https://github.com/quarkusio/quarkus-quickstarts/ or something in Quarkus broke the quickstarts.

You can find more information about the failure here.

This is not a fatal error, you can retry by adding a @quarkusbot retry comment.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts ⚙️ ☚ You are here
  • Update documentation
  • Announce release

@gsmet
Copy link
Contributor Author

gsmet commented Jan 27, 2024

@quarkusbot retry

@github-actions GitHub Actions
Copy link

⚙️ Proceeding to step Update quickstarts

You can follow the progress of the workflow here.

Where am I?
  • Prerequisites
  • Approve the core release
  • Create branch (if needed)
  • 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 JBang catalog
  • Publish CLI
  • Update quickstarts ⚙️ ☚ You are here
  • Update documentation
  • Announce release

@github-actions GitHub Actions
Copy link

✅ 3.6.8 was successfully released.

Connected to the Red Hat VPN, in a clone of https://github.com/quarkusio/quarkus-release, run:

./trigger-performance-testing.sh 3.6.8

to trigger the performance evaluation testing for this release.

Then it is time to write the announcement:

  • Update the versions in _data/versions.yaml
  • Write a blog post for the website
    • Use a previous announcement as a template (be aware, annoucements are very different for the first final of a major/minor and the follow-up micros)
  • Push it and wait for it to be live on quarkus.io - you can follow the progress of the deployment on GitHub Actions
  • Send the announcement to quarkus-dev@googlegroups.com
  • Send the announcement to various social networks using https://buffer.com/

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