You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>This _working group aims to make the <a href="https://github.com/dmlloyd/gizmo/tree/gizmo2">Gizmo 2 POC</a> production-ready and integrate it into Quarkus core.</p>
9
-
<ul>
10
-
<li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li>
In the past month, the WG - Gizmo 2 successfully closed numerous issues, including improvements in error handling, support for instance field initializers, and updates to annotation handling. Key enhancements were made to Lambda singleton implementations and field check validations. Concurrently, several new issues were opened, still addressing challenges in error messaging, generic type handling, and improvements to operational efficiencies. The group remains focused on optimizing the Gizmo 2 framework while ensuring robust functionality and user experience.
22
-
23
-
(This status update was automatically generated using AI.)
24
-
deliverable: TBD
25
-
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
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.
61
-
readme: |
62
-
<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>
63
-
<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>
64
-
<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>
65
-
<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>
66
-
<ul>
67
-
<li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</li>
In the past month, the WG - Quarkus 3.20 LTS successfully closed three issues, addressing an exception related to missing Maven classes in the dev-ui for Gradle projects, enhancing the Grafana LGTM dashboards, and determining the appropriate Kafka client version for the 3.20 LTS release. No new issues were opened during this period, indicating focused progress on existing challenges.
@@ -106,10 +57,59 @@ working-groups:
106
57
status: on track
107
58
lts: true
108
59
completed: false
109
-
last-activity: 2025-05-19
60
+
last-activity: 2025-05-20
110
61
last-update-date: 2025-04-01
111
62
last-update: |
112
63
In the last month, the WG - Quarkus 3.15 LTS closed two issues: one regarding the assignment of random ports in the configuration and another updating the Kafka client version to 3.7.2 to address CVE-2024-56128. No new issues were opened, reflecting a commitment to resolving important topics for the upcoming LTS release.
<p>This _working group aims to make the <a href="https://github.com/dmlloyd/gizmo/tree/gizmo2">Gizmo 2 POC</a> production-ready and integrate it into Quarkus core.</p>
70
+
<ul>
71
+
<li>Point of contact: @mkouba (@<strong>Martin Kouba</strong> on Zulip)</li>
In the past month, the WG - Gizmo 2 successfully closed numerous issues, including improvements in error handling, support for instance field initializers, and updates to annotation handling. Key enhancements were made to Lambda singleton implementations and field check validations. Concurrently, several new issues were opened, still addressing challenges in error messaging, generic type handling, and improvements to operational efficiencies. The group remains focused on optimizing the Gizmo 2 framework while ensuring robust functionality and user experience.
83
+
84
+
(This status update was automatically generated using AI.)
85
+
deliverable: TBD
86
+
point-of-contact: "@mkouba (@<strong>Martin Kouba</strong> on Zulip)"
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.
93
+
readme: |
94
+
<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>
95
+
<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>
96
+
<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>
97
+
<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>
98
+
<ul>
99
+
<li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</li>
0 commit comments