Skip to content

Commit a709eb2

Browse files
actions-useractions-user
committed
Sync working groups
1 parent 97def69 commit a709eb2

1 file changed

Lines changed: 94 additions & 94 deletions

File tree

‎_data/wg.yaml‎

Lines changed: 94 additions & 94 deletions
Original file line numberDiff line numberDiff line change
@@ -1,48 +1,73 @@
11
---
22
working-groups:
3-
- title: "Quarkus 4"
4-
board-url: "https://github.com/orgs/quarkusio/projects/51"
3+
- title: "Quarkus Data"
4+
board-url: "https://github.com/orgs/quarkusio/projects/50"
55
short-description: |
6-
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
6+
The primary objective of this working group is to develop the next version of Panache, now known as Quarkus Data.
77
readme: |
8-
<h2>Objective</h2>
9-
<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>
10-
<h2>The Problem</h2>
11-
<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>
12-
<h2>Proposed Solution</h2>
13-
<p>Establish a designated WG to:</p>
8+
<h1>Objective</h1>
9+
<p>The main objective of this working group is to bring forth the next version of Panache.</p>
10+
<h1>The Problem</h1>
11+
<p>Panache is great for many things, but over time, we realised the following limitations:</p>
1412
<ul>
15-
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
16-
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
17-
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
18-
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
19-
<li>Publish ADRs, migration guides, and summary docs</li>
13+
<li>We have three distinct versions: Hibernate ORM, Hibernate Reactive and Mongo (blocking and reactive)</li>
14+
<li>It is impossible to use the same entities with Hibernate ORM and Hibernate Reactive</li>
15+
<li>Stateless sessions are not supported</li>
16+
<li>Hibernate Processor annotations, and Jakarta Data are not supported</li>
17+
<li>We have triplicate types such as <code>Sort</code> and <code>Order</code> between Panache, ORM and Jakarta Data</li>
18+
<li>We have two ways to place entity query operations : on the entity itself, or in repositories</li>
19+
<li>Entity query operations require type-system hacks which makes them less type-safe than we want with <code>var</code> and <code>for-each</code> and especially with reactive operations.</li>
2020
</ul>
21-
<h2>Definition of Done</h2>
22-
<p>This WG will be considered complete when:</p>
21+
<h1>The proposed Solution</h1>
22+
<p>We propose a new Panache version that will solve all these issues:</p>
2323
<ul>
24-
<li>Quarkus 4 GA is released (including the platform)</li>
25-
<li>All major features are merged and tested</li>
26-
<li>Migration documentation is publicly available</li>
24+
<li>Unify all variants in a single module, supporting blocking, reactive, stateless and stateful sessions</li>
25+
<li>Provide an entity toplevel class for each 4 modes of operation, yet allow access to the other modes</li>
26+
<li>Move all entity query operations from the entity class to the repository class</li>
27+
<li>Provide a repository toplevel class for each 4 modes of operation, yet allow access to the other modes</li>
28+
<li>Provide easy access to any type of repository by placing them as nested interfaces in the entity class, via a generated accessor on the entity metamodel class</li>
29+
<li>Provide out of the box accessors for the 4 modes of operation repositories on the entity metamodel class</li>
30+
<li>Support Jakarta Data and Hibernate Processor type-safe annotations</li>
31+
<li>Optional: Support of Mongo via the coming ORM JDBC support</li>
32+
<li>Optional: provide JD repository type alternatives for the missing three modes</li>
33+
<li>Optional: provide a way to convert Panache 1 to Panache.Next</li>
2734
</ul>
28-
<h2>Organizing the Work</h2>
29-
<p>Coordination via:</p>
35+
<h1>Definition of Done</h1>
3036
<ul>
31-
<li>GitHub Discussions: use design‑discussions category</li>
32-
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
33-
<li>Project board to track status</li>
37+
<li>Deliver the new Panache extension as a <code>stable</code> state (after preview/experimental versions for feedback)</li>
38+
<li>Tests</li>
39+
<li>Documentation</li>
40+
<li>Codestart</li>
41+
<li>REST Data with Panache support</li>
42+
<li>Renarde support</li>
43+
<li>Quarkus Insights</li>
3444
</ul>
45+
<h1>Scope of Work</h1>
46+
<p>It is currently out of scope to retrofit this with the existing Panache modules. This will be a new module with no backward compatibility (although most type-unsafe operations will continue as-is, so you will be familiar with them).</p>
47+
<h1>Organizing the Work</h1>
48+
<h2>Communication and Transparency:</h2>
49+
<p>This will be done via GitHub issues on the Quarkus core project.</p>
3550
<h2>Expected Timeline:</h2>
36-
<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>
51+
<p>Most of the R&amp;D and design work has been completed over the last two years. Now remains the task of merging, documenting, testing, and tweaking it until it's complete.</p>
52+
<ul>
53+
<li>Point of contact: @FroMage (@<strong>Stephane Epardaud</strong> on Zulip)</li>
54+
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/48949</li>
55+
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261">Zulip</a></li>
56+
<li>Deliverable: <a href="https://quarkus.io/blog/hibernate-panache-next/">Blog Post</a></li>
57+
</ul>
3758
status: on track
3859
lts: false
3960
completed: false
4061
last-activity: 2026-06-03
4162
last-update-date: 2026-05-26
4263
last-update: |
43-
Big strides this week on the Quarkus 4 effort! We finally closed out the upgrade to Vert.x 5, including migrating the OpenTelemetry extension and several others. Also got the OpenShift, Kubernetes, and MongoDB dev services to behave and not start during augmentation.
64+
The Quarkus Data WG completed a big renaming effort, transitioning Panache Next to Quarkus Data and its module to Quarkus Data Hibernate. We improved native compilation support, especially when Hibernate Reactive is absent. Security annotations now properly apply to repositories, and we resolved various compilation issues. Plus, we switched repository scopes from `@Dependant` to `@ApplicationScoped`.
4465
4566
(This status update was automatically generated using AI.)
67+
deliverable: <a rel="nofollow" href="https://quarkus.io/blog/hibernate-panache-next/">Blog Post</a>
68+
point-of-contact: "@FroMage (@<strong>Stephane Epardaud</strong> on Zulip)"
69+
proposal: https://github.com/quarkusio/quarkus/discussions/48949
70+
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261
4671
- title: "Quarkus Terminal"
4772
board-url: "https://github.com/orgs/quarkusio/projects/77"
4873
short-description: |
@@ -140,74 +165,6 @@ working-groups:
140165
point-of-contact: "@maxandersen"
141166
proposal: https://github.com/quarkusio/quarkus/discussions/53667
142167
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Quarkus.20Terminal/with/587817394
143-
- title: "Quarkus Data"
144-
board-url: "https://github.com/orgs/quarkusio/projects/50"
145-
short-description: |
146-
The primary objective of this working group is to develop the next version of Panache, now known as Quarkus Data.
147-
readme: |
148-
<h1>Objective</h1>
149-
<p>The main objective of this working group is to bring forth the next version of Panache.</p>
150-
<h1>The Problem</h1>
151-
<p>Panache is great for many things, but over time, we realised the following limitations:</p>
152-
<ul>
153-
<li>We have three distinct versions: Hibernate ORM, Hibernate Reactive and Mongo (blocking and reactive)</li>
154-
<li>It is impossible to use the same entities with Hibernate ORM and Hibernate Reactive</li>
155-
<li>Stateless sessions are not supported</li>
156-
<li>Hibernate Processor annotations, and Jakarta Data are not supported</li>
157-
<li>We have triplicate types such as <code>Sort</code> and <code>Order</code> between Panache, ORM and Jakarta Data</li>
158-
<li>We have two ways to place entity query operations : on the entity itself, or in repositories</li>
159-
<li>Entity query operations require type-system hacks which makes them less type-safe than we want with <code>var</code> and <code>for-each</code> and especially with reactive operations.</li>
160-
</ul>
161-
<h1>The proposed Solution</h1>
162-
<p>We propose a new Panache version that will solve all these issues:</p>
163-
<ul>
164-
<li>Unify all variants in a single module, supporting blocking, reactive, stateless and stateful sessions</li>
165-
<li>Provide an entity toplevel class for each 4 modes of operation, yet allow access to the other modes</li>
166-
<li>Move all entity query operations from the entity class to the repository class</li>
167-
<li>Provide a repository toplevel class for each 4 modes of operation, yet allow access to the other modes</li>
168-
<li>Provide easy access to any type of repository by placing them as nested interfaces in the entity class, via a generated accessor on the entity metamodel class</li>
169-
<li>Provide out of the box accessors for the 4 modes of operation repositories on the entity metamodel class</li>
170-
<li>Support Jakarta Data and Hibernate Processor type-safe annotations</li>
171-
<li>Optional: Support of Mongo via the coming ORM JDBC support</li>
172-
<li>Optional: provide JD repository type alternatives for the missing three modes</li>
173-
<li>Optional: provide a way to convert Panache 1 to Panache.Next</li>
174-
</ul>
175-
<h1>Definition of Done</h1>
176-
<ul>
177-
<li>Deliver the new Panache extension as a <code>stable</code> state (after preview/experimental versions for feedback)</li>
178-
<li>Tests</li>
179-
<li>Documentation</li>
180-
<li>Codestart</li>
181-
<li>REST Data with Panache support</li>
182-
<li>Renarde support</li>
183-
<li>Quarkus Insights</li>
184-
</ul>
185-
<h1>Scope of Work</h1>
186-
<p>It is currently out of scope to retrofit this with the existing Panache modules. This will be a new module with no backward compatibility (although most type-unsafe operations will continue as-is, so you will be familiar with them).</p>
187-
<h1>Organizing the Work</h1>
188-
<h2>Communication and Transparency:</h2>
189-
<p>This will be done via GitHub issues on the Quarkus core project.</p>
190-
<h2>Expected Timeline:</h2>
191-
<p>Most of the R&amp;D and design work has been completed over the last two years. Now remains the task of merging, documenting, testing, and tweaking it until it's complete.</p>
192-
<ul>
193-
<li>Point of contact: @FroMage (@<strong>Stephane Epardaud</strong> on Zulip)</li>
194-
<li>Proposal: https://github.com/quarkusio/quarkus/discussions/48949</li>
195-
<li>Discussion: <a href="https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261">Zulip</a></li>
196-
<li>Deliverable: <a href="https://quarkus.io/blog/hibernate-panache-next/">Blog Post</a></li>
197-
</ul>
198-
status: on track
199-
lts: false
200-
completed: false
201-
last-activity: 2026-06-03
202-
last-update-date: 2026-05-26
203-
last-update: |
204-
The Quarkus Data WG completed a big renaming effort, transitioning Panache Next to Quarkus Data and its module to Quarkus Data Hibernate. We improved native compilation support, especially when Hibernate Reactive is absent. Security annotations now properly apply to repositories, and we resolved various compilation issues. Plus, we switched repository scopes from `@Dependant` to `@ApplicationScoped`.
205-
206-
(This status update was automatically generated using AI.)
207-
deliverable: <a rel="nofollow" href="https://quarkus.io/blog/hibernate-panache-next/">Blog Post</a>
208-
point-of-contact: "@FroMage (@<strong>Stephane Epardaud</strong> on Zulip)"
209-
proposal: https://github.com/quarkusio/quarkus/discussions/48949
210-
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/WG.20-.20Panache.2ENext/with/529258261
211168
- title: "Dev Star"
212169
board-url: "https://github.com/orgs/quarkusio/projects/75"
213170
short-description: |
@@ -331,6 +288,49 @@ working-groups:
331288
point-of-contact: "@phillip-kruger"
332289
proposal: https://github.com/quarkusio/quarkus/discussions/53093#discussioncomment-16271096
333290
discussion: https://quarkusio.zulipchat.com/#narrow/channel/187038-dev/topic/wg-dev-star/with/581636141
291+
- title: "Quarkus 4"
292+
board-url: "https://github.com/orgs/quarkusio/projects/51"
293+
short-description: |
294+
The Quarkus 4 working group aims to coordinate and track all Quarkus 4-related development in a long-running effort.
295+
readme: |
296+
<h2>Objective</h2>
297+
<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>
298+
<h2>The Problem</h2>
299+
<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>
300+
<h2>Proposed Solution</h2>
301+
<p>Establish a designated WG to:</p>
302+
<ul>
303+
<li>Track all Quarkus 4‑related issues and PRs (using label triage/quarkus-4)</li>
304+
<li>Maintain a GitHub project board for feature status, blockers, and timelines</li>
305+
<li>Coordinate across teams (core, extensions, platform, tooling)</li>
306+
<li>Surface migration considerations and flag impacts (e.g. new --add-opens needs, optimized defaults) - useful to create the migration guide and rules</li>
307+
<li>Publish ADRs, migration guides, and summary docs</li>
308+
</ul>
309+
<h2>Definition of Done</h2>
310+
<p>This WG will be considered complete when:</p>
311+
<ul>
312+
<li>Quarkus 4 GA is released (including the platform)</li>
313+
<li>All major features are merged and tested</li>
314+
<li>Migration documentation is publicly available</li>
315+
</ul>
316+
<h2>Organizing the Work</h2>
317+
<p>Coordination via:</p>
318+
<ul>
319+
<li>GitHub Discussions: use design‑discussions category</li>
320+
<li>Issues/PRs: label with <code>triage/quarkus-4</code></li>
321+
<li>Project board to track status</li>
322+
</ul>
323+
<h2>Expected Timeline:</h2>
324+
<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>
325+
status: on track
326+
lts: false
327+
completed: false
328+
last-activity: 2026-06-03
329+
last-update-date: 2026-05-26
330+
last-update: |
331+
Big strides this week on the Quarkus 4 effort! We finally closed out the upgrade to Vert.x 5, including migrating the OpenTelemetry extension and several others. Also got the OpenShift, Kubernetes, and MongoDB dev services to behave and not start during augmentation.
332+
333+
(This status update was automatically generated using AI.)
334334
- title: "Unified Event Bus"
335335
board-url: "https://github.com/orgs/quarkusio/projects/73"
336336
short-description: |

0 commit comments

Comments
 (0)