Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,32 +1,5 @@
 ---
 working-groups:
-    - title: "Dev Services Lifecycle"
-      board-url: "https://github.com/orgs/quarkusio/projects/49"
-      short-description: |
-        This working group will define and implement a consistent and configurable lifecycle model for Dev Services. It will shift the startup to the correct phase, enable optional reuse across dev and test modes, and clarify teardown and sharing behavior. The goal is to improve the developer experience.
-      readme: |
-        <p>This working group was formed to address long-standing inconsistencies and pain points in the Dev Services lifecycle within Quarkus. Dev Services are essential for simplifying local development and testing by automatically provisioning runtime dependencies (e.g., databases, message brokers), but their current lifecycle behavior leads to confusion and inefficiencies. Most notably, they are started during the augmentation phase, which conflicts with their inherently runtime-oriented nature and causes issues with newer efforts such as the test classloading revamp.</p>
-        <p>The primary goal of this group is to define and implement a consistent, runtime-aligned lifecycle model for Dev Services. This includes shifting their startup to a phase after augmentation but before the application begins execution, ensuring better alignment with the runtime environment. A critical focus will also be on enabling optional reuse of Dev Services across dev and test modes — including reuse between repeated test executions — to reduce startup time and improve the iterative development experience.</p>
-        <p>The group's scope covers several strategic areas: formalizing when and how Dev Services are started, reused, or stopped; defining rules for discoverability and sharing between profiles or processes; and avoiding resource leaks or accidental retention. It explicitly excludes broader orchestration features (such as service dependency graphs) and unrelated feature enhancements.</p>
-        <p>The working group will produce a set of deliverables to support the new model. These include one or more Architecture Decision Records (ADRs) describing the new lifecycle model, the implementation of lifecycle logic in Quarkus Core, and updates to both user-facing and contributor documentation. Additionally, enhancements to the Dev Services development model will make it easier for extension authors to adopt and follow the new lifecycle standards. A public communication effort (e.g., blog posts or demos) will also be used to showcase the improvements.</p>
-        <p>The new API is described here: https://quarkus.io/blog/new-dev-services-api/</p>
-        <ul>
-        <li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong>  on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</li>
-        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/47683</li>
-        <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev">Zulip</a>)</li>
-        </ul>
-      status: on track
-      lts: false
-      completed: false
-      last-activity: 2026-05-12
-      last-update-date: 2026-03-30
-      last-update: |
-        We investigated some cases where quarkus-devservices-deployment not depending on quarkus-devservices was unexpectedly triggering validation warnings, and identified root causes and workarounds. We also resolved an issue with Kafka Dev Service loading across different Docker networks.
-        
-        (This status update was automatically generated using AI.)
-      point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong>  on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )"
-      proposal: https://github.com/quarkusio/quarkus/discussions/47683
-      discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev
     - title: "Dev Star"
       board-url: "https://github.com/orgs/quarkusio/projects/75"
       short-description: |
@@ -141,13 +114,83 @@ working-groups:
       status: on track
       lts: false
       completed: false
-      last-activity: 2026-05-12
+      last-activity: 2026-05-13
       last-update-date: 2026-03-25
       last-update: |
         Working Group Started.
       point-of-contact: "@phillip-kruger"
       proposal: https://github.com/quarkusio/quarkus/discussions/53093#discussioncomment-16271096
       discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/wg-dev-star/with/581636141
