Merge branch 'quarkusio:main' into PerformancePage

Author: insectengine

.github/workflows/sync-working-groups.yml

@@ -24,7 +24,7 @@ jobs:
           java-version: ${{ env.JVM_VERSION }}
 
       - name: Build working groups YAML file
-        uses: jbangdev/jbang-action@v0.117.1
+        uses: jbangdev/jbang-action@v0.119.0
         with:
           script: working-groups/main.java
           jbangargs: --verbose -Dworking-groups.output=_data/wg.yaml

_data/insights-videos.yaml

@@ -4,12 +4,7 @@ futureheadline: "Scheduled Podcasts"
 
 futurevideos:
 
-- title: "EPISODE #183: Build indestructible services with Quarkus Temporal"
-  link: 
-  date: "October 21, 2024"
-  authors: "Emil Lefkof (Melloware) & Loïc Hermann"
-
-- title: "EPISODE #184: Quarkus & Develocity"
+- title: "EPISODE #184: Quarkus CI builds now 4X faster with Develocity"
   link: 
   date: "October 28, 2024"
   authors: "Trisha Gee, Jérôme Prinet, & Guillaume Smet"
@@ -33,6 +28,10 @@ pastheadline: "Archived Podcast Videos"
 
 pastvideos:
 
+- title: "EPISODE #183: Build indestructible services with Quarkus Temporal"
+  link: https://youtube.com/live/XICZxuaeYwI
+  date: "October 21, 2024"
+  authors: "Emil Lefkof (Melloware) & Loïc Hermann"
 
 - title: "EPISODE #182: Quarkus testing with Wiremock"
   link: https://youtube.com/live/ey4a1mxWHr4

_data/versioned/main/index/quarkus.yaml

@@ -633,6 +633,11 @@ types:
     id: security-basic-authentication-howto
     type: howto
     url: /guides/security-basic-authentication-howto
+  - title: Frequently asked questions about writing extensions
+    filename: extension-faq.adoc
+    id: extensions-faq
+    type: howto
+    url: /guides/extension-faq
   - title: Quarkus Security with Jakarta Persistence
     filename: security-jpa.adoc
     summary: You can configure your application to use Jakarta Persistence to store users' identities.

_data/wg.yaml

@@ -1,22 +1,5 @@
 ---
 working-groups:
-    - title: "Quarkus 3.15 LTS"
-      board-url: "https://github.com/orgs/quarkusio/projects/28"
-      short-description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
-      readme: |
-        <p>This working group uses a different board:</p>
-        <ul>
-        <li>The <code>under discussion</code> column contains the issues we would like to have in the next LTS but are still under consideration.</li>
-        <li>The <code>out of scope</code> column contains the issues under discussion' that won't be included. The reason can be time or technical...</li>
-        <li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li>
-        <li>The <code>done</code> column means that the issues have been completed</li>
-        </ul>
-      status: on track
-      completed: false
-      last-activity: 2024-10-16
-      last-update: |
-        3.15 has been cut. 
-        The 3.15.x is the new LTS, starting with 3.15.1
     - title: "Roq :: Quarkus SSG"
       board-url: "https://github.com/orgs/quarkiverse/projects/6"
       short-description: Allow Static Site Generation with Quarkus.
@@ -38,7 +21,7 @@ working-groups:
         <p>This is a great opportunity to participate in fun effort and be involved with the Quarkus community, if anyone is interested in being a part of this, please reach out to me 🚀</p>
       status: on track
       completed: false
-      last-activity: 2024-10-14
+      last-activity: 2024-10-22
       last-update: |
         0.0.3 has been released, it is the MVP version and allowed to publish the Roq blog: https://quarkiverse.io/quarkus-roq/posts/2024-08-29-welcome-to-roq/
         
@@ -47,18 +30,23 @@ working-groups:
         The target is to have 1.0.0 the 1 October 2024.
         
         For 1.0 we need pagination, tags and SEO.
-    - title: "WebSocket Next"
-      board-url: "https://github.com/orgs/quarkusio/projects/26"
-      short-description: WebSocket-Next related tasks
+    - title: "Quarkus 3.15 LTS"
+      board-url: "https://github.com/orgs/quarkusio/projects/28"
+      short-description: This WG focuses on defining the issues we would like to have in the next-to-be LTS (Quarkus 3.14/3.15)
       readme: |
-        <p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
-        <p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
-        <p>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</p>
+        <p>This working group uses a different board:</p>
+        <ul>
+        <li>The <code>under discussion</code> column contains the issues we would like to have in the next LTS but are still under consideration.</li>
+        <li>The <code>out of scope</code> column contains the issues under discussion' that won't be included. The reason can be time or technical...</li>
+        <li>The <code>in progress</code> means that the work has started and should be completed before the TLS cut date</li>
+        <li>The <code>done</code> column means that the issues have been completed</li>
+        </ul>
       status: on track
       completed: false
-      last-activity: 2024-10-11
+      last-activity: 2024-10-21
       last-update: |
