|
1 | 1 | --- |
2 | 2 | working-groups: |
| 3 | + - title: "Dev Services Lifecycle" |
| 4 | + board-url: "https://github.com/orgs/quarkusio/projects/49" |
| 5 | + short-description: | |
| 6 | + 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. |
| 7 | + readme: | |
| 8 | + <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> |
| 9 | + <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> |
| 10 | + <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> |
| 11 | + <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> |
| 12 | + <ul> |
| 13 | + <li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</li> |
| 14 | + <li>Proposal: https://github.com/quarkusio/quarkus/discussions/47683</li> |
| 15 | + <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev">Zulip</a>)</li> |
| 16 | + </ul> |
| 17 | + status: on track |
| 18 | + lts: false |
| 19 | + completed: false |
| 20 | + last-activity: 2025-07-18 |
| 21 | + last-update-date: 2025-06-24 |
| 22 | + last-update: | |
| 23 | + In the last month, the WG - Dev Services Lifecycle has made significant progress by closing several issues related to the Redis dev services, including enhancements in testing and controlling their startup behavior during augmentation. Additionally, new issues were opened to refine test coverage further and simplify the development services model, indicating ongoing efforts to enhance the developer experience and consistency. |
| 24 | + |
| 25 | + (This status update was automatically generated using AI.) |
| 26 | + |
| 27 | + |
| 28 | + **NOTE**: The Redis exploration took a long time, but it has paved the way for the generalization for other dev services. Many test scenarios were not covered in the initial codebase. |
| 29 | + point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )" |
| 30 | + proposal: https://github.com/quarkusio/quarkus/discussions/47683 |
| 31 | + discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev |
3 | 32 | - title: "OIDC improvements" |
4 | 33 | board-url: "https://github.com/orgs/quarkusio/projects/46" |
5 | 34 | short-description: | |
@@ -116,35 +145,6 @@ working-groups: |
116 | 145 | point-of-contact: "@FroMage (@<strong>Stephane Epardaud</strong> on Zulip)" |
117 | 146 | proposal: https://github.com/quarkusio/quarkus/discussions/48949 |
118 | 147 | discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261 |
119 | | - - title: "Dev Services Lifecycle" |
120 | | - board-url: "https://github.com/orgs/quarkusio/projects/49" |
121 | | - short-description: | |
122 | | - 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. |
123 | | - readme: | |
124 | | - <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> |
125 | | - <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> |
126 | | - <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> |
127 | | - <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> |
128 | | - <ul> |
129 | | - <li>Point of contact: @holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )</li> |
130 | | - <li>Proposal: https://github.com/quarkusio/quarkus/discussions/47683</li> |
131 | | - <li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev">Zulip</a>)</li> |
132 | | - </ul> |
133 | | - status: on track |
134 | | - lts: false |
135 | | - completed: false |
136 | | - last-activity: 2025-07-17 |
137 | | - last-update-date: 2025-06-24 |
138 | | - last-update: | |
139 | | - In the last month, the WG - Dev Services Lifecycle has made significant progress by closing several issues related to the Redis dev services, including enhancements in testing and controlling their startup behavior during augmentation. Additionally, new issues were opened to refine test coverage further and simplify the development services model, indicating ongoing efforts to enhance the developer experience and consistency. |
140 | | - |
141 | | - (This status update was automatically generated using AI.) |
142 | | - |
143 | | - |
144 | | - **NOTE**: The Redis exploration took a long time, but it has paved the way for the generalization for other dev services. Many test scenarios were not covered in the initial codebase. |
145 | | - point-of-contact: "@holly-cummins (@<strong>Holly Cummins</strong> on Zulip), @ozangunalp (@<strong>Ozan Günalp</strong> on Zulip )" |
146 | | - proposal: https://github.com/quarkusio/quarkus/discussions/47683 |
147 | | - discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev |
148 | 148 | - title: "Gizmo 2" |
149 | 149 | board-url: "https://github.com/orgs/quarkusio/projects/43" |
150 | 150 | short-description: | |
|
0 commit comments