+    - title: "Quarkus 4"
+      board-url: "https://github.com/orgs/quarkusio/projects/51"
+      short-description: |
+        The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
+      readme: |
+        <h2>Objective</h2>
+        <p>This long‑running working group is dedicated to tracking development and ensuring a smooth rollout for Quarkus 4. It will serve as the central coordination point for feature tracking, release hygiene, migration guidance, and community alignment related to Quarkus 4.</p>
+        <h2>The Problem</h2>
+        <p>Quarkus 4 introduces significant shifts, including new Java 25 flags, architectural refinements, deprecations, and ecosystem changes. Without a focused group, efforts become fragmented, and downstream consumers (extensions, integrations, platform partners) may struggle to stay aligned.</p>
+        <h2>Proposed Solution</h2>
+        <p>Establish a designated WG to:</p>
+        <ul>
+        <li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
+        <li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
+        <li>Coordinate across teams (core, extensions, platform, tooling)</li>
+        <li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
+        <li>Publish ADRs, migration guides, and summary docs</li>
+        </ul>
+        <h2>Definition of Done</h2>
+        <p>This WG will be considered complete when:</p>
+        <ul>
+        <li>Quarkus 4 GA is released (including the platform)</li>
+        <li>All major features are merged and tested</li>
+        <li>Migration documentation is publicly available</li>
+        </ul>
+        <h2>Organizing the Work</h2>
+        <p>Coordination via:</p>
+        <ul>
+        <li>GitHub Discussions: use design‑discussions category</li>
+        <li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
+        <li>Project board to track status</li>
+        </ul>
+        <h2>Expected Timeline:</h2>
+        <p>This is a long-running WG, starting now and wrapping up post‑GA (~late Q2 2026). We’ll mark it as “done” upon the public release of Quarkus 4 GA.</p>
+      status: on track
+      lts: false
+      completed: false
+      last-activity: 2026-05-13
+      last-update-date: 2026-03-30
+      last-update: |
+        The team closed out significant work on the Vert.x 5 upgrade and migration of its core extension for Quarkus 4. New tasks include updating Vert.x configuration, reworking CI, and addressing Kafka Kerberos authentication in native mode. We're also defining OpenTelemetry trace sampling defaults and looking into extension modularity.
+        
+        (This status update was automatically generated using AI.)
+    - title: "Dev Services Lifecycle"
+      board-url: "https://github.com/orgs/quarkusio/projects/49"
+      short-description: |
+        This working group will define and implement a consistent and configurable lifecycle model for Dev Services. It will shift the startup to the correct phase, enable optional reuse across dev and test modes, and clarify teardown and sharing behavior. The goal is to improve the developer experience.
+      readme: |
+        <p>This working group was formed to address long-standing inconsistencies and pain points in the Dev Services lifecycle within Quarkus. Dev Services are essential for simplifying local development and testing by automatically provisioning runtime dependencies (e.g., databases, message brokers), but their current lifecycle behavior leads to confusion and inefficiencies. Most notably, they are started during the augmentation phase, which conflicts with their inherently runtime-oriented nature and causes issues with newer efforts such as the test classloading revamp.</p>
+        <p>The primary goal of this group is to define and implement a consistent, runtime-aligned lifecycle model for Dev Services. This includes shifting their startup to a phase after augmentation but before the application begins execution, ensuring better alignment with the runtime environment. A critical focus will also be on enabling optional reuse of Dev Services across dev and test modes — including reuse between repeated test executions — to reduce startup time and improve the iterative development experience.</p>
+        <p>The group's scope covers several strategic areas: formalizing when and how Dev Services are started, reused, or stopped; defining rules for discoverability and sharing between profiles or processes; and avoiding resource leaks or accidental retention. It explicitly excludes broader orchestration features (such as service dependency graphs) and unrelated feature enhancements.</p>
+        <p>The working group will produce a set of deliverables to support the new model. These include one or more Architecture Decision Records (ADRs) describing the new lifecycle model, the implementation of lifecycle logic in Quarkus Core, and updates to both user-facing and contributor documentation. Additionally, enhancements to the Dev Services development model will make it easier for extension authors to adopt and follow the new lifecycle standards. A public communication effort (e.g., blog posts or demos) will also be used to showcase the improvements.</p>
+        <p>The new API is described here: https://quarkus.io/blog/new-dev-services-api/</p>
+        <ul>
+        <li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong>  on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</li>
+        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/47683</li>
+        <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev">Zulip</a>)</li>
+        </ul>
+      status: on track
+      lts: false
+      completed: false
+      last-activity: 2026-05-12
+      last-update-date: 2026-03-30
+      last-update: |
+        We investigated some cases where quarkus-devservices-deployment not depending on quarkus-devservices was unexpectedly triggering validation warnings, and identified root causes and workarounds. We also resolved an issue with Kafka Dev Service loading across different Docker networks.
+        
+        (This status update was automatically generated using AI.)
+      point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong>  on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )"
+      proposal: https://github.com/quarkusio/quarkus/discussions/47683
+      discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev
     - title: "Modularity (JPMS) and JLink"
       board-url: "https://github.com/orgs/quarkusio/projects/76"
       short-description: |
@@ -379,49 +422,6 @@ working-groups:
       point-of-contact: "Guillaume Smet (@gmset) / Georgios Andrianakis (@geoand)"
       proposal: https://github.com/quarkusio/quarkus/discussions/52017
       discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/AOT.20cache.20-.20Global.20thread/with/568847190
-    - title: "Quarkus 4"
-      board-url: "https://github.com/orgs/quarkusio/projects/51"
-      short-description: |
-        The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
-      readme: |
-        <h2>Objective</h2>
-        <p>This long‑running working group is dedicated to tracking development and ensuring a smooth rollout for Quarkus 4. It will serve as the central coordination point for feature tracking, release hygiene, migration guidance, and community alignment related to Quarkus 4.</p>
-        <h2>The Problem</h2>
-        <p>Quarkus 4 introduces significant shifts, including new Java 25 flags, architectural refinements, deprecations, and ecosystem changes. Without a focused group, efforts become fragmented, and downstream consumers (extensions, integrations, platform partners) may struggle to stay aligned.</p>
-        <h2>Proposed Solution</h2>
-        <p>Establish a designated WG to:</p>
-        <ul>
-        <li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
-        <li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
-        <li>Coordinate across teams (core, extensions, platform, tooling)</li>
-        <li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
-        <li>Publish ADRs, migration guides, and summary docs</li>
-        </ul>
-        <h2>Definition of Done</h2>
-        <p>This WG will be considered complete when:</p>
-        <ul>
-        <li>Quarkus 4 GA is released (including the platform)</li>
-        <li>All major features are merged and tested</li>
-        <li>Migration documentation is publicly available</li>
-        </ul>
-        <h2>Organizing the Work</h2>
-        <p>Coordination via:</p>
-        <ul>
-        <li>GitHub Discussions: use design‑discussions category</li>
-        <li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
-        <li>Project board to track status</li>
-        </ul>
-        <h2>Expected Timeline:</h2>
-        <p>This is a long-running WG, starting now and wrapping up post‑GA (~late Q2 2026). We’ll mark it as “done” upon the public release of Quarkus 4 GA.</p>
-      status: on track
-      lts: false
-      completed: false
-      last-activity: 2026-05-12
-      last-update-date: 2026-03-30
-      last-update: |
-        The team closed out significant work on the Vert.x 5 upgrade and migration of its core extension for Quarkus 4. New tasks include updating Vert.x configuration, reworking CI, and addressing Kafka Kerberos authentication in native mode. We're also defining OpenTelemetry trace sampling defaults and looking into extension modularity.
-        
-        (This status update was automatically generated using AI.)
     - title: "Agentic Foundation and LangChain4j Next"
       board-url: "https://github.com/orgs/quarkiverse/projects/9"
       short-description: |