-        The last outstanding issue is OTel integration. @michalvavrik is working on a [pull request](https://github.com/quarkusio/quarkus/pull/41956). I will meet with Michal and Bruno in the coming weeks. The PR is quite massive and we need to review it carefully.
+        3.15 has been cut. 
+        The 3.15.x is the new LTS, starting with 3.15.1
     - title: "Test classloading"
       board-url: "https://github.com/orgs/quarkusio/projects/30"
       short-description: The goal of this working group is to rewrite Quarkus's test classloading, so that tests are run in the same classloader as the application under tests, and Quarkus extensions can do "Quarkus-y" manipulations of test classes.
@@ -72,17 +60,29 @@ working-groups:
         <p>The goal of this working group is to allow test classes to fully participate in the 'quarkification' of classes. The mechanism for this is probably just to load the test classes with the classloader we intend to run them with, so that JUnit sees the 'correct' version of the class.</p>
       status: on track
       completed: false
-      last-activity: 2024-10-04
+      last-activity: 2024-10-19
       last-update: |
         Progress continues. In the CI runs, the number of failing jobs is now 10. Most significantly, a bug which meant almost nothing worked on windows has now been fixed.
+    - title: "WebSocket Next"
+      board-url: "https://github.com/orgs/quarkusio/projects/26"
+      short-description: WebSocket-Next related tasks
+      readme: |
+        <p>The WebSocket Next <em>focus group</em> aims to improve our WebSocket experience.</p>
+        <p>Recently, we delivered a new approach to dealing with WebSocket (both for the server and client). This was the first step. There are still a few areas to improve, such as documentation, security, observability, and testability. The goal of this focus group is to track these efforts.</p>
+        <p>Point of contact: @mkouba (@<strong>Martin Kouba</strong>  on Zulip)</p>
+      status: on track
+      completed: false
+      last-activity: 2024-10-11
+      last-update: |
+        The last outstanding issue is OTel integration. @michalvavrik is working on a [pull request](https://github.com/quarkusio/quarkus/pull/41956). I will meet with Michal and Bruno in the coming weeks. The PR is quite massive and we need to review it carefully.
     - title: "Quarkus Config and IDEs"
       board-url: "https://github.com/orgs/quarkusio/projects/32"
       short-description: Let's define a format for the files containing the config model we will include in the jars for IDE consumption.
       readme: |
         <p>Let's define a format for the files containing the config model we will include in the jars for IDE consumption.</p>
         <p>See https://github.com/quarkusio/quarkus/discussions/42671 for more details.</p>
         <p><em>Point of contact</em>: @gsmet (Zulip: @_<strong>Guillaume Smet</strong> )</p>
-      status: on track
+      status: staled
       completed: false
       last-activity: 2024-10-03
     - title: "Docker file generation"

_generated-doc/main/config/quarkus-agroal.adoc

@@ -85,25 +85,6 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |
 
-a|icon:lock[title=Fixed at build time] [[quarkus-agroal_quarkus-datasource-jdbc-tracing]] [.property-path]##link:#quarkus-agroal_quarkus-datasource-jdbc-tracing[`quarkus.datasource.jdbc.tracing`]##
-
-`quarkus.datasource."datasource-name".jdbc.tracing`
-
-[.description]
---
-Enable JDBC tracing. Disabled by default.
-
-
-ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_DATASOURCE_JDBC_TRACING+++[]
-endif::add-copy-button-to-env-var[]
-ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_DATASOURCE_JDBC_TRACING+++`
-endif::add-copy-button-to-env-var[]
---
-|boolean
-|`false`
-
 a|icon:lock[title=Fixed at build time] [[quarkus-agroal_quarkus-datasource-jdbc-telemetry]] [.property-path]##link:#quarkus-agroal_quarkus-datasource-jdbc-telemetry[`quarkus.datasource.jdbc.telemetry`]##
 
 `quarkus.datasource."datasource-name".jdbc.telemetry`

_generated-doc/main/config/quarkus-agroal_quarkus.datasource.adoc

@@ -85,25 +85,6 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |
 
-a|icon:lock[title=Fixed at build time] [[quarkus-agroal_quarkus-datasource-jdbc-tracing]] [.property-path]##link:#quarkus-agroal_quarkus-datasource-jdbc-tracing[`quarkus.datasource.jdbc.tracing`]##
-
-`quarkus.datasource."datasource-name".jdbc.tracing`
-
-[.description]
---
-Enable JDBC tracing. Disabled by default.
-
-
-ifdef::add-copy-button-to-env-var[]
-Environment variable: env_var_with_copy_button:+++QUARKUS_DATASOURCE_JDBC_TRACING+++[]
-endif::add-copy-button-to-env-var[]
-ifndef::add-copy-button-to-env-var[]
-Environment variable: `+++QUARKUS_DATASOURCE_JDBC_TRACING+++`
-endif::add-copy-button-to-env-var[]
---
-|boolean
-|`false`
-
 a|icon:lock[title=Fixed at build time] [[quarkus-agroal_quarkus-datasource-jdbc-telemetry]] [.property-path]##link:#quarkus-agroal_quarkus-datasource-jdbc-telemetry[`quarkus.datasource.jdbc.telemetry`]##
 
 `quarkus.datasource."datasource-name".jdbc.telemetry`