quarkus-release / release

Releasing Quarkus, the supersonic subatomic way
1 stars 1 forks source link

3.8.1 #47

Closed gsmet closed 7 months ago

gsmet commented 7 months ago

Branch

3.8

Qualifier

No response

Major version

github-actions[bot] commented 7 months ago

:gear: Proceeding to step Prerequisites

You can follow the progress of the workflow here.


Where am I? - [ ] Prerequisites :gear: ☚ 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[bot] commented 7 months ago

We are going to release the following release:

If not, simply close this issue.


Where am I? - [X] Prerequisites - [ ] Approve the core release :pause_button: ☚ 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
gsmet commented 7 months ago

@quarkusbot yes

github-actions[bot] commented 7 months ago

:gear: Proceeding to step Approve the core release

You can follow the progress of the workflow here.


Where am I? - [X] Prerequisites - [ ] Approve the core release :gear: ☚ 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[bot] commented 7 months ago

:white_check_mark: Core release is approved, proceeding...

:bulb: The Core release steps take approximately 2 hours and 30 minutes 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.

github-actions[bot] commented 7 months ago

:white_check_mark: 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: * Wait for 1 hour (starting from the time of this comment) * Check that https://repo1.maven.org/maven2/io/quarkus/quarkus-bom/3.8.1/ does not return a 404 Once these two conditions are met, you can continue with the release by adding a `@quarkusbot continue` comment.

Where am I? - [X] Prerequisites - [X] Approve the core release - [X] Create branch (if needed) - [X] Prepare the core release - [X] Perform the core release - [ ] Sync core release to Maven Central :pause_button: ☚ 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
quarkusbot commented 7 months ago

@quarkusbot continue

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

github-actions[bot] commented 7 months ago

:gear: Proceeding to step Sync core release to Maven Central

You can follow the progress of the workflow here.


Where am I? - [X] Prerequisites - [X] Approve the core release - [X] Create branch (if needed) - [X] Prepare the core release - [X] Perform the core release - [ ] Sync core release to Maven Central :gear: ☚ 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[bot] commented 7 months ago

:white_check_mark: Core artifacts have been synced to Maven Central, continuing...

github-actions[bot] commented 7 months ago

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

:warning: This is the .0 release so we update the Platform first then wait one week for the Platform members to contribute their updates then we release. Make sure you follow the instructions closely.

cd <your quarkus-platform clone>
git checkout main
git pull upstream main
git checkout -b quarkus-3.8.1
./update-quarkus-version.sh 3.8.1
git add .
git commit -m 'Upgrade to Quarkus 3.8.1'
git push origin quarkus-3.8.1
git checkout main
git pull upstream main
git checkout -b 3.8
git push upstream 3.8

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


Where am I? - [X] Prerequisites - [X] Approve the core release - [X] Create branch (if needed) - [X] Prepare the core release - [X] Perform the core release - [X] Sync core release to Maven Central - [X] Release Gradle plugin - [X] Execute post-core-release operations - [ ] Prepare the Quarkus Platform :pause_button: ☚ 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
gsmet commented 7 months ago

@quarkusbot continue

github-actions[bot] commented 7 months ago

:gear: Proceeding to step Prepare the Quarkus Platform

You can follow the progress of the workflow here.


Where am I? - [X] Prerequisites - [X] Approve the core release - [X] Create branch (if needed) - [X] Prepare the core release - [X] Perform the core release - [X] Sync core release to Maven Central - [X] Release Gradle plugin - [X] Execute post-core-release operations - [ ] Prepare the Quarkus Platform :gear: ☚ 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[bot] commented 7 months ago

:white_check_mark: The Platform branch main is ready to be released, continuing...

github-actions[bot] commented 7 months ago

:white_check_mark: 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: * Wait for 40 minutes (starting from the time of this comment) * Check that https://repo1.maven.org/maven2/io/quarkus/platform/quarkus-bom/3.8.1/ does not return a 404 Once these two conditions are met, you can continue with the release by adding a `@quarkusbot continue` comment.

Where am I? - [X] Prerequisites - [X] Approve the core release - [X] Create branch (if needed) - [X] Prepare the core release - [X] Perform the core release - [X] Sync core release to Maven Central - [X] Release Gradle plugin - [X] Execute post-core-release operations - [X] Prepare the Quarkus Platform - [X] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central :pause_button: ☚ You are here - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update documentation - [ ] Announce release
quarkusbot commented 7 months ago

@quarkusbot continue

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

github-actions[bot] commented 7 months ago

:gear: Proceeding to step Sync Platform release to Maven Central

You can follow the progress of the workflow here.


Where am I? - [X] Prerequisites - [X] Approve the core release - [X] Create branch (if needed) - [X] Prepare the core release - [X] Perform the core release - [X] Sync core release to Maven Central - [X] Release Gradle plugin - [X] Execute post-core-release operations - [X] Prepare the Quarkus Platform - [X] Release the Quarkus Platform - [ ] Sync Platform release to Maven Central :gear: ☚ You are here - [ ] Update extension catalog - [ ] Execute post-Platform-release operations - [ ] Update JBang catalog - [ ] Publish CLI - [ ] Update quickstarts - [ ] Update documentation - [ ] Announce release
github-actions[bot] commented 7 months ago

:white_check_mark: Platform artifacts have been synced to Maven Central, continuing...

github-actions[bot] commented 7 months ago

:white_check_mark: 3.8.1 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.8.1

to trigger the performance evaluation testing for this release.

Then it is time to write the announcement:

Here is some content that could help in writing the announcement:

Announcement email template

Subject: [RELEASE] Quarkus 3.8.1

Hello,

Quarkus 3.8.1 has been released, and is now available from the Maven Central repository. The quickstarts and documentation have also been updated.

More information in the announcement blog post: https://quarkus.io/blog/quarkus-3-8-1-released/.

* BOM dependency:

  <dependency>
      <groupId>io.quarkus.platform</groupId>
      <artifactId>quarkus-bom</artifactId>
      <version>3.8.1</version>
      <type>pom</type>
      <scope>import</scope>
  </dependency>

* Changelogs are available from https://github.com/quarkusio/quarkus/releases/tag/3.8.0.CR1, https://github.com/quarkusio/quarkus/releases/tag/3.8.0, and https://github.com/quarkusio/quarkus/releases/tag/3.8.1
* Download is available from https://github.com/quarkusio/quarkus/releases/tag/3.8.1
* Documentation: https://quarkus.io

--
The Quarkus dev team

For new major/minor releases, we include the list of contributors in the announcement blog post. You can get a rough list of contributors (check for duplicates!) since the previous minor by executing the following commands in a Quarkus repository local clone:

git fetch upstream --tags git shortlog -s '3.7.0'..'3.8.1' | cut -d$'\t' -f 2 | grep -v dependabot | sort -d -f -i | paste -sd ',' - | sed 's/,/, /